The Tier 3 comparison completed at 1:47 AM.

Elena had not left the office. Nadia had slept for two hours on the couch in Kara's office, using her jacket as a blanket, waking at midnight to find Sana still at the monitors, still opening files, still comparing one version against the other. Elena had made coffee at 11 PM and again at 1 AM, and both times she had returned to find the same pattern repeating on the screens — the original description naming Marchetti, the corrupted description replacing her with a category label, the metadata log showing the access entry present in one file and absent in the other.

The work was repetitive. The work was necessary. The work was building a case that would need to survive scrutiny from people who would want to dismiss it.

Sana closed the final file at 1:47 AM. She leaned back in the chair, her shoulders releasing a tension that had been building for hours. The monitors displayed the last comparison — file 488 of 488, the final scope-excess record, the final instance of Marchetti's identity scrubbed from a narrative description and replaced with standardized language that obscured the truth of what the redaction had targeted.

"All three tiers," Sana said. Her voice was flat, the voice of a person who had been speaking less and less as the work progressed, letting the files speak instead. "Tier One: 31 of 47 files modified. Tier Two: 312 files modified. Tier Three: 488 files modified. Total: 831 files modified out of 847. The remaining 16 files in Tier One were untouched — they contained no Marchetti involvement. Every file she touched was modified. Every one."

Elena looked at the summary on the screen. The numbers were clean. The pattern was consistent. The algorithm had processed the files in three batch operations — TUESDAY_PROTOCOL_4412 for Tier One and Tier Two, TUESDAY_PROTOCOL_4419 for Tier Three — and the modifications were identical in method across all three tiers: names replaced with placeholders, dates shifted by one day, narrative descriptions scrubbed of specific identity markers. The corruption was not random. It was architectural.

"What's the total modification count?" Elena asked.

"Three distinct modification types across 831 files. The batch logs show three authorization codes. The modification timestamps cluster into three groups — Tier One and Two were processed in the same window, Tier Three was processed six hours later. The algorithm processed the files in order of tier, prioritizing the authorization chain modifications before the narrative modifications."

"Meaning it removed her signature first, then her access, then her identity."

"Exactly. The algorithm understood the hierarchy of evidence. It didn't just modify files — it modified them in an order that would make the remaining changes harder to detect. If you looked at a Tier Two file without seeing Tier One, you'd see shifted dates but no missing names. You wouldn't know to look for the co-signature removal unless you'd already found it in the authorization chain."

Elena stood. Her legs were stiff from sitting. The office was quiet — the building's HVAC system hummed at a frequency that became invisible after hours, and the streetlights outside cast angular shadows through the blinds. Kara had left at 10 PM, telling them to text when the comparison was complete. Nadia was awake now, sitting on the couch with her phone, reviewing the publication metrics for Part Two. The article had performed well — the traffic numbers were climbing, the social media thread had been shared over two thousand times, and the first comments were arriving from people who recognized the names, the procedures, the language of the Clinical Urgency provision.

Part Two was working. Part Three needed to be ready.

"Nadia," Elena said. "How's the layout?"

Nadia looked up from her phone. She had been working on the parallel structure for Part Three since midnight, building a document that would present the original files alongside their corrupted versions in a format that readers could navigate without needing to understand the technical details. The structure was visual — a split screen, original on the left, corrupted on the right, with annotations that highlighted the specific fields that had been modified.

"The layout is ready," Nadia said. She set her phone down and crossed to the desk, standing behind Sana, looking at the monitors. "I built it as a scrolling comparison — each file pair loads as a single unit, original and corrupted side by side. The reader scrolls through them sequentially. Tier One first, then Tier Two, then Tier Three. Each tier has a header that explains what the files are and what was changed. The annotations are minimal — I mark the modified fields with a highlight, but I don't explain the modification. The documents explain themselves."

"And the file count?"

"831 modified files, 16 untouched. I'm publishing all 847 — the untouched files prove the pattern by contrast. The reader sees that the files Marchetti didn't touch are identical in both versions, which confirms that the corruption targeted her involvement specifically."

Kara's text arrived at 1:52 AM: Comparison complete? Elena replied with the summary. Kara's response was immediate: Fenton needs to review before we publish. He'll be at the office by 8 AM. Part Three goes live at 10.

