Cherreads

Chapter 34 - Chapter 35: THE HALF MEASURE

Chapter 35: THE HALF MEASURE

Saturday, December 10, 2011, 11:00 AM — CTC Bullpen / Saul's Office, CIA Langley

Estes's response arrived in a classified memorandum routed through Saul's office at 10:47 AM, and the weight of it was exactly half what it should have been.

Enhanced security coordination with Secret Service for December 15 event. Additional screening protocols for facility perimeter. Counter-sniper team deployment approved for approach route and adjacent structures. Event relocation: DENIED — VP's office deems assessment insufficient for schedule disruption. Full attendee magnetometer screening: DENIED — operationally infeasible for VIP-level event. Recommendation for event cancellation: DENIED — no actionable intelligence meeting threshold for cancellation.

I read the memorandum at my desk with the specific numbness of a man who'd predicted the institutional response as accurately as he'd predicted the threat it was supposed to address.

They'll screen the perimeter but not the people. They'll put counter-snipers on the rooftops but leave the front door open to anyone with a VIP credential and a vest under their suit. The Assessment predicted a multi-vector attack with an insider component, and the institutional response addresses the external vector while ignoring the internal one because screening a congressman is "politically insulting."

Two hundred nineteen people died at Langley because the institution moved too slowly. The December 15 briefing is a smaller event, fewer casualties, but the institutional failure mode is identical: acknowledge the threat, respond to the part that's politically comfortable, and pray the uncomfortable part doesn't happen.

Saul was in his office. The door was open — a signal, in Saul's behavioral lexicon, that he was accessible but not inviting. I stood at the threshold.

"The response."

"I read it."

"It addresses the sniper vector. It doesn't address the insider vector."

Saul's reading glasses sat on the desk beside the memorandum. His hands were folded. The posture of a man who'd already had this argument with Estes and lost it, and was now hearing the post-mortem from the analyst who'd predicted both the threat and the insufficient response.

"Estes won't screen VIPs at their own security briefing. The political calculus is simple — if we're wrong, the screening is an insult that damages the Agency's relationship with the VP's office. If we're right, the screening is a confession that we let a threat get close enough to require it."

"And if we're right and we don't screen?"

"Then we'd better catch the threat before it reaches the door."

The answer was Saul at his most pragmatic — the institutional reality compressed into a tactical imperative. If the full security enhancement was off the table, then the interdiction had to happen upstream. Catch Walker before his sniper position was established. Identify and disrupt the coordination signal before it reached Brody. Intervene at the handler level, not the event level.

Ghost-Saul's insight from the strategic session: "If you can identify the trigger mechanism, you can interdict the attack without confronting Brody directly." The Assessment recommended event-level security. The institution rejected it. The alternative is network-level disruption — catching the coordination before it becomes action.

"The communication relay," I said. "The burner phone endpoint. If we can intercept the activation signal—"

"NSA is monitoring. The relay nodes are flagged. If the handler transmits through the identified infrastructure, we'll catch it."

"And if the handler uses a different channel?"

Saul's silence lasted six seconds. The longest I'd measured from him in nine weeks. The silence of a man who'd weighed the same question and found the answer insufficient.

"Then we'd better have a backup plan."

The backup plan took shape in the tech bay at 2:00 PM. Max had cleared a workstation — two monitors, a printer, spread space for documents — with the practical efficiency of someone who'd spent his career preparing operational support infrastructure without questioning the operations it supported.

"Contingency modeling," I said. "The December 15 briefing venue. I need evacuation route analysis, structural vulnerability assessment, and blast radius calculations for various explosive yields inside the facility."

Max's hands paused on the keyboard.

"Blast radius calculations."

"The Assessment identified an insider threat with potential explosive capability. Estes approved partial security enhancement. The structural analysis fills the gap."

Max studied me for three seconds. The same quiet evaluation from the Georgetown bar, from the 4 AM phone call, from every moment where he'd measured the distance between what I was saying and what I was meaning.

"You think someone's bringing a bomb to that briefing."

Not a question. An observation from a man who ran surveillance equipment for a living and could read an intelligence picture from its component pieces without needing the frame.

"I think the Assessment identified a credible threat and the institutional response is insufficient. The contingency planning addresses the gap."

