Chapter 18
DAR
Tommy isn't. I left him sleeping twenty minutes ago, his glasses on the bedside table and his face unguarded against the pillow in a way that made my fingers itch to trace the line of his jaw.
I didn't. I came to the workspace because the targeting data had been nagging at me since the briefing, a loose thread in Marsh's code that I couldn't leave unpulled, and the discipline of pre-dawn analysis is a habit I've never been able to break even when the alternative is a warm bed and a man whose hands I can still feel on my skin.
Every screen flickers simultaneously. A synchronized stutter that lasts less than a second but registers in my peripheral vision like a flash of lightning in a room with no windows.
The server hum changes pitch. A quarter tone, maybe less. The kind of variation that ninety-nine percent of people would never notice, buried beneath the threshold of conscious hearing.
I'm reaching for the diagnostic feed before the flicker ends.
Tommy appears in the workspace doorway forty seconds later, glasses crooked, hair wrecked, pulling a shirt over his head as he moves. He must have felt it through the floor. The hum is his heartbeat, and even in sleep, he heard it skip.
The transformation is instantaneous. One second he's the man I left in bed, soft around the edges, sleep-warm and human.
The next his posture straightens, his jaw sets, and his eyes lock onto the screens with a focus that erases every trace of vulnerability.
He crosses the room in three strides, drops into his chair, and his fingers find the keyboard the way a pilot finds the stick.
No fumbling. No adjustment period. Just immediate, total engagement.
The man behind the screens was never behind anything. He was always right here, coiled inside the jokes and the chocolate and the easy warmth, waiting for the moment the system needed him.
"That wasn't a fluctuation," he says, pulling up his primary console in one motion.
"No." My screens populate with diagnostic feeds that should be green and are instead cycling through amber. "Multi-vector. They're hitting the outer firewall, communications relay, and the biometric access layer at the same time."
Tommy's hands are moving before I finish the sentence. His keyboard rhythm accelerates to a speed that borders on mechanical.
The humor is gone. The warmth is gone. In its place is a focus so complete that his body becomes an extension of the machine, his fingers translating thought to code at a rate that my conscious mind can barely follow.
The same fingers that were in my hair three hours ago. I shove the thought sideways and match his pace.
The attack unfolds on my screens in real time and it's beautiful in the way that a well-designed virus is beautiful, which is to say it's elegant and lethal and I hate that I can admire the engineering while fighting to dismantle it.
Marsh built this thing in layers. The outer assault is noise, a brute-force battering ram against the firewall designed to consume defensive resources and attention while the real attack, the surgical component, slips through secondary channels like a knife between ribs.
I can see him in the code. The GCHQ training, the methodical layering, the defensive protocols inverted for offense.
But underneath the familiar framework, something new.
The creative deviation Tommy identified.
Marsh learned to improvise after I left, and the improvisation is woven through the GCHQ fundamentals like a second language acquired late, fluent enough to function but carrying an accent I can read.
"He's running a diversionary protocol on the primary firewall," I call out. My voice is flat. Loud enough to carry, stripped of everything that isn't information. "Ignore the volume. The real penetration vector is in the biometric relay. He's trying to clone access credentials."
"I see it." Tommy's voice matches mine in register. Low, fast, precise. "He's using the framing signature to authenticate. If it matches against my baseline, the system will read the intrusion as internal traffic."
"Then change the baseline."
Tommy's fingers pause. A fraction of a second. A lifetime in code.
"If I rewrite my own authentication signature during an active attack, every system in this facility that relies on my credentials will flag me as an intruder."
"Every system that relies on the old signature. Rotate to a new one and push it to the critical nodes before the weapon catches up."
"That gives us a window of about ninety seconds where the base runs on trust instead of verification."
"Then we'd better be fast."
He looks at me. Without the humor, without the glasses-adjustment stalling mechanism, without any of the layered defenses he maintains between himself and the world, Tommy's face in crisis is controlled intensity that makes something tighten low in my belly.
Which is wildly inappropriate given the circumstances, and I file it under later and focus.
"On three?" he says.
"I'm already on five. Keep up."
His fingers move. Mine move. The workspace fills with the sound of two keyboards running in tandem, and the synchronization we built through days of collaboration becomes operational for the first time under live fire.
I run offensive countermeasures against the biometric relay intrusion, dismantling Marsh's access vectors as fast as he deploys them.
His attack patterns carry the GCHQ signature like a fingerprint, and every time he launches a new vector I feel the ghost of the division we shared, the training that lives in both of us like muscle memory.
I know how he thinks because I learned from the same manuals, and the intimacy of fighting someone whose code you can read is a specific kind of violence that leaves no marks and draws no blood but strips you bare just the same.
Tommy rebuilds his authentication signature in real time, a coding sprint that requires rewriting the credentials that every critical system in Echo Base recognizes as belonging to the man who built them.
It's the digital equivalent of changing the locks on your house while someone is trying to pick the front door, and Tommy does it with a precision that would make me jealous if I weren't too busy to feel anything except the focused heat of combat through code.
Kane's voice comes through the internal comm. "Status."
"Active intrusion," Tommy responds without pausing his keystrokes. "Multi-vector attack on firewall, comms, and biometric access. We're containing. Estimate twelve minutes to initial stabilization."
"Do we have compromised systems?"
"Not yet. Working on keeping it that way."
The comm clicks. Kane issues orders I only half register.
Stryker and Mercer deploying to physical perimeter positions. Dylan on internal security. Sarah rerouting signals traffic through backup channels. Victoria feeding intelligence from contacts who are monitoring Committee communication chatter for indicators of secondary operations.
The team moves around us like a system responding to a threat alert. Each component activating its designated function. Each person doing the thing they were built for.
I’m doing the thing I was built for.
The realization settles into my body between keystrokes. I'm not running this fight from a loft with flat Mountain Dew and no one to hear me curse when a system fails.
I'm running it beside Tommy, inside his mountain, surrounded by people who are counting on us to keep the walls standing. The team isn't abstract. The stakes aren't theoretical.
Khalid passes through the workspace carrying cable. He's pale, his eyes too wide, but his hands are steady and the cable goes where it needs to go.
Tommy's mentoring, paid forward in a crisis. Something twists behind my ribs, and I file the sensation and keep typing.
"He's adapting," I say. The weapon's secondary layer activates as Marsh realizes his biometric intrusion is being countered. New vectors open against the communications infrastructure, probing for the backup channels Sarah just activated. "He saw the reroute. He's targeting the backup comm relays."
"How fast?"
"Fast enough to worry me." My fingers find a pattern in the attack code that makes my gut clench. "He's not improvising. He anticipated we'd reroute to backup. The weapon has pre-built attack vectors for every contingency channel in the system."
Tommy swears. A single word, concise, without the usual creative elaboration he brings to profanity. The brevity tells me more about his stress level than any diagnostic could.
"He mapped my contingency protocols," Tommy says. "He didn't just study the primary systems. He studied the fallbacks."
"He studied you." I keep my voice clinical.
The personal implications of this statement are significant, and we both know it, and neither of us can afford the processing cycles to feel it right now.
"Every defensive move you make, he's already modeled.
Your instincts are compromised because he predicted them. "
"Then I need to stop being me."
I look at him. His face is lit by scrolling red alerts, his glasses reflecting threat data, his jaw set with the controlled fury of a man watching someone disassemble his life's work in real time.
"Be me instead," I say.
The idea lands. I watch it register. Tommy's eyes widen, and then his mouth does the thing it does when his brain catches a solution before his conscious mind has finished formulating the problem.
"He doesn't know your methodology," he says. "He mapped my defensive patterns, but you weren't part of this system when he built the weapon."
"I'm an unknown variable in his model. My offensive countermeasures don't match anything he's prepared for."
"If I run your playbook instead of mine and you handle the defense while I attack..."
"We invert his entire prediction framework." My fingers accelerate. "He's built to fight you. He's not built to fight us."