Mira lost her archive access at 7:52 on Monday morning.
The notice reached her private counsel first and her council inbox second. It cited an active privacy review and ordered her to surrender her badge before entering any records area. This time the threat from October third had become an act: Victor's division had revoked her permissions.
At 8:06, a separate maintenance ticket changed the old placement server from scheduled privacy destruction to immediate sanitization.
My preservation order had been signed at 7:41.
I arrived at the North City archive with an independent process officer, an outside technician, and two sealed cases of blank storage media. Mira waited beyond the public security line. Her badge had already turned gray in the reader.
Victor stood inside the glass doors.
“You brought a witness whose access was revoked for mishandling protected records,” he said.
“I brought the records manager who can identify the system within her former duties. She will not operate it.”
I held the order against the glass. It confined us to one equipment code, three categories of noncontent metadata, and a segregated process for juvenile identities. Every other council server and all browsable family files remained outside its scope.
Victor read without opening the door. “That machine contains children’s medical and placement information.”
“Which is why the order requires identity separation.”
“An outside technician has no authority to see it.”
“The technician will image encrypted partitions without viewing content. The identity partition stays sealed under the court key. We receive only hashes, version indexes, access logs, deletion logs, and the communication-retention index for the dates in the order.”
“You cannot guarantee a mirror won't copy a name.”
“I can guarantee you do not get to erase the system while making that argument.”
Behind him, a progress bar glowed on a wall terminal.
SANITIZATION PREPARATION: 12%.
The process officer recorded the screen through the glass.
Victor followed my gaze. “Routine privacy compliance.”
“The maintenance ticket changed fourteen minutes after Mira's permissions were revoked, twenty-five minutes after the order was signed, and twenty minutes after central legal acknowledged it.”
“My office had not been served.”
“Your central legal office acknowledged at 7:46. The order binds the system custodian, not your preference for when to read it.”
He opened the doors.
The old server room sat behind two more checkpoints. Mira walked with us until the final reader rejected her badge. She did not try twice.
“From here,” I told her, “you identify what you recognize from outside the restricted line. You do not log in, touch the console, or interpret anything beyond your archive role.”
“Understood.” Her voice was steady. Her hands were not.
The technician connected a write-blocking device while the process officer filmed the ports and serial label. Victor demanded that his own administrator supervise. I allowed observation from the clean side of the room, with no keyboard access and no private communication.
He handed me a written objection before the first cable was seated. It listed nine categories of protected information and claimed the order failed to separate medical records from placement administration.
The categories were real; the attached controls defeated his conclusion.
I opened the mirror protocol attached to the order and matched each objection to a control: names and addresses to the sealed identity partition; medical content excluded from the review copy; family contact data encrypted under the court key; communication bodies sealed; public-facing indexes limited to anonymous transfer codes.
“Your protocol still copies everything,” Victor said.
“Preservation copies are not disclosure. The court container holds what cannot safely be reviewed. The working containers hold only the approved indexes and logs.”
“And if your technician makes a mistake?”
I turned to the technician. “What do you know about the children in this system?”
“Nothing.”
“What will you know after imaging?”
“Partition sizes, cryptographic values, error states, and whether the authorized acquisition completed.”
“Can you decide which record proves wrongdoing?”
“No.”
“Can you bypass the scope and open the identity container?”
“Not without the court-held key and a new authorization.”
I looked back at Victor. “The technician preserves. Mira identifies only her archive structure. I decide what goes into the application, and the tribunal decides what can be reviewed. No one person holds the whole path.”
He glanced at the progress bar, as if time might give him an argument the paper had not.
Then the sanitization bar moved to thirteen percent.
“Stop the active process,” I said.
The technician shook their head. “Stopping it through the operating system would write a new event and may alter the queue.”
“Can you isolate power without losing volatile logs?”
“Not both.”
The decision belonged to me. Preserve the running state and risk more deletion, or cut power and lose whatever existed only in memory.
I pointed to the network diagram included with the order. “Disconnect outbound network access. Keep local power. Capture volatile process data first, then suspend the sanitization task through the forensic interface. Record every write.”
Victor stepped forward. “You are choosing to leave children's information exposed.”
“The route is isolated, the identity partition encrypted, and the witness recording continuous. Whoever started deletion had more exposure than this process permits.”
The outside technician severed the network link. The preparation bar froze at fourteen percent.
For the next three hours, the room became heat, fan noise, and numbered decisions. I approved the mirror map partition by partition. The identity store was copied into a sealed encrypted container whose key went to the court custodian. The version archive produced hashes and file names while child content stayed sealed. The access and deletion logs went into a second container. The communication index copied headers, retention markers, senders by office code, and subject lines within the authorized dates; message bodies remained sealed unless separately approved.
At one point, the version partition reported a damaged block. The technician offered two methods: retry the sector repeatedly, which might stress the aging drive, or record the failure and continue before returning with a lower-speed pass.
“What is downstream of it?” I asked.
“The directory map says historical list versions. I cannot see content.”
Mira leaned toward the boundary line but did not cross it. “That range held quarterly working files when I managed the queue.”
If we lost the rest of the mirror chasing one damaged block, Victor would get the cleanest possible failure.
“Record the sector, continue the first pass, then retry at lower speed after every other authorized partition is sealed,” I said.
The technician documented my instruction. It meant accepting an imperfect first image instead of performing competence for the camera.
Victor read the first-pass warning and called the mirror incomplete. He left with his observer after the observer signed only two facts: the identity container had not been opened, and the damaged sector had been recorded. The order did not entitle them to remain inside the independent custodian's recovery review.
Forty minutes later, the slower pass recovered the block.
Mira let out a breath. I waited for the recovered data's matching hash before calling it a victory.
Mira identified the naming convention for R-16 and R-17 from behind the line. She confirmed which queue she had managed and which version markers she had personally seen. When the index displayed finance or security folders, she said, “Outside my duties,” and stopped.
Victor tried three times to expand her answer into misconduct. I ended each attempt.
“She is here to identify records, not explain your motive or hers.”
At noon, the deletion log populated.
The deletion log exposed the sanitization ticket as an accelerated act: an underlying manual command had issued at 7:55 from a placement-administration terminal. That instruction came fourteen minutes after the order was signed, nine minutes after central legal acknowledged it, and three minutes after Mira's permissions were revoked. The maintenance system displayed the switch at 8:06, eleven minutes after the command. The command targeted the old version partition and communication-retention index first. It left the active child files for last.
Privacy destruction designed to protect children would have begun with identity content. This sequence began with the records that could explain institutional action.
I asked the technician to state only the observable fact for the camera.
“The deletion priority was changed after the preservation order issued. The command source is a placement-administration terminal class. This image does not identify the individual user.”
Victor held his expression still, but sharp iron cut through the scent of expensive wool.
Adrian kept his guards away. At 12:18, the custodian delivered a lawful facility-access record from his office showing who held physical authority over the room. It arrived through the evidence channel without an instruction attached. I accepted only the record.
The mirror completed at 2:43. Each container received a separate hash, seal, and custody form. The final recovery status remained sealed with the custodian; Victor received notice that the authorized acquisition had occurred, not whether the damaged historical range had been recovered in full. Mira signed only that the folder labels and version sequence matched the system she had managed before her access was revoked.
“Do I get my badge back?” she asked Victor.
“That is under review.”
The gray badge in her hand already answered him.
Outside, her protected transport waited under the court arrangement. No pack vehicle. No Kane crest.
I stayed for the index review.
R-16 and R-17 appeared with the same hash relationships Mira's work copy had preserved. The server image added deletion events and a restricted communication-retention entry. The raw signet log and the second key's user remained beyond it, but the image gave us a path to seek a particular communication without pretending we already had its body.
The final retained header had been created two days before Julian's public release. Sender: placement administration office. Recipient: security committee vice-chair office.
I sealed the header index before requesting any message body. The subject justified the next application while leaving the communication itself still to be obtained.
The subject line was seven words.
LET JULIAN RELEASE THE CLEAN VERSION FIRST.