Chapter 20
DAR
M y hands go still.
Tommy walks down the red-lit corridor toward the primary server room, and my fingers, which have been moving for hours, which have been fighting and building and dismantling across keyboards in the longest sustained operational engagement of my life, stop.
The stillness is involuntary. My body shuts down nonessential output because every available processing cycle is tracking the man who lives behind screens walking toward a room where a retaliatory surge is about to hit.
The data I'm computing is a probability assessment I don't want to complete.
He disappears around the corner. His footsteps fade against the stone.
The silence of the dead mountain swallows him.
"Dar." Sarah's voice, sharp and clinical, the scalpel that cuts through the silence. "He'll signal when he's ready. Stay on the node."
I turn back to my screen. The backup server's pale glow is the only light in the room besides the emergency red, and my offensive position against Marsh's control node is holding but degrading.
The weapon's adaptive protocols are testing my containment perimeter, probing for the weakness that a moment of distraction might create. Marsh, wherever he is, can feel me losing focus because his code pushes harder against the breach I've been maintaining.
I can't afford to lose focus. Tommy's life depends on the timing of what happens next.
My fingers move.
Force of will overriding the animal part of my brain that wants to run down the corridor after him and drag him back to the keyboard where he belongs, where he's safe, where the worst thing that can happen to him is carpal tunnel and bad coffee.
The comm crackles. Backup comms, limited range, the thin signal that Sarah rigged from the backup server's minimal output.
Tommy's voice comes through with a quality I've never heard from him in the workspace, stripped of distance and mediation. Raw audio. No processing.
Just his breath and his words and the cold acoustics of a room full of silent servers.
"Primary core intact. Hardware undamaged. I'm reconnecting to the backup system now."
"Copy." My voice matches his in register. Flat. Precise. The emotional bandwidth required for anything else has been allocated to the operation, and what's left for communication is pure function.
I hear him working. The sound of physical connection, cables being seated, switches being thrown. The mechanical simplicity of it is almost absurd after hours of fighting through code. Hands on hardware. The digital world reduced to its most fundamental physical reality: a man plugging in a cable.
"Reconnection in progress," Tommy says. "Primary core is accepting the backup system's handshake. Signal integrity looks stable."
"How long until full integration?"
"Three minutes. Maybe less. The primary core's processing power is intact. Once the connection stabilizes, it can absorb whatever the weapon throws at it."
Three minutes.
I spend them fighting alone and alone feels different now than it used to.
Marsh's weapon senses the shift in my defense patterns. Without Tommy's systems feeding me data, my response time degrades and the weapon's adaptive protocols exploit every gap.
A probe hits the backup server's secondary buffer and nearly punches through before I catch it, reroute, and slam a containment wall into the breach with a block of code I write in real time, fingers moving faster than thought.
Another probe. A different vector.
This one targets the connection Tommy is building between primary and backup, testing the handshake for instability, and I have to split my attention between fighting the weapon and protecting the bridge he's constructing on the other end of the comm channel.
Callum died because I couldn't protect him and fight the threat at the same time.
The memory surfaces without permission, cold and precise, and I shove it into a locked partition because I am not losing someone else to a system failure. I am not.
My fingers accelerate. The code I write is vicious, precise, every countermeasure carrying the accumulated fury of a woman who has already buried one person because an institution failed and will burn this weapon to its foundations before she lets it happen again.
Marsh pushes harder. I push back.
The weapon tests a lateral attack on the comm channel itself, trying to sever the connection between my console and the primary server room. Trying to cut me off from Tommy's voice.
The surge of cold rage that hits me when I recognize the intent is productive in a way that surprises me.
I use it. Channel it into a counterattack that doesn't just block the lateral probe but dismantles the vector entirely, stripping Marsh's code down to its framework and leaving the access point cauterized.
Tommy's voice on the comm. Steady. Present. Alive.
"Integration complete. Primary core is online and synced. The absorption buffer is active. When you hit the node, the retaliation goes through the primary core, not the backup."
"And you?"
"I'll be clear of the hardware before the surge hits."
"Tommy."
"I'll be clear."
"That's not a promise you can make. If the surge timing is faster than Marsh's other deployments..."
"Then I'll move faster. Hit the node, Dar."
My fingers hover over the keystroke that will trigger the offensive. The control node is exposed.
Marsh's last line of defense is a kill switch designed to destroy whatever system attempts to shut him down, and the only thing standing between that retaliatory surge and the obliteration of our operational capability is a reconnected server core and the assumption that Tommy can disconnect from the hardware before the electricity follows the path of least resistance through the cables he just connected.
The assumption. The variable I can't control. The one piece of data I can't collect, analyze, predict, or engineer.
Trust.
"Dar." Sarah's voice from behind me. "Do it."
I hit the key.
The offensive launches. My code tears through Marsh's control node with the accumulated momentum of every vulnerability I mapped, every behavioral pattern I predicted, every piece of institutional knowledge I carried out of GCHQ and refined through years of solitary warfare against the Committee's infrastructure.
The node cracks. The weapon's central command structure collapses in a cascade that mirrors the one Marsh launched against us, his own engineering turned back on itself.
For a beautiful, terrible fraction of a second, the backup server's screen fills with the weapon dying. Lines of code decompiling. Attack vectors folding. Adaptive protocols shutting down in sequence like lights going out in a building.
Then the kill switch triggers.
The retaliatory surge hits the primary server core with a force that I can hear through the comm channel.
A vibration that travels through the stone floor of the mountain, through the backup server's frame, through the desk, through my hands flat on the keyboard.
The servers in the primary room absorb the impact with the patient brutality of hardware doing what hardware does. Taking the hit. Holding.
Tommy's comm channel fills with noise. Static and vibration and the high-frequency whine of systems under extreme load, and underneath all of it, silence where his voice should be.
"Tommy." I'm standing. I don't remember standing. "Tommy."
Static.
"Tommy, respond."
The static stretches. One second. Two. Three.
In those three seconds, my body does things my mind doesn't authorize. My fingers go dead still. My breathing stops. My vision narrows to the comm speaker as if proximity to the hardware will make his voice come through it faster.
The stillness in my hands is the tell I've never been able to control, the one that means I am holding something so enormous that if I move, if I tap, if I let my fingers translate what's happening inside me into any kind of output, I will come apart.
Callum's comm went silent too. Different frequency, different system, different war. The silence sounded the same.
The static resolves. Three seconds that take three years.
Then his voice, thready and winded and carrying the unmistakable quality of a man who just moved very fast in a very small space.
"Clear. I'm clear. Core's holding."
My knees want to fold. I lock them.
Sit back down. Place my hands on the keyboard and run the diagnostic that will tell me whether the weapon is actually dead or just dormant.
The diagnostic returns clean. Marsh's weapon is offline. The control node is destroyed. The adaptive protocols are decompiled.
The kill switch fired and the primary core absorbed the surge and the backup system is intact and the framing evidence is being systematically dismantled by Sarah's forensic analysis on the adjacent console.
"Systems coming online," Sarah reports. Her voice has the careful neutrality of a professional delivering results, but her hands are shaking against the laptop keyboard, and that tells me more about the last three minutes than her tone does.
"Primary core is stable. Environmental controls restoring. Comm channels reinitializing."
The emergency lighting flickers. White light replaces red. The color shift is so sudden, so complete, that my eyes water from the change, and for a moment the workspace looks unfamiliar in full illumination, as if the hours of red light rebuilt it into a different room.
Then the hum returns.
Low first. A vibration more felt than heard, rising through the stone floor into the soles of my boots, climbing through my bones.
The servers spooling up, one rack and then the next, each one adding its frequency to the chord.
The ventilation system engages and the first push of fresh air moves through the room like a breath the mountain has been holding. Cold, metallic, carrying the mineral taste of rock and filtration.
The communication relays reinitialize and the blue status lights on Sarah's console bloom left to right, each one a node in the network coming alive.