Aruna passed the directors a proposed passenger-document policy: no original ticket, identification, or physical control document could be destroyed during a dispute; any denial required a logged reason and a review path; exceptional directions from senior management would be preserved automatically. The cost estimate was modest. The question was whether management would accept limits on its ability to act without scrutiny.
The discussion turned to the Apex contract. An independent auditor described the incentive structure. Automated anomaly classification itself was not prohibited. The failure arose from combining a contractor's financial reward for availability, insufficient separation of decision-making authority, and a system that could hide the original engineer's finding. A board member asked how much performance improvement Meridian had achieved under Apex.
“According to the reported figures, twelve percent,” Aruna answered.
“And after we correct the manipulated classifications?”
“We don't know yet. The number is not currently reliable.”
The room was quiet. For months, directors had celebrated a result they could not now measure. They had awarded bonuses, praised the operations team, and described the software contract as a model for other companies. The most embarrassing disclosure was not a single bad component. It was that their confidence had been built on a dashboard that omitted contrary evidence.
Elias spoke last. He did not describe the evening he arrived or the screen that displayed his credential. Instead, he asked the board to make three commitments: preserve raw evidence independently of the systems that present it; separate safety certification from commercial performance incentives; and protect the right of frontline staff to raise documented concerns without having to find an influential supporter. None of those principles was glamorous. Each required money, authority, and the willingness to accept bad news.
One director challenged him. “You make it sound as though ordinary leadership judgment has no place.”
“Judgment has a place everywhere,” Elias said. “But a leader's judgment should determine how to respond to a technical finding, not whether the finding existed.”
The board voted that afternoon to terminate the automatic closure feature, commission a complete maintenance-record reconciliation, and create an independent safety audit committee with external members. It deferred a final decision on the full Apex contract pending litigation and operational transition. The votes were not unanimous. Two directors warned of expense and reputational damage. A third said the greater reputational damage would come from being caught making the same choice again.
After the meeting, Aruna met Elias near the elevators. “You were harder on us than I expected,” she said.
“I was trying to be precise.”
“I know. It's just that precision leaves less room to hide.”
He almost smiled. “That's one of its advantages.”
Across the lobby June noticed that the board had kept her proposed policy in the final resolution. She did not know whether the institution could change as fast as it had promised. But for once, the document describing her job contained a procedure for saying no to someone more powerful. It would have been a small reform to describe in a press release. At a check-in desk, it could be enormous.
CHAPTER 25
The Offer
The settlement proposal arrived three days before the first public regulatory hearing. Apex offered Meridian a substantial refund, free support during transition, and additional technical warranties. In exchange, the airline would agree that the observed errors had resulted from an isolated misconfiguration. A separate provision asked Meridian to support a confidential dispute process for claims arising from the affected records. Apex's lawyers insisted the language did not prevent lawful reporting to regulators. Its practical effect, however, would have made public discussion of the system's failures much harder.
Aruna circulated the offer to counsel and the independent safety committee. Several executives favored accepting it. The refund would cover much of the emergency inspection cost, and the company was losing customers. They argued that litigation would take years and might reveal even more embarrassing documents. Aruna asked whether the proposal included an independent review of the software's underlying authorization design. It did not.
“The money is attractive,” she told the executive committee. “The description of what happened is not.”
Meanwhile Iris received a letter from Apex accusing her of violating a confidentiality agreement by retaining internal records. Her lawyer explained that protected whistleblowing laws could shield relevant disclosures, though the scope would depend on the documents and jurisdiction. Iris listened carefully. She had no interest in becoming a test case for reckless disclosure. She had tried to report a specific technical concern to a lawful authority, and she wanted the evidence to be reviewed without exposing innocent passengers or employees.