Rachel requested the contract amendment's approval history. It showed Simon Kells's electronic approval and Owen Beck's operational acknowledgment. Eleanor Shaw's name did not appear.
Owen was interviewed again. He admitted that the business team had pushed for a rapid launch but insisted he believed every proposed seat change would require human confirmation.
“Where is that requirement written?” Rachel asked.
Owen looked through the packet. “It was discussed.”
“By whom?”
“I don't remember everyone.”
“Did you verify it was implemented?”
He said nothing for several seconds. “No.”
Tessa explained one more detail about the test environment. During early demonstrations, the vendor had used invented travelers with neutral histories. Later, business reviewers requested realistic profiles drawn from de-identified customer patterns. The change made the simulations more convincing, but it also allowed the model to learn which kinds of travelers were less likely to complain. Tessa had asked for a fairness review. The request remained open when the pilot launched.
Rachel assigned a separate specialist to examine whether the selection criteria produced unequal effects across passenger groups. She emphasized that the team should not infer sensitive characteristics from individual records or make claims before a careful analysis. Priya agreed. The underlying wrong was already clear: a confirmed booking should not be canceled merely because a customer was predicted to resist less. A broader impact analysis could help determine the full scope of the harm.
That evening Marisol wrote a short account for her union representative about the training session. She described the instructor's response without guessing at his motives. She wanted frontline workers protected when they questioned unreliable systems. Her representative told her that several other agents had raised similar concerns and asked whether she would help collect suggestions for safer procedures. Marisol agreed, provided passengers' private details remained protected.
The answer did not make him the sole author of the harm. It did make his oversight failure impossible to ignore.
Late that night Felix found a series of system messages sent during the original launch. One warned that human confirmation was disabled. Another recorded a manual override approving continued operation.
The override was associated with a credential issued to Simon Kells's office.
Priya stared at the timestamp. It fell forty-three minutes after Tessa's report had been downgraded.
The system had warned its operators. Someone had decided to proceed anyway.
The airline's first public statement acknowledged that an experimental inventory tool had improperly affected confirmed reservations. It promised an independent review and invited affected passengers to contact a dedicated support team. The statement did not name Nora Vale, and she was relieved. She had never wanted strangers to know her family's medical circumstances.
Still, the story spread quickly. Travelers posted screenshots of canceled bookings, changed seat assignments, and confusing notices. Some accounts concerned ordinary operational disruptions unrelated to the pilot. Rachel urged the review team not to treat every complaint as evidence of the same failure. Each case needed its own records, timeline, and explanation.
Nora read the statement aloud to Daniel. He listened, then asked a question she had not expected.
“Do they say sorry?”
“Not in those words.”
“Then they should.”
She smiled sadly. Daniel had always been direct. His illness had made him more patient with people and less patient with evasions.
A support representative called Nora later that day and offered reimbursement for her replacement travel expenses, a payment for the delay, and a written apology. Nora accepted the expenses but asked to review the rest in writing. She wanted to be sure the payment would not require her to stop cooperating with the investigation.
The representative assured her that it would not. Nora requested the assurance in the agreement itself.
At headquarters, Priya and Felix were reviewing the list of affected travelers. One was a student named Amara Okafor who had missed a scholarship interview. Another was a home-care worker, Luis Romero, who had lost a day's wages after being rebooked. A retired teacher named Harold Bell had missed his sister's memorial service.
The stories were different, but the records shared a pattern: valid confirmations had been restricted shortly before departure, and seats had been released into a premium inventory channel. The airline's systems had then recorded the travelers as voluntarily absent or ineligible to board.
“That label follows people,” Priya said. “It changes what customer service thinks happened.”
Felix agreed. “The correction has to reach every downstream system, not just the reservation database.”
Rachel asked the review team to map where the inaccurate status had traveled. It appeared in refund workflows, complaint histories, loyalty profiles, and performance reports used to evaluate airport staff. The error had become many errors, each reinforcing the others.
Marisol discovered that her own gate performance record contained a negative notation for an extended boarding dispute. The notation did not mention that she had helped uncover a faulty restriction. She requested a correction, attaching her contemporaneous notes and the case reference number.
Her supervisor initially said the score was automated and could not be changed. Marisol asked for the policy supporting that answer. Two days later, the notation was removed and the airport manager began reviewing similar cases.
The review's growing scope troubled Eleanor Shaw. She called Rachel into her office and asked whether the airline should delay the conference entirely.
“That's a leadership decision,” Rachel replied. “But the company should not claim the issue is resolved while the investigation is active.”
Eleanor looked at the revised speech. It now spoke about accountability rather than perfection. She asked Rachel whether she should resign.
“I can't answer that for you,” Rachel said. “I can tell you that accepting responsibility requires more than choosing a dramatic consequence. We need decisions that protect customers and preserve evidence.”
Eleanor sat with the answer. She had built her career on speed and operational discipline. She had been proud of making large projects move quickly. Now she was learning how speed could become a way to avoid asking whether the project should move at all.
Meanwhile, Simon Kells retained outside counsel. Through his lawyer, he said he had approved a technical override based on assurances that the pilot would affect only simulated inventory. He denied directing anyone to conceal warnings.
Rachel asked the independent examiner to test that claim against the messages. One email from Tessa's team clearly described confirmed passenger records. Another, sent to Simon's office, requested acknowledgment of the risk. The reply stated that commercial validation would proceed and that the launch team should avoid unnecessary escalation.
“That's not the same as an instruction to conceal,” Felix said.
“No,” Priya answered. “But it tells us what they were willing to call unnecessary.”
The vendor's commercial director also faced questions. She acknowledged that revenue targets had created pressure but argued that the airline controlled production deployment. The airline pointed to the vendor's technical design. Each side could describe the other's role in detail and its own in generalities.