Chapter 49: The Deletion Order
The migration order called the safety-log mirror a duplicate.
The neutral custodian opened the governance packet in the production aisle, where each page moved from sealed source to classified record without becoming a general exhibit. Its subject line described cleanup of duplicate legacy copies after a systems migration.
Routine language covered an unusual scope.
The attached matrix included old working files, superseded indexes, temporary transfer packages, and the independent offline safety image.
That final category was not a working duplicate. The retention policy treated it as a read-only record of safety-log content and versions.
The custodian compared the scope label with the archive holder's custody reference from the previous session. They matched. Sterling could not argue that the order referred to some other harmless copy with a similar name. The independent mirror now before the panel had been placed inside the migration scope.
Sterling's records counsel joined by secure line. "Migration teams use broad category names. Inclusion on a scope sheet does not prove deletion."
"It proves scope, not execution," I said.
It proved the mirror had been placed within the authority of an order seeking to remove duplicate copies. Whether anyone carried out every line remained a different question.
The custodian classified the issue date. It came after the incident and after Mina's automatic export receipt, while Sterling was consolidating records for its investigation.
The packet also contained a completion checklist, but the line for the offline safety image had no visible outcome. The committee could not infer deletion, preservation, or failure from a blank result. That was why Mina's separately retained objection mattered without becoming proof of what happened after she filed it.
No technical steps appeared on the review screen. The committee did not need instructions for deleting a file. It needed the authority, scope, objections, and outcome records.
The packet contained one contemporaneous objection.
Mina had filed it through the safety-policy exception route.
Her memo did not accuse anyone of fabrication. It stated that the offline image could not be treated as a disposable duplicate while participant-related safety review remained unresolved. She refused to approve removal of the last read-only version protected by the retention schedule.
Nathan called the memo a disagreement over records management.
"Did safety approve the removal?" the panel chair asked.
"This reviewer did not," he said.
"Was another safety approval obtained?"
"That requires examination of the full routing history."
Mina's lawyer allowed one narrow question.
"Did you file this exception?"
"Yes," Mina said.
"Did you authorize deletion of the offline image?"
"No."
She did not claim her refusal preserved every copy, stopped every migration, or proved someone intended to conceal a change. Her record established what she had been asked to approve and the policy reason she refused.
Her lawyer also authenticated the response receipt showing the exception entered Sterling's governance queue before the migration packet closed. No one could dismiss it as an objection invented after the current review began.
The image remained in independent custody. Mina's record proved she had not authorized its removal, and the exception remained unresolved.
Celeste said the order could still have been ordinary cleanup prepared by technical staff.
"Who authorized its scope?" Rhea asked.
The visible packet ended with an electronic authorization reference. The authorization page had been retained separately because its credential fields required independent classification before names or initials could enter the record.
Sterling requested that the page remain sealed as legal work product.
The chair ruled that advice could stay protected, but the identity and authority used to approve a records-disposition order were factual routing information. The page would open under the restricted order.
No signature appeared that day.
No certificate had been tested.
The custodian logged the authorization reference and scheduled a separate unsealing session for the next morning. Mina and her lawyer were excused; her refusal memo required no expansion.
The migration order returned to its evidence sleeve.
Its scope was now visible.
The person—or office—behind its authorization was not.