"They will listen to evidence we can present properly," Bennett replied. "They won't listen to us merely because we know we're right. Those are different things."
He looked at her sharply. "So we lose because we can't pay someone to explain a computer?"
"We may lose if we stop finding ways to establish what happened," she said. "That's why I need you to go back through the maintenance files. Not because you're some miracle child, Elijah. Because nobody else in this case has spent the time to read every page."
Pierce passed the open doorway while Bennett packed up. She paused beside Elijah and examined the printouts on his lap. "You should have taken the offer," she murmured, soft enough that only he could hear. "Tomorrow I rest my case. Friday your mother will be waiting for a sentence instead of going home."
He looked up at her. "Did you read the maintenance correspondence?"
She hesitated almost imperceptibly. "All relevant disclosures have been made."
"That isn't what I asked."
Her expression tightened. "You are in over your head, Mr. Cross. And people who don't understand their limits sometimes hurt the people they're trying to protect."
She left before he could answer. Elijah sat with those words until Bennett called his name from the door. Outside, rain had begun falling hard enough to blur the streetlights, and the buses hissed along the curb through shallow pools of water. He watched them without moving and thought about the split second of hesitation before Pierce claimed that the disclosures were complete.
He knew he might be inventing significance where none existed. He also knew that in mathematics, an assumption could survive a hundred tests and still be disproved by a single counterexample. Pierce's account of the fraud relied on several assumptions the city had never properly tested. The night before the state rested, Elijah decided he would examine every remaining file until he either found that counterexample or had nothing left to read.
He returned to the library basement, where Lila had obtained permission for him to use the archival workroom beyond ordinary closing hours. She brought him a thermos of coffee and a small plate of crackers, then left him alone with the desktop terminal. The rain struck the basement window in soft, irregular blows. Behind him, the building's old heating system hummed like a machine refusing to surrender.
At first the new files yielded nothing but disappointment. Elijah sorted the server tickets chronologically and found descriptions of ordinary maintenance: a printer that would not connect, a password reset, a failed overnight backup, and requests to restore access after the city reorganized a department. The fourth-floor terminal appeared repeatedly, but every entry seemed to refer to an isolated fault. He had been reading for so many hours that the fluorescent lines at the edge of the screen began to appear curved.
At 2:17 a.m., he found a reference to a file called INCIDENT REVIEW 18-1137. It appeared inside a routine help-desk message, where an employee had written that the matter had been escalated to senior management. The attachment field was blank, but the message included a routing identifier. Elijah copied the identifier into the file index and searched across the entire late production.