The first session of the hearing began with a procedural argument. Kestrel's counsel asked the panel to exclude Evelyn's analysis because some source material came from internal archives. Jonah replied that the evidence had been obtained during her authorized employment and that independent measurements reproduced the critical pattern. The chair permitted the testimony, reserving a decision on disputed documents.
Evelyn took the witness seat and explained the flaw without exaggeration. She used a simple example: imagine two clocks, both wrong by the same amount, agreeing with each other and persuading a third device to trust them. Agreement was not accuracy. Her job had been to identify circumstances in which the system was too willing to confuse the two.
Richard's attorney asked whether any aircraft had crashed because of the anomaly. “Not to my knowledge,” Evelyn said. “That is not the standard for reporting a known risk.”
“Isn't this theoretical?”
“The failure condition was reproduced in controlled tests.”
“Did you personally see it happen on a passenger flight?”
As the internal review expanded, Evelyn insisted on interviewing frontline staff without their supervisors present. She asked each person a version of the same question: What happens here when a customer with influence wants you to bend a rule? The answers were varied and often uncomfortable. One employee recalled a gate reassignment made after a celebrity's assistant threatened to post online. Another described being told to hide a wheelchair delay from the morning performance report. A third said nothing at all until Evelyn promised that silence would not be treated as loyalty. Gradually a pattern emerged. The company had not lost its policies. It had trained people to believe that following the policies might leave them alone when complaints reached senior management.
“No. I would have preferred that it remain impossible for any passenger flight to encounter it.”
In the gallery, Victoria sat beside Martin and listened with growing discomfort. She knew nothing about sensor fusion, but she understood the basic question. Someone had identified a danger. Someone else had decided a warning was inconvenient. She remembered the boarding pass and the way she had demanded that the system bend around her wishes.
Ruth Chen agreed to meet in a borrowed office rather than the hotel lobby. She brought a canvas bag filled with notebooks, each labeled with a month and a sequence of initials. For nearly a decade she had supervised maintenance checks at a facility where Kestrel components moved through inspection. Her concern had begun not with the sophisticated navigation algorithm but with the ordinary process for closing a work order. A test that required follow-up could be marked as administratively complete while technical work continued elsewhere. Used honestly, the method prevented scheduling software from displaying duplicate tasks. Used carelessly, it made incomplete work look finished to outsiders.
Ruth showed Evelyn an example. A test fixture had produced an out-of-tolerance reading during cold-weather calibration. The equipment was removed for inspection, but the primary work order was closed because a replacement fixture had been assigned. The follow-up task existed in a separate maintenance system. When managers exported completion statistics, they received the primary work-order status but not the dependent task. Ruth had raised the issue in a weekly meeting and been told that a dashboard was only a dashboard. Then that same dashboard appeared in a presentation as evidence that all validation activities had been completed.
Jonah asked whether she had tried to correct the public account. Ruth opened her notebooks to a page bearing three meeting dates. She had sent corrections to two directors and a quality officer. One director acknowledged receipt. Another replied that the matter was beyond her remit. The quality officer proposed a reconciliation, then left the company before it was scheduled. Ruth did not claim to know anyone's motive. She knew that the final presentation still omitted the dependent task. Evelyn thanked her for making the chain of events precise.
The review team arranged a demonstration using an offline copy of the maintenance software. Samir reconstructed the two-system workflow while Priya provided the test identifiers. A temporary network failure forced them to postpone the first run. Jonah grumbled about the irony. Evelyn found it useful. They were investigating assumptions about systems that appeared seamless only when everything worked. During the second run, Samir showed how an export could report a test as complete even while a linked task remained open. The demonstration did not prove that every closure was misleading. It established a mechanism that the panel could verify independently.