Chapter 16
NEIL MARSH
T he deployment dashboard runs clean across three monitors, and the sandwich on the desk beside the keyboard is halfway to room temperature because eating requires attention I've allocated elsewhere.
Ham and Swiss. The same order from the same deli on the same rotation I've maintained for eleven months, because consistency in the small things frees cognitive resources for the work that matters.
The wrapper is folded precisely at the corners.
The napkin is unused. The coffee is black, no sugar, cooled to the temperature where flavor becomes irrelevant and caffeine is the only remaining function.
The weapon's status indicators scroll in real time.
Every module performing within expected parameters.
The framing component uploaded to the distribution network eighteen minutes ago, and the confirmation pings are arriving at intervals that match my deployment model to within a two-percent margin of error.
Two percent. Acceptable. Not elegant, but acceptable.
I pull up the coding signature I built for the frame.
Tommy's patterns, reconstructed from months of intercepted output, layered into the attack payload with enough fidelity to pass automated forensic analysis.
The variable naming conventions. The conditional nesting.
The structural logic that marks his work the way a brushstroke marks a painter's.
It's competent work. My work is always competent.
The signature replication follows a methodology I developed specifically for this project, systematic and thorough, and the result is a fabrication that will hold under any scrutiny short of someone who has spent significant time inside Hale's actual codebase.
The probability of that is negligible. The man works inside a mountain. His code doesn't leave.
I take a bite of the sandwich. The bread is going stale at the edges.
I chew, swallow, and return my attention to the deployment timeline.
Phase two is scheduled for the window I identified in Hale's relay synchronization protocol, the handshake gap between primary and backup channels that opens for fractions of a second on a predictable rotation.
The timing is precise because precision is what I do. What I have always done.
The Atterly notification sits in a separate partition on my secondary monitor. A flagged name, routed through Committee intelligence channels three days ago. Dar Atterly, formerly of GCHQ Cyber Operations Division, located inside the target facility.
I remember her.
Not well. Not the way you remember someone who mattered.
The way you remember someone who occupied adjacent space in a building full of adjacent spaces, a face attached to a workstation three rows from yours who filed reports with a frequency that bordered on compulsive and spoke in meetings with the particular intensity of someone who believed that being correct entitled her to being heard.
She was correct. About the vulnerability, about the risk, about the probable failure mode that killed the operative in the field.
Her reports were technically precise and her conclusions were sound and none of that mattered because the institution she was shouting at had already decided that admitting the flaw was more expensive than absorbing the loss.
I sat in those meetings. I heard the reports.
I understood the technical argument well enough to know she was right, and I said nothing, because saying something would have required me to attach my name to a position the institution had decided to reject, and attaching my name to rejected positions is how careers end.
Hers ended. Mine continued. The distinction wasn't about courage or cowardice. It was about resource allocation. She spent her capital on being right. I spent mine on being retained. Both of us made rational choices given the information available.
The fact that her choice cost her partner's life and mine cost nothing is an asymmetry I've noted without assigning moral weight, because moral weight is a variable I don't track.
Systems succeed or fail. People make choices that serve their interests or don't. The institution protected itself.
I protected myself. Atterly protected her principles and lost everything, which is what happens when you prioritize principle over pragmatism in a system designed to reward the opposite.
She's inside the facility now. Working with Hale. The intelligence suggests she arrived voluntarily, which means she made another principled choice, and this one puts her directly in the path of a weapon I've spent eleven months building.
I take another bite. Chew. Note the time. The deployment window opens in hours, and the preparation checklist has four remaining items, each one scheduled and sequenced and ready for execution.
The sandwich wrapper goes in the bin. The napkin, still unused, follows it.
I return to the dashboard and make a minor adjustment to the phase-two timing coefficient. The correction is small. Point-three percent. The kind of refinement that separates adequate work from thorough work, and my work is always thorough.
The monitors glow. The coffee cools. Somewhere inside a mountain in Montana, a system administrator and a former colleague are preparing to defend against something they haven't fully seen yet, and the preparation will be impressive and insufficient because I've been studying Hale's defensive patterns longer than either of them knows, and the weapon I built accounts for every contingency his methodology is capable of producing.
It does not account for hers. But then, I haven't thought about Dar in years, and the Committee's intelligence assessment rates her involvement as a minor variable.
Minor variables don't change outcomes. That's what makes them minor.
I open the next item on the checklist and begin.
DAR
Tommy said the name twenty minutes ago, and my mouth still tastes like metal.
Neil Marsh. Two words that shouldn't carry more weight than any other data point, but my body disagrees with my brain on this one and my pulse is running too fast for someone sitting still.
He stood in front of me at the overlook with his hands in his pockets and his jaw tight and said it like he knew it would detonate something, and he was right.
I haven't moved since.
Tommy has. He retreated to his own station, two desks over, and the sound of his keyboard has been a low, steady rhythm at the edge of my awareness while I process.
He's giving me space without leaving the room, which is the kind of calculated proximity that should feel tactical and instead feels like something I don't have a clean word for.
My fingers are flat on my desk. Motionless.
I'm aware of the stillness in them because I'm aware of everything right now, every input amplified to a frequency that hurts.
The hum of the servers. The cold bleed of the monitors.
The faint, persistent smell of his dark chocolate from his second drawer, embedded in the workspace like a scent I can't scrub out of my operating system.
Neil Marsh built the weapon aimed at this mountain.
Neil Marsh, who worked three desks from mine in GCHQ's Cyber Operations Division. A contractor embedded so deeply in the division that most of us forgot he wasn't staff. Quiet. Methodical.
The kind of coder who builds by the manual and never deviates, whose work was competent enough to keep the contract and unremarkable enough to ever draw scrutiny.
He sat in the same meetings I sat in. He heard me flag the vulnerability.
He nodded along with everyone else and did nothing when the reports disappeared into institutional inertia.
He was still there when they buried me.
My hands stay still. The stillness is deliberate now, controlled, because if I let my fingers move they'll shake and I refuse to give this that much power.
Data is signal. Emotion is noise. Neil Marsh is a data point, and I will process him the way I process every other piece of intelligence that crosses my screens.
Except the data tastes like metal and the signal keeps degrading.
I pull up every file Victoria provided. Cross-reference against my own GCHQ maps. The coding signatures match.
I've been staring at Marsh's work for weeks without recognizing it because he's gotten better since I left, or because I wasn't looking for him, or because the possibility that someone I worked alongside would build a weapon designed to crack open a facility full of people and aim it at the man sleeping next to me was so far outside my operational parameters that I never ran the scan.
My fault. Should have been broader. Should have been faster.
Tommy's keyboard goes quiet. The absence of his rhythm pulls my attention sideways the way an anomaly in a data feed would, involuntary and immediate.
"The briefing is in twenty minutes," he says. His voice is stripped of its usual layers. No sarcasm. No deflection. When Tommy drops the humor, the silence where it used to be has a weight that presses on my sternum. "Kane wants your assessment. Victoria's already in the conference room."
"I know."
"You don't have to do this alone."
"If I needed a pep talk, I'd have asked for one in a less patronizing font."
The words come out sharper than I intend, but I don't take them back. Tommy absorbs the edge without flinching, which is one of the more infuriating things about him. Most people retreat from precision. Tommy leans into it.
"Noted," he says. "How about a tactical observation instead? You've been staring at the same screen for twenty minutes and your hands haven't moved, which means you're either catatonic or composing a masterpiece. Since your eyes are tracking, I'm going with masterpiece."