"Franklin." My first name. Max used it rarely — the shift from surname to given name carried the weight of personal rather than professional communication. "Why are you this fixated on this specific event?"

The question landed in the space between cover story and truth, the same space I'd been living in for sixty-six days. Max had watched me build the Brody file, volunteer for illegal surveillance, survive a bipolar episode, present the Walker trail, deliver the Ingham Assessment, and now request blast radius calculations for a political event five days away. The accumulation had reached a mass that simple analytical enthusiasm couldn't explain.

Tell him. Not everything — not the transmigration, not the system, not the Ghosts. But enough. Tell him you think someone is going to die at that briefing. The truth, or the closest thing to it you can offer.

"Because I think someone's going to die there."

The words came out flatter than I'd intended — not clinical, not emotional, just the bare statement of a conviction I'd been carrying since the first morning I woke up in this body and understood what world I'd landed in.

Max held my gaze for four seconds. Then he turned back to the keyboard.

"Then let's make sure they don't."

The contingency planning consumed three hours. Max pulled architectural plans for the briefing facility from the General Services Administration database — floor layouts, structural specifications, HVAC routing, emergency egress paths. I overlaid the plans with the vulnerability analysis I'd been developing since the Walker sniper assessment: entry points, screening gaps, structural weak points where explosive force would propagate most effectively.

The blast radius calculations were the hardest part. Not technically — the physics of explosive detonation in enclosed spaces was well-documented in the CIA's own tactical reference library. The difficulty was emotional. Each calculation translated into a count — seven casualties at this yield and range, fourteen at this yield, twenty-three if the blast channeled through the corridor toward the secondary meeting room. Numbers that represented people whose names I didn't know and whose deaths I was modeling on a workstation in a tech bay while they went about their Friday afternoon unaware that an analyst at Langley was calculating the geometry of their potential destruction.

[Shadow Archive Protocol: OI engagement — structural analysis, venue assessment. Analytical work: genuine tradecraft, no system abilities required. OI adjustment: 12→13.]

Max worked beside me without speaking, the comfortable operational silence of two professionals collaborating on a problem too serious for small talk. His contributions were precise — the structural specifications I needed, the evacuation modeling software I didn't know the Agency possessed, the practical knowledge of a man who'd spent years installing surveillance equipment in buildings and understood their architecture from the inside.

At 5:00 PM, the contingency package was complete. Evacuation routes mapped. Structural vulnerabilities identified. Blast scenarios modeled for three explosive yields. Counter-sniper positioning recommendations for the approach corridor. Emergency medical response staging locations. A complete backup plan that assumed the worst and prepared for everything the Assessment predicted and Estes's half-measure ignored.

Max printed two copies. One for Saul's classified inbox. One for the contingency file that would sit in the operations center on December 15, available for immediate deployment if the worst-case scenario manifested.

"Franklin."

"Yeah."

"The next time you think someone's going to die somewhere—" Max paused. Chose his words with the precision of a man who'd learned that the right sentence at the right moment was its own form of tradecraft. "Tell me sooner."

The walk back to my desk carried the weight of the afternoon's work and the specific, quiet solidarity of a man who'd spent three hours calculating blast radii beside me because I'd asked and because he trusted the asking.

The Assessment. The half-measure. The contingency plan. Five days to December 15, and the institutional framework for response was as complete as one analyst and one surveillance technician could make it. The rest depended on whether the CIA's counter-sniper teams could find Walker, whether the NSA's communication monitoring could intercept the activation signal, and whether the partial security enhancement would be enough to stop a man who'd already decided to die.

And if none of that is enough — if Walker takes his position, if the signal reaches Brody, if the vest passes through the gap in the screening — then the contingency plan becomes the last line of defense. An evacuation plan built by an analyst who knew the threat because he watched it on television in another life, and a tech who helped because someone said "I think someone's going to die."

To supporting Me in Pateron.

with exclusive access to more chapters (based on tiers more chapters for each tiers) on my Patreon, you get more chapters if you ask for more (in few days), plus new fanfic every week! Your support starting at just $6/month helps me keep crafting the stories you love across epic universes.

By joining, you're not just getting more chapters—you're helping me bring new worlds, twists, and adventures to life. Every pledge makes a huge difference!

Join now at patreon.com/TheFinex5 and start reading today!

More Chapters