The message had been sent by Bell.
A reply from the Northbridge project director followed:
The system can be configured to accept the historical status field as sufficient validation. This will prevent the incomplete record from interrupting the reconciliation process.
Bell's response was brief.
Proceed, but ensure the function remains available until the review is finalized.
The correspondence did not prove that Bell had personally initiated the latest validation attempts. It did establish that he had approved the approach that allowed the ledger to treat an incomplete record as valid.
The external archive also contained a later message, dated several months after the project was supposedly terminated.
The recovery function must remain active. If the ledger is disconnected before the historical chain is reconciled, the executive record will be permanently incomplete.
The message was again signed by Bell.
Samuel read it carefully.
“He knew the function was still active after the termination request,” he said. “And he knew it was being retained because the fourth approval was incomplete.”
Jonathan looked at the correspondence.
“Did he understand that the system could issue new credentials?”
“We need more evidence before we can say that,” Samuel replied. “But he knew the validation function was being used to resolve an authorization gap that should have required independent approval.”
The legal team immediately preserved the correspondence and added it to the formal investigation report. Bell was notified that the new evidence would be reviewed by the external oversight authority. He was not given access to the forensic copy or the original records.
At 1:20 p.m., Jonathan returned to the incident command room. For the first time in days, the investigation had produced a complete technical explanation of the central vulnerability.
Project Horizon had been allowed to treat a historical status field as a substitute for an actual approval. A temporary recovery account had been retained beyond its authorized period. The contractor environment had been used to renew the certificate. The hidden fallback chain could search for alternate executive identities when one person refused to validate the record.
And the system had been designed to make the resulting decision look legitimate.
“Can we close the operational incident?” Daniel asked.
“We can close the immediate security incident once the external authority confirms the containment measures,” Jonathan said. “But the historical investigation continues. We still need to establish who made each change and whether anyone used the recovery function to obtain unauthorized access.”
At 2:04 p.m., Richard Bell's lawyer contacted the airport. Bell denied intentionally enabling any unauthorized access and argued that the correspondence referred only to historical record reconciliation. He requested an opportunity to provide a formal response.
Jonathan agreed to preserve that opportunity. The investigation was not a public trial, and the evidence would be evaluated through the proper process.
At 3:15 p.m., the external oversight authority confirmed receipt of the evidence and appointed an independent team to review the authorization history. Westbridge would no longer control the investigation alone.
Jonathan stood beside Elena as the laboratory workstation was shut down.
“Do you think we've found the whole truth?” he asked.
Elena considered the question.
“We've found how the system could lie. We've found who authorized the process that allowed it to lie. We haven't proved that every person who touched it understood what it could do.”
“That's enough to shut it down?”
“Yes. We don't need to prove every motive before we remove an unsafe system. We need to prove the risk exists and that the controls work.”
Jonathan nodded.
The machine had finally failed its final test.
It could no longer turn an unsigned approval into a valid permission under the controlled configuration. The hidden fallback chain had been documented. The legacy equipment was isolated, and the evidence was in independent custody.
But the final question remained: what would happen to the people whose names had been used to construct the false authorization chain?
That answer would come from the investigation, not from the machine.
The external investigation lasted several weeks. During that time, Westbridge Airport continued operating under its modern authorization framework, while the legacy equipment remained isolated and the Master Clearance Ledger was treated strictly as an unverified historical source.
The airport's governing board received weekly briefings. The public was informed that an outdated authorization system had been found to contain incomplete and inconsistent records, and that the airport had suspended its use pending an independent review. Officials avoided naming individuals while the evidence was still being assessed.
For Jonathan Reed, the weeks were exhausting. Every day brought another document, another interview, or another inconsistency that needed to be explained. The technical vulnerability had been contained, but the administrative consequences were far-reaching.
Some employees feared that their own past approvals might be questioned. Others worried that the investigation would damage Westbridge's reputation. Several senior managers argued that the airport should focus on the successful containment of the system rather than reopening decisions made years earlier.
Jonathan refused to let the issue disappear behind reassuring language.
“If we describe this as a software problem, we ignore the decisions that allowed it to continue,” he told the governing board. “If we describe it as an isolated paperwork error, we ignore the way those records were used to authorize a system. We need to acknowledge both the technical failure and the failure of oversight.”
The independent investigators interviewed Adrian Cole, Martin Hale, Victor Shaw, Lorraine Voss, and Richard Bell. They compared the original documents against the electronic records, reviewed the contractor certificate history, and examined the metadata from the recovery account.
Adrian's account was supported by the original termination request and the first version of the committee minutes. He had raised concerns about the missing fourth approval and had requested that Project Horizon be suspended. The evidence did not support the claim that he had authorized the live connection.
Martin's role was more complicated. He had approved the temporary maintenance exception that allowed the legacy bridge to remain connected during a limited window. He had failed to verify that the exception was properly closed and had assumed that the later executive review would resolve the problem. The investigators found no evidence that he personally activated the recovery account, but they concluded that his failure to confirm the shutdown had contributed to the system remaining available.
Victor had followed instructions to leave a technical module connected after Flight 608. He had also signed a decommissioning record without personally verifying that every component had been removed. His decision had helped preserve the physical infrastructure that later enabled the recovery process to be reactivated.
However, the evidence showed that Victor had retained copies of the original logs because he suspected the official records had been changed. His cooperation provided the investigation with documents that would otherwise have been difficult to recover.
Lorraine had processed the revised committee minutes and submitted the request for the temporary validation account. She had done so under executive instruction, but she had not demanded proof that the committee had reversed its original decision. The investigators concluded that her actions had contributed to the creation of the misleading administrative record, even though there was insufficient evidence that she understood the technical consequences.
Richard Bell's position was the most serious.
The correspondence established that he had known the fourth approval was incomplete. He had authorized the preservation of the recovery function and had approved the use of the historical exception chain to reconcile the ledger. His office had received the original committee decision to suspend Project Horizon, yet he had signed the later version that described the committee as having agreed to continue the project.
Bell maintained that he believed the revised record accurately reflected the committee's intention and that the recovery function was necessary to preserve historical data. He denied intending to create unauthorized access or falsify a clearance decision.
The investigators did not accept that explanation as sufficient to excuse the actions documented in the correspondence. They concluded that Bell had authorized a process that bypassed the requirement for independent approval and had allowed an incomplete authorization chain to be represented as valid.
The report did not claim to know every private motive behind his decisions. It did not need to. The documented actions were enough to establish that the process had violated the airport's authorization requirements and created a significant security risk.
Northbridge Technical Services also faced scrutiny. The contractor had maintained the recovery certificate and provided technical support for the legacy environment after the project was supposed to have been terminated. The investigators found that the contractor's access controls were inadequate and that its records did not consistently identify the individual responsible for each administrative action.
The company argued that it had acted under instructions from Westbridge executives. The investigators agreed that the airport's own failures had contributed to the situation, but they also found that Northbridge had an independent responsibility to ensure that its technical work remained within the approved scope.
The final report contained several major findings:
-
The fourth approval for the live connection had never been properly completed.
-
The original committee decision to suspend Project Horizon had been replaced by a revised record without adequate evidence of a second decision.
-
The recovery account had been retained beyond its authorized period through repeated administrative exceptions.
-
The legacy authorization system had treated a historical status field as a substitute for a verified approval.
-
The contractor environment had been used to maintain access to the recovery function.
-
The airport lacked sufficient separation between executive recordkeeping, technical administration, and authorization approval.
The report also confirmed that the investigation had found no evidence that the hidden account had been used to cause a physical security incident or disrupt a flight. That finding was important, but it did not make the vulnerability harmless. The system had been capable of creating misleading authorization records, and the airport could not rely on the absence of a known incident as proof that the process was safe.
The governing board accepted the findings and ordered a permanent retirement of Project Horizon's legacy authorization functions. All historical records would be retained in a read-only archive, and any disputed approval would require verification against original documents. Contractor accounts would be reviewed, shared administrative identities would be eliminated, and every authorization exception would have a named owner, an expiration date, and an independently documented closure.
Richard Bell's consultancy contract was suspended pending the outcome of the formal employment and legal review. Northbridge lost its access to the legacy environment and was required to cooperate with the external investigation. The airport also referred the potentially falsified authorization records to the appropriate oversight authorities for further assessment.
Martin Hale was removed from responsibility for legacy-system approvals and assigned to a role that did not involve control of the investigation. He accepted the decision.
“I should have checked whether the exception was closed,” he told Jonathan during their final interview. “I trusted the process because I thought the paperwork had been completed. That was not good enough.”
Jonathan appreciated the admission, but he did not offer easy reassurance.
“The purpose of this review is not to find one person to blame for everything,” he said. “It's to establish what each person did and what the organization needs to change.”
Martin nodded. “Then I hope we make those changes permanent.”
Victor's contractor role ended after the independent team completed its review of his actions. He provided a written account of the instructions he had received and agreed to testify if needed. He was not absolved of his own mistakes, but his preservation of the original logs was formally acknowledged as a significant contribution to the investigation.
Lorraine gave the investigators her notebook and original correspondence. Her statement became part of the official record, including her admission that she had processed the revised minutes without demanding evidence of the committee's decision. She later wrote to Adrian Cole to apologize for her part in the altered record.
Adrian accepted the apology but told her that the most important thing was ensuring the truth remained accessible.
“You cannot change what happened,” he wrote. “But you can make sure no one has to depend on a summary that hides the evidence.”
Jonathan received a copy of the final report in his office late one Friday afternoon. He read the conclusion slowly.
The report did not describe Project Horizon as the work of a single mastermind. It described a chain of failures: an incomplete approval, an unclosed exception, a revised record, an unaccountable service identity, and a contractor certificate that had remained active beyond its intended purpose. Each failure had made the next one easier.
The hidden recovery process had survived because people assumed that someone else had checked it.
And when the official record became inconsistent with the evidence, too many people chose to trust the record.
Jonathan closed the report and looked out toward the airport apron. Aircraft moved along the taxiways, ground crews worked beneath the wings, and passengers continued their journeys without knowing how close the airport had come to allowing a compromised authorization system to define what counted as legitimate.
He thought about the moment his ticket had been torn at check-in, the humiliation of being treated as though a system error had somehow become his fault, and the disbelief he had felt when the airport's own display appeared to contradict the staff member standing in front of him.
At the time, he had believed the incident would be resolved by finding the correct booking, restoring the correct record, and identifying the employee who had made the mistake.
He now understood that the torn ticket had only been the visible beginning of a much larger failure.
The real danger had been hidden in the space between what the system displayed and what the evidence could prove.
At 5:32 p.m., Jonathan received one last message from the anonymous account.
The report is public now.
He read it, then waited.
A second message arrived.
You did what the system could not.
Jonathan typed a reply.
Who are you?
For nearly a minute, there was no answer.
Then the screen displayed a final message.
Someone who should have spoken sooner.
The account went silent.
Jonathan forwarded the messages to the investigators. He did not assume the sender was a hero or a villain. Whoever they were, they had known details about the system, the hidden account, and the planned validations. Their identity might matter to the final review, and the evidence would be preserved.
He turned off his phone and returned to the report.
The investigation had cost people their positions, damaged reputations, and exposed failures that Westbridge would have preferred to leave in the past. It had also forced the airport to confront a truth that could no longer be edited out of the record.
A system could display an approval.
A database could label it valid.
An executive could insist that the paperwork was complete.