“Why are you speaking now?”
Lorraine looked toward the closed door.
“Because I saw the airport's announcement about the investigation. I realized the system had been activated again, and I remembered what Adrian said before he left. He told me that one day someone would need the original records, and that I should never allow the official summary to replace the evidence.”
She passed the notebook to Samuel.
“I was wrong to process the revised minutes without demanding proof. I was wrong to assume someone else had checked the authorization. I cannot undo those decisions. But I can tell you what I saw and give you the records I kept.”
Jonathan thanked her and assured her that the documents would be preserved and examined independently. He made no promises about the outcome of the investigation. Lorraine's cooperation was important, but her account still needed corroboration.
As the interview ended, she asked one question.
“Has Adrian Cole been cleared?”
“We haven't reached conclusions about individual responsibility,” Jonathan replied. “But the original records support his claim that he requested the project be suspended.”
Lorraine nodded, visibly relieved.
“He tried to stop it. He was the only person in those meetings who kept asking what would happen if the system was wrong.”
At 10:46 a.m., the handwriting examiner's preliminary review confirmed that the initials on the memo were unlikely to have been written by Adrian Cole. A full examination would take longer, but the finding supported Lorraine's account.
The legal team also confirmed that the transfer receipt for the Master Clearance Ledger had been signed by Richard Bell and that no separate approval for the transfer had been located.
Jonathan brought the findings to the incident command room. Elena had already traced the Northbridge certificate to a contractor account used during the recent modernization review.
“There's a direct link,” she said. “The account that renewed the recovery certificate was accessed through the same consultancy environment Bell used. We still can't prove who was physically operating the terminal, but the account activity overlaps with his authorized access.”
“Can we suspend the consultancy account?”
“It's already suspended. The contractor's access to all legacy systems has been blocked, and the certificate has been revoked. We're preserving the records before making further changes.”
At 11:15 a.m., the airport's legal team contacted Bell and requested that he preserve all records related to Project Horizon. Bell replied that he would cooperate with the formal process but denied any wrongdoing.
Then Priya discovered one more item in the ledger's historical metadata.
The recovery account had been scheduled to expire after thirty days, just as Lorraine had described. But the expiration date had been extended repeatedly.
Each renewal used the same administrative exception.
Each renewal appeared to have been approved by a system identity rather than an individual.
And every renewal had been processed through Northbridge's contractor environment.
Jonathan stared at the records.
“Someone turned a temporary account into a permanent one,” he said.
Elena nodded. “And because every renewal referred back to the previous approval, the system created the appearance of an unbroken authorization chain.”
“Even though the chain began with a request that had never been properly approved.”
“Exactly.”
The technical investigation had finally identified how the recovery function survived. Lorraine's testimony had explained how the paperwork was altered. Adrian's records showed that the fourth approval had never been signed. Martin's admission established that the maintenance exception had been temporary.
The remaining evidence pointed toward Richard Bell and the contractor environment he continued to influence after retirement.
But Jonathan refused to announce a conclusion until the team had completed its forensic review.
They had spent three years living with an official story that did not match the evidence.
They would not replace it with another story based on assumptions.
That afternoon, Jonathan approved a formal escalation to the airport's governing board and external oversight authorities. The report documented the unauthorized recovery process, the alteration of historical records, the unapproved retention of the legacy gateway, and the repeated use of a contractor certificate to maintain the hidden authorization function.
At the end of the report, Jonathan added one final instruction:
No historical authorization will be accepted as valid solely because it appears in the Master Clearance Ledger. Every disputed decision must be verified against its original record and independently confirmed by the responsible authority.
The instruction was simple.
But it marked the beginning of the end for the system that had allowed an unsigned approval to become official truth.
By the third day of the investigation, Westbridge Airport's modern operational systems were functioning normally. Passenger processing continued, flights departed, and security procedures remained in place. The legacy authorization environment was isolated, and no new clearance could be issued through Project Horizon.
Yet the investigation team had not finished.
The Master Clearance Ledger still contained thousands of historical records, many of which had been copied across multiple systems. Some were genuine. Others had been revised, duplicated, or linked to authorization references that could no longer be verified. Simply deleting the ledger would remove evidence of the manipulation, while leaving it active would preserve the risk that its records could be used again.
The airport needed a controlled way to prove that the hidden recovery process could no longer operate.
Elena proposed a final test in a laboratory environment disconnected from all operational systems. The team would create a forensic copy of the ledger, reproduce the conditions under which the unauthorized account had activated, and confirm that the system could not generate a valid permission without a complete, independently verified approval chain.
Jonathan agreed, but with strict conditions. No live credentials would be used. No airport operational system would be connected. The test would be observed by the independent auditor, the airport's legal representative, and a technical specialist who had not participated in Project Horizon.
Victor Shaw would help identify the original configuration, but he would not be allowed to modify the system directly.
“Are you comfortable with that?” Jonathan asked him.
Victor nodded. “I should never have assumed the equipment was harmless because it was old. I'll provide whatever information I can.”
The test began at 9:00 a.m. in a secured technical laboratory. The forensic copy of the ledger was loaded onto a controlled workstation. Elena verified that the laboratory had no route to the airport's operational network. Samuel checked the evidence record, and Priya confirmed that the copied authorization entries matched the preserved source files.
The team first attempted to process the original fourth approval.
The ledger accepted the record as complete.
“That is the problem,” Priya said. “It doesn't check for a signed approval document. It checks whether the reference number is marked as validated in the historical database.”
Elena examined the configuration. “The original system was designed to trust the ledger's status field. Once the record was marked complete, the system stopped checking the underlying approval.”
“So if someone changes the status field, the ledger treats the authorization as legitimate,” Jonathan said.
“Yes. The recovery account was able to do exactly that.”
The team then modified the test copy so that the fourth approval was explicitly marked as unsigned. They removed the legacy exception and disabled the recovery function. When the same request was submitted, the ledger rejected it.
AUTHORIZATION INCOMPLETE. INDEPENDENT APPROVAL REQUIRED.
Samuel reviewed the result.
“That's the expected behavior. Now we need to test the fallback path.”
Priya submitted a simulated emergency request. The ledger attempted to use the generic recovery account, but the account had no active permission to validate historical records. The request was rejected.
They repeated the test with a simulated contractor certificate. The result was the same.
For the first time, the team had demonstrated that the recovery function could be prevented from turning an incomplete historical record into a valid authorization.
But Elena was not satisfied.
“We've tested the known paths,” she said. “We still need to verify whether a queued request can synchronize after the system is restored.”
The team used the forensic copy of the backup unit to simulate an offline request. The ledger stored the request locally, then attempted to synchronize it when the simulated connection returned. Because the approval chain was incomplete, the modern validation layer rejected it.
The result was reassuring.
Then a new record appeared in the test log.
ALTERNATE VALIDATION HOLDER: RICHARD BELL.
No one spoke.
The entry had been generated by the forensic copy, which contained no live connection to Bell's account. It appeared to be part of the original ledger's internal fallback logic.
“Is this just a historical entry?” Jonathan asked.
Elena checked the timestamp. “No. The test copy generated it during the simulated recovery.”
“Can it issue a permission?”
“No. The modern validation layer rejects the request. But the fact that Bell's name is embedded in the fallback logic is significant.”
Priya opened the account mapping table. Richard Bell's name was linked to an old executive service identity. That identity had been used to approve the transfer of the Master Clearance Ledger to Northbridge. It was also associated with the administrative exception that kept the recovery function active.
The system had not simply searched for any available executive.
It had a predefined fallback chain, and Bell was one of the names inside it.
“Someone configured the ledger to use his identity when the primary authorization failed,” Jonathan said.
“Or the system inherited an old mapping that was never removed,” Elena replied. “We need to distinguish deliberate design from careless configuration.”
They examined the mapping's creation date. It had been added after the original termination request, on the same day the fifth authorization role was created.
The metadata identified the account that submitted the change, but the account itself was a shared executive administration identity. The record had no personal signature.
However, the change request included an attachment reference that had never been copied into the modern archive.
Samuel recognized the number from Lorraine's notebook.
“It may be in the external legal archive,” he said. “The same reference was used for the committee minutes.”
Jonathan contacted the archive custodian through the legal team. The custodian confirmed that the file existed but required a formal request from the airport's oversight authority before it could be released. Jonathan submitted the request immediately.
While they waited, the laboratory test continued. The team repeated the validation sequence under several conditions: with the fourth approval missing, with the emergency certificate revoked, with the recovery account disabled, and with the historical status field changed. In every case, the modern validation layer rejected an incomplete request.
By 11:32 a.m., Elena was satisfied that the known unauthorized paths had been contained.
“The system cannot issue a live permission in this configuration,” she reported. “The remaining risk is administrative. If someone restores the old configuration or reintroduces the legacy certificate, the vulnerability could return. That's why the physical equipment must remain isolated and the old authorization service must be retired permanently.”
Jonathan authorized the permanent retirement process, subject to preservation of all forensic evidence. The backup unit would be retained as evidence, not destroyed. The original legacy bridge would remain secured under independent custody until the external review was complete.
At 12:05 p.m., the external legal archive responded.
The missing file had been located.
It contained a series of internal correspondence records exchanged between Richard Bell, Lorraine Voss, and a Northbridge project director after Flight 608. The first messages discussed the need to preserve the ledger until the investigation was complete. The later messages described a plan to consolidate the original records into a single repository and use the existing exception chain to resolve inconsistencies.
One message stood out.
If the fourth approval cannot be located, the ledger must treat the previous exception as the governing authorization. We cannot allow a documentation gap to prevent the project from being closed.