Chapter 34: The Next Thirty Days
Elena stared at the spreadsheet on her laptop screen. The patient list glowed in the dark office—forty-seven rows, each one a life altered by the Tuesday Protocol. The last entry was different. The name column was blank. The authorization code was TUESDAY_PROTOCOL_4420. The status was Scheduled.
She looked at the clock: 11:02 PM. Thirty-six hours and fifty-eight minutes until the redaction order deadline. But that was the deadline for the past. The scheduled entry was a deadline for the future.
The office was quiet. Kara had gone home at 10:45 PM, promising to return at 6:00 AM to finish the redactions. Nadia was in the conference room, asleep on the couch, her notebook open on her chest. Sana was in the server room, monitoring the network analyzer. Fenton had left at 10:30 PM with a warning: "If another motion comes in tonight, I need three hours notice."
Elena picked up her notepad. The eighteenth note was still there, written in her precise hand. She added a nineteenth:
11:02 PM — the scheduled entry is not a historical record. It is a future appointment. The Protocol is ongoing. The next redaction is pending. The deadline is not Thursday close of business. The deadline is the next thirty days.
She closed the notepad. The drive was still plugged into her laptop. The file directory was visible—the directories exposed by the probe. The probe had stopped at 9:15 PM, but the damage was done. Someone had mapped what they had.
Elena navigated to the patient list again. She looked at the blank name. The authorization code was sequential—each one a number in a series. The previous entry was TUESDAY_PROTOCOL_4419, dated two months ago, status Completed. The entry before that was TUESDAY_PROTOCOL_4418, dated three months ago, status Completed. The pattern was clear: the Protocol redacted one person every thirty to forty-five days.
She scrolled up the list. The entries were consistent—each one a patient, each one a date, each one a completed redaction. The names were varied: Marchetti, Brennan, Herrera, and others she did not recognize. The dates were specific—month, day, year. The authorization codes were sequential, each one a number in a series that spanned four years.
Elena looked at the completed entries. They had names. The scheduled entry did not. Why was the name blank?
She opened the notes column for the scheduled entry. The text was brief: Subject has accessed internal documentation regarding the Tuesday Protocol. Clinical Urgency authorization pending.
Elena recognized the phrasing. It was identical to the language in the Clinical Urgency memos. The authorization was pending. The redaction was scheduled. The patient was unknown.
She thought about the other patients on the list. Marchetti. Brennan. Herrera. The names she had replaced with identifiers in Part Four. The names that were now numbers in a redacted article. The names that proved the pattern.
But the scheduled entry had no name. It was a placeholder. A waiting room.
Elena closed the spreadsheet. She looked at the clock again: 11:07 PM. Thirty-six hours and fifty-three minutes until the redaction order deadline. But the redaction order was about the past. The scheduled entry was about the future.
She needed to think about both.
At 11:15 PM, Sana knocked on the office door.
"The probe is back," she said. Her voice was low, steady. "Different signature. Same target. It's mapping the drive's encryption layer now."
Elena followed her to the server room. The analyzer screen was glowing—a graph of incoming connections, a spike in traffic from a new IP address. The probe was methodical—it was probing the drive's encryption, testing the key strength, mapping the security architecture.
"Is it the Gardener?" Elena asked.
"No. The Gardener uses a specific signature. This is different. This is a brute-force probe. It's testing the encryption."
"Can it break it?"
"Not quickly. The drive uses AES-256. A brute-force attack would take years. But the probe is not trying to break the encryption. It's mapping the encryption. It's building a profile of the drive's security."
"Why?"
"To prepare for a legal motion. If they know the encryption strength, they can argue that the drive's contents are protected by trade secret law. They can argue that the encryption proves the data has commercial value."
Elena watched the probe. It was moving through the encryption layer—probing, testing, mapping. The drive was a vault. The probe was a locksmith's apprentice.
"They're building a case," Elena said.
"They're building a wall," Sana said. "Every probe, every motion, every precedent—it's all part of the same architecture. They're not trying to stop you from publishing. They're trying to make sure that after you publish, you can never publish again."
Elena looked at the screen. The probe was still active—a steady stream of requests, each one testing a different encryption parameter. The drive's security was being mapped, cataloged, analyzed.
"They know we have the Clinical Urgency memos," Elena said.
"They know. They know we have the patient list. They know we have the Tuesday Protocol documentation. They know everything."
"And they're preparing for Part Five."
"They're preparing for Part Six. The Tuesday Protocol documentation is the core. The memos are the evidence. The patient list is the scope. They know that."
Elena was quiet. The probe continued its work. The encryption was strong, but the map was being drawn.
"We need to move the data," Elena said. "We need to copy the drive. We need to ensure the evidence survives."
"The drive is already backed up," Sana said. "I mirrored it to an encrypted cloud server last night. The original is here. The copy is there. If they seize the drive, the evidence survives."
"Good."
"But the copy is only as secure as the cloud server. If they probe that too—"
"Then we need a third copy. Physical. Offline. Something they can't probe."
Sana nodded. "I have a secure location. A safety deposit box at a bank in Bethesda. The key is with Fenton."
"Then we're covered."
"For now."
At 11:30 PM, Elena returned to the conference room. Nadia was awake, sitting on the couch with her notebook open.
"The probe is back," Elena said.
"I heard," Nadia said. "Sana texted me."
Elena sat down at the table. The stack of Clinical Urgency memos was still there—twenty-three pages, each one an authorization of emergency redaction without consent. The memos were the evidence for Part Five.
"Part Five is ready," Nadia said. "Kara reviewed it. Fenton reviewed it. It's clean."
"Good."
"But there's a problem."
Elena looked at her.
"The memos are dated," Nadia said. "The dates are specific. The order requires redaction of 'dates of redaction procedures.' The memos have dates of redaction procedures."
Elena was quiet. She had not thought about that.
"The memos are internal documents," she said. "The order covers the article. The memos are separate."
"The order covers 'patient-identifying information derived from the authorization codes.' The memos contain authorization codes. The dates in the memos are linked to the authorization codes. The dates are patient-identifying information."
Elena looked at the memos. The dates were specific—March 12, April 3, January 17. The dates of the procedures. The dates that proved the pattern.
"We redact the dates too," Elena said.
"We redact the dates. We replace them with relative timeframes. 'In the weeks prior to publication.' 'Several months earlier.' 'In the preceding quarter.'"
"That weakens the chronology."
"The chronology is weakened. But the evidence is intact. The signatures are intact. The reasoning is intact. The pattern is intact."
Elena looked at the clock. 11:35 PM. Thirty-six hours and twenty-five minutes until the redaction order deadline.
"We publish Part Five tomorrow morning," Elena said. "We publish Part Six tomorrow afternoon. We comply with the redaction order by Thursday close of business. We publish everything before the precedent solidifies."
"The timeline is tight."
"The timeline is necessary."
At 11:45 PM, Elena's phone buzzed.
She looked at the screen. Unknown number. A text message:
Dr. Marsh — I am Patient 47. I am the next name on the list. We need to talk.
Elena stared at the message. Her hands did not shake. Her breathing stayed even. She read it twice, then a third time, looking for something wrong beyond the obvious.
She showed the message to Nadia.
Nadia read it. Her eyes widened.
"Patient 47," she said. "The scheduled entry."
"The blank name."
"They're reaching out."
"They're reaching out."
Elena looked at the message again. The text was precise, clinical. It used her title. It used the list terminology. It referenced the authorization code without naming it.
She typed a reply:
Who is this?
The response came in thirty seconds:
A Reeve employee. I accessed the Tuesday Protocol files last week. The Gardener flagged me. I am scheduled for redaction in thirty days. I have documentation. I need to get it out.
Elena looked at Nadia. Nadia looked at Elena.
"It's a trap," Nadia said.
"It could be."
"It's Reeve. He's monitoring the drive. He's probing the encryption. He's building a wall. And now he's sending a message."
"Why?"
"To control the narrative. To steer the investigation. To make sure you publish what he wants you to publish."
Elena looked at the message. The text was precise. The grammar was correct. The tone was clinical.
Or it was a person who was afraid.
She typed another reply:
What documentation?
The response came in forty-five seconds:
Gardener algorithm logs. Authorization chains. Patient list updates. The next ten scheduled redactions. I have everything.
Elena looked at Nadia.
"If it's real," Nadia said, "it's the smoking gun."
"If it's real."
"And if it's not?"
"Then it's a trap. And we walk into it."
Elena looked at the clock. 11:52 PM. Thirty-five hours and forty-eight minutes until the redaction order deadline. The scheduled entry was no longer abstract. It had a voice. It had a message. It had documentation.
She typed a reply:
Where can we meet?
The response came in one minute:
Not over text. Not over phone. In person. Tomorrow. 8:00 AM. The coffee shop on 4th and K. I will be at the corner table. I will have a red notebook.
Elena looked at the message. A red notebook. A coffee shop. A corner table.
It was either real or it was the most sophisticated trap Reeve had ever devised.
She typed a final reply:
I will be there.
She put the phone down. The office was quiet. The city was outside—the ordinary rhythm of a Wednesday night. The drive was in her bag. The evidence was encrypted. The directory was exposed. The precedents were building. The wall was growing.
But the list was there. Forty-seven patients. The next redaction was pending. The clock was not just about the deadline. The clock was about the next thirty days.
And now, someone was waiting in a coffee shop with a red notebook.
Elena looked at Nadia. "We need to be there. But we need to be careful."
"We need to be smart," Nadia said. "We need to verify. We need to confirm. We need to know who we're meeting before we meet them."
"And if it's a trap?"
"Then we spring it on our terms."
Elena nodded. The night was outside. The office was quiet. The clock was ticking. The next thirty days had just begun.
At 11:55 PM, Elena opened her notepad again. She wrote a twentieth note:
11:55 PM — Patient 47 has contacted me. They claim to be a Reeve employee with documentation. They want to meet tomorrow at 8:00 AM. The meeting is either real or a trap. If real, they have the next ten scheduled redactions. If a trap, Reeve is controlling the narrative. We need to verify before we meet.
She closed the notepad. The night was deepening. The office was quiet. The clock was ticking. The next thirty days had just begun, and the first test was already here.