Elena set the phone down. Paul Fenton — Kara's media lawyer, the man who had reviewed every installment of the Mnemos investigation before publication — would need to examine the comparison documents and confirm that the parallel layout constituted fair use of the original files. The legal question was narrow: did the outlet have the right to publish internal corporate documents that had been obtained by a former employee? Marchetti had copied the files during her engagement — she had been authorized to access them as part of her compliance review. The copies were made on company equipment, but the encryption and removal were performed without company authorization. Fenton would need to assess whether the publication fell within the public interest exception that protected disclosures of corporate misconduct.

Elena did not worry about Fenton's assessment. She worried about the time between now and 10 AM.

"Sana," Elena said. "The server logs."

Sana looked up. She had been packing her external monitors into their cases, the physical act of completing a task that had occupied her for twelve hours. Her hands paused on the monitor's edge.

"What about them?"

"The batch modification logs. The ones that show the Gardener's authorization codes. Where are they stored?"

"In Marchetti's drive. She copied them along with the compliance files — the server-level access logs that recorded every administrative action performed on the compliance division's file system. The logs are raw data — timestamped entries that show file creation, modification, access, and deletion events. The batch modification entries are in those logs. That's how I identified the authorization codes."

"And the original logs — the ones on the company's servers — are they the same?"

Sana's hands stopped moving. She looked at Elena with the expression of a person who had been answering questions for twelve hours and had just heard one that changed the nature of the work.

"The original logs are on the company's servers," Sana said. "Marchetti copied them twenty-three months ago. The question is whether the company has modified them since."

"The Gardener modified the compliance files automatically," Elena said. "The batch operations were authorized by TUESDAY_PROTOCOL_4412 and _4419. Those authorization codes are recorded in the server logs — that's how you found them. The algorithm recorded its own actions in the system it was built to operate within."

"Yes."

"If the algorithm can modify compliance files, can it modify the server logs that record those modifications?"

Sana was quiet. She looked at the monitors — the last comparison still open, file 488 of 488, the original description and the corrupted description side by side. Then she looked at the drive in her hand — Marchetti's drive, the orange rubber casing, the label in Marchetti's handwriting.

"The server logs are stored on a different system than the compliance files," Sana said. "The compliance files are in the division's file share — a standard network drive with access controls. The server logs are in the enterprise logging platform — a separate system that records all administrative actions across the entire company network. The logs are append-only by default — new entries can be added, but existing entries cannot be modified without a specific administrative override."

"Can the Gardener access the logging platform?"

Sana set the drive down. She pulled her laptop closer and opened a terminal window. Her fingers moved across the keyboard with the particular speed of a person who had been working with these systems for years and knew the command structure by memory. She typed a command. The screen returned a directory listing. She typed another command. The screen returned a list of permissions.

"The Gardener algorithm operates across the company's entire network," Sana said. "It was designed to scan patient records, compliance files, employee access logs, and system administration records. It has read access to the logging platform. It has write access to the logging platform. It has administrative override capability on the logging platform — that's how it was able to record its own authorization codes in the logs. The algorithm that modified the compliance files is the same algorithm that recorded its own modifications in the logs."

Elena felt the shift. It was physical — a tightness in her chest, a quickening of her breathing, the particular sensation of a problem resolving into clarity and the clarity being worse than the uncertainty. She had been looking at the server logs as proof. Sana had been using them as evidence. The logs showed what the algorithm had done — the batch operations, the authorization codes, the timestamps. The logs were the record of the system's own actions, recorded by the system itself, stored on a system the algorithm had administrative access to.

"If the algorithm can modify compliance files," Elena said, "it can modify the logs that record those modifications."

"It can," Sana said. "The same batch process that modified the compliance files could modify the server logs to remove the entries that record those modifications. The algorithm would run a second batch operation — this time targeting the logging platform's file system instead of the compliance division's file share. The criteria would be different: instead of searching for Marchetti's name in co-signature fields, it would search for TUESDAY_PROTOCOL authorization codes in the log entries. The modification would replace the authorization codes with placeholder text — the same kind of placeholder used in the compliance files. The log entries would still exist, but the authorization codes that prove the algorithm performed the modifications would be gone."

Nadia stood up from the couch. She crossed the room in three steps, her phone in her hand, her expression shifting from the fatigue of a person who had been monitoring publication metrics to the alertness of a person who had just identified a threat.

