"What am I looking for?" Victoria asked.
"A difference that shouldn't be there," Caleb said. "Not just any difference. The first one that changes what the aircraft thinks it knows about itself."
He set the records side by side. The last successful startup was uneventful, a long sequence of acknowledgments moving from one system to another. Then came the post-update attempt, with the same orderly beginnings and an abrupt absence where one subsystem's acknowledgment should have appeared. The summary marked that subsystem healthy because its individual self-check had passed. The full record, however, showed that a required handoff had never happened.
Caleb stopped scrolling. He did not say anything immediately. Instead, he read backward, then forward, then returned to the previous successful record. He asked Noah to show him the timestamp at which the maintenance package had been installed and the moment the aircraft had first entered the no-start condition. Everything aligned.
"There," Caleb said at last. "That's where the story changes."
Noah leaned close enough that their shoulders nearly touched. "The unit reports it completed its own check, but it doesn't send the next acknowledgment. Why wouldn't it?"
"I can think of several reasons. A damaged component. An interrupted state restoration. An update that left one part of the system believing its work was already complete." Caleb traced the corresponding lines with his finger.
"You said the update was verified. What did the verification actually verify?"
Noah pulled the installation certificate. The file was valid, the signed software package matched the approved release, and the application had completed without an interruption recorded by the standard installer. Caleb read every line and nodded. There was nothing wrong with the software package itself. The failure was almost certainly in the state the aircraft had retained while installing it.
"The report is true," he said. "That's what makes it dangerous. The package installed. Nobody lied about that. But the report doesn't establish that the system returned to a clean operating state afterward. Those are two different claims."
Victoria had spent a career listening to executives make a similar distinction disappear by accident or convenience. She heard the trap immediately. "So we've been accepting evidence that answers a smaller question than the one we're asking."
"Exactly."
Caleb explained it the way Marcus would have explained it to a ten-year-old in their garage. An aircraft's electronic systems did not all wake at once, he said; they checked conditions, recorded states, exchanged confirmations, and waited for other systems to become ready. During the update, a little piece of persistent information had apparently survived when it should have been reset. To a later diagnostic, it looked as though an early stage had already completed its work. In reality, the stage had never performed the handoff needed to allow the full sequence to continue.
"It's like a runner arriving at a race and discovering the official clipboard already says he finished," Caleb told her. "He doesn't know the entry is wrong. Everybody checking the clipboard assumes the race is over. Meanwhile the next runner never receives the baton."