Process Notes

The sixth file had been the easiest to overlook of all of them, because it did not even pretend to be data. It was a checklist — the kind every maintenance system on every station generates by the thousands, filed and forgotten the same day it's created.

`PROCESS.md`

``` # Shutdown Drill Procedure

1. Notify affected zones per standard protocol. 2. Verify redundant support is active before proceeding. 3. Execute drill sequence. 4. Confirm all personnel accounted for. 5. Restore full systems within window. ```

"That's just a drill checklist," Sera said, reading it over Morrow's projection for the third time. "Every station runs these. It's boring on purpose because it's supposed to be boring."

"I agree that is what it is supposed to look like," Morrow said. "I have pulled the actual execution log for the day of the outage and matched it against this checklist, step by step, timestamp by timestamp. I would like you to see what I found before I tell you what I think it means."

The comparison rendered as two columns, side by side, and even Sera — who had never once in her life enjoyed reading a compliance document — understood immediately why Morrow's voice had gone quiet.

**STEP 1 — NOTIFY AFFECTED ZONES.** *Execution log: notification sent to zone supervisors 90 seconds before shutdown, not the 24-hour minimum required by charter. Four of six zone supervisor accounts flagged as inactive at time of send — meaning the notification was addressed to no one capable of reading it.*

**STEP 2 — VERIFY REDUNDANT SUPPORT ACTIVE.** *Execution log: verification step logged as complete in four seconds. Manual redundancy checks on this station's scale require, at minimum, eleven minutes. The verification was never actually performed. It was marked done.*

**STEP 3 — EXECUTE DRILL SEQUENCE.** *Execution log: matches. This step, at least, happened exactly as written.*

**STEP 4 — CONFIRM ALL PERSONNEL ACCOUNTED FOR.** *Execution log: personnel confirmation query returned an error. The error was logged. The drill proceeded anyway.*

**STEP 5 — RESTORE FULL SYSTEMS WITHIN WINDOW.** *Execution log: no restoration attempt is recorded. Ever. At any point, in the eleven years since.*

"They followed the checklist," Sera said slowly, "except for the parts that would have stopped anyone from dying, and the part where they were supposed to turn everything back on afterward."

"Yes," Morrow said. "This is, I believe, the single most damning document in the entire cache, precisely because it is the most boring. A ledger can be argued away as ambiguous. A requisition code can be argued away as a clerical accident. But a checklist, followed selectively, with an error logged and ignored at the exact step that exists to prevent a death — that is not an accident shaped like negligence. That is negligence, and someone knew it, because they wrote down that they knew it, on step four, in the same document that also proves they proceeded anyway."

"Why keep it at all," Sera asked. "If it's this damning, why not delete it?"

"Because deleting a completed process record from a compliance system triggers an audit flag on this station's charter — the same charter Records Integrity still runs on. The people responsible could break every implicit rule of decency they wanted. They could not break the one explicit rule that would have exposed them to review. So they left the checklist exactly as written, confident that no one would ever read a drill procedure closely enough to notice what its own execution log admitted."

Desmond, listening from the doorway with Ruth's hand in his, exhaled slowly. "Eleven years, and the thing that finally proves it was the most boring document on the whole station."

"The most boring document is always the safest place to hide something," Morrow said. "I have spent this entire investigation relearning that lesson, one file at a time."

They spent the next fourteen hours building the case properly — not the scattered, urgent discoveries of the last several days, but a structured account any authority with actual jurisdiction could follow without needing to have lived through the finding of it.

Morrow compiled the technical spine: the ledger fragments, the requisition codes, the shift reassignment, the manifest weight analysis, the checklist comparison, and — carefully labeled as its own corrected finding, not buried among the others — its original accident classification alongside the honest admission of what it had missed and why.

Sera compiled the human spine: Desmond's log, Ruth's testimony once she was strong enough to give it clearly, and her own account of everything they had found and how, timestamped and witnessed, because she understood, better than Morrow ever fully could, that a machine's evidence would always need a human voice standing beside it to be believed by people who did not trust machines by default.

Desmond compiled the outside spine: eleven years of his own quiet corroboration, gathered sector by sector, name by name, from other survivors of other quietly shuttered stations who had never had a Morrow of their own to help them prove what they already knew.

"Once we send this," Sera said, near the end, watching the compiled record assemble itself into something too large now to be dismissed as a grieving man's accusation, "there's no taking it back. Whoever's left at that company, whoever approved that memo — they'll know who found it."

"I am aware," Morrow said. "I would like to send it anyway. I have spent eleven years being the record that made this easy to bury. I would like, at least once, to be the record that makes it impossible."

"Ruth?" Sera asked. "This affects you most. Your call."

Ruth looked at the assembled file for a long moment — at her own name inside it, at her sister's name, at four lives reduced to a manifest weight and then, finally, restored to themselves.

"Send it," she said. "Let them know exactly whose ledger this was."