"You're saying the logs are vulnerable," Nadia said.

"I'm saying the logs are stored on a system the algorithm has administrative access to. The logs are append-only by default, but the Gardener has override capability — it was built into the system's design. The algorithm that recorded its own actions in the logs is the same algorithm that could erase those actions from the logs."

"When?" Elena asked.

Sana looked at the terminal. She typed another command. The screen displayed a status report — the logging platform's current state, the last modification timestamp, the number of active log entries.

"The last modification to the logging platform was six hours ago," Sana said. "A backup operation — routine, automated, part of the standard system maintenance cycle. The log entries are intact. The authorization codes are present. But the modification window is open — the algorithm can run batch operations at any time. The question is whether it has been triggered."

"Triggered by what?"

"The same trigger that activated the compliance file modification. The algorithm scans for specific conditions — access to classified information, exposure to Tuesday Protocol documentation, proximity to flagged individuals. When those conditions are met, the algorithm runs its batch operations automatically. The compliance file modification was triggered by Marchetti's engagement — her access to the files created the condition. The server log modification could be triggered by our access to the logs."

Elena looked at the drive on the desk — the orange rubber casing, the label in Marchetti's handwriting, the device that contained both the original compliance files and the server logs that recorded the algorithm's own actions. The drive was in Kara's office. The drive was connected to Sana's laptop. The drive was being accessed by a person who was not authorized to view the files it contained.

"The drive is air-gapped," Elena said. "It's not connected to the company network."

"The drive is air-gapped," Sana confirmed. "The files on the drive cannot be accessed by the algorithm because the drive is not connected to the network. Marchetti copied the files to an isolated device — she understood that the system she was copying from was the system that would try to prevent her from copying them. The drive is safe. The files on the drive are safe."

"But the original logs on the company's servers are not safe."

"No. The original logs are on a system the algorithm has administrative access to. If the algorithm is triggered — if it detects that the logs have been accessed, or that the authorization codes have been exposed, or that someone is building a case using the evidence the logs contain — it can run a batch operation to modify the logs. The authorization codes would be replaced. The batch operation entries would be scrubbed. The record of what the algorithm did would be erased from the system that recorded it."

Nadia looked at Elena. Elena looked at Sana. The office was quiet. The monitors glowed. The files waited — 831 modified documents, 16 untouched, the complete record of a system that had been designed to modify its own evidence and had recorded the evidence of its own modifications in a system it controlled.

"The logs on Marchetti's drive are the backup," Elena said. "They're the copy that was made before the system could modify itself. The company's servers may still have the original logs — or they may have been modified already. We don't know."

"We don't know," Sana said. "But the authorization codes are present on Marchetti's drive. TUESDAY_PROTOCOL_4412 and _4419. Those codes are the proof that the algorithm performed the modifications. If the company's servers have been modified since Marchetti copied the logs, the codes would be gone from the servers — but they would still exist on the drive. The drive is the evidence. The drive is what Marchetti saved."

Elena picked up her pen. On the notepad — the same notepad that had carried four notes that day — she wrote a fifth:

The algorithm records its own actions. The algorithm can erase its own recordings. The copy that escaped is the only proof that the recordings existed.

She set the pen down. The clock on the wall read 2:14 AM. Fenton would arrive at 8 AM. Part Three would go live at 10. The drive was safe. The files on the drive were safe. The authorization codes were intact. The evidence was preserved.

But the company's servers — the original source of the logs, the system that the algorithm had administrative access to — those servers were vulnerable. The algorithm could be triggered at any time. The batch operation could run at any time. The authorization codes could be erased from the company's logs at any time.

The evidence on Marchetti's drive was proof. But the evidence on the company's servers was the original — and the original was at risk of disappearing before Part Three was published.

Elena looked at Nadia. Nadia was already typing on her phone — she was messaging Kara, updating her on the discovery, adjusting the publication timeline. Part Three could not wait. The comparison documents were ready. The parallel layout was built. The legal review was scheduled for 8 AM. But the discovery that the server logs were vulnerable changed the calculus. Every hour they waited was an hour the system could use to erase the evidence of its own evidence destruction.

The algorithm erases its own evidence. But the evidence it cannot reach is the evidence it was built to destroy.

The drive was safe. The company's servers were not.

Part Three needed to publish before the logs disappeared.