"Can you stop it?"
"I can fight it. Whether I can stop it depends on what the payload does when it arrives."
Kane nods. Turns to Dylan. Some communication passes between them that doesn't require language, the shorthand of men who have stood in worse places and made harder decisions.
"Hold the mountain," Kane tells all of us. Then he's gone, moving through red-lit corridors to coordinate the rest of the team, and the sound of his boots on stone fades until the only thing left is the thin hum of the backup server and the rhythm of two keyboards.
Dar fights.
I've watched combat through screens for years. Helmet feeds and drone footage and the grainy resolution of satellite imagery, violence mediated by pixels and distance. Watching Dar fight Neil Marsh through code is the first time I've ever witnessed a battle that happens in my own domain, and it's more visceral than any firefight I've observed through glass.
She works in silence. Complete silence. Her fingers move in bursts, fierce salvos of keystrokes separated by pauses so still that I'm not sure she's breathing.
Each burst is a countermeasure, an attack, a feint, a probe. Each pause is analysis, recalculation, the brief gapbetween seeing and acting that separates competent coders from exceptional ones.
Marsh's weapon responds to each counter with adaptive modifications. The code shifts. Evolves. Tests new vectors. Probes weaknesses in the backup system that shouldn't exist but do because no system is perfect and every defense has a seam.
I watch my diagnostic feeds and try to be useful. Patch vulnerabilities as Dar identifies them. Shore up the backup system's limited defenses. Feed her data on the attack patterns so she can anticipate Marsh's next adaptation.
It's support. Behind the screen. The role I've always played.
Sarah works the signals infrastructure with grim efficiency, rerouting what little communication capability the backup server provides to maintain minimal contact with the outside world.
She traces the framing evidence distribution, maps the channels Marsh used, and begins building the forensic case that will prove the fabricated signatures aren't mine.
Dylan stands guard. He stands in the doorway of the backup server room with his hand near his weapon and his eyes on the corridor, because in Dylan's world, digital attacks can become physical ones with no warning, and he's not going to let anyone through that door.
Hours pass. The air gets thicker. The red emergency lighting gives everyone the look of people operating inside a wound.
Dar breaks Marsh's outer defense layer mid-afternoon. The breakthrough is quiet, marked by a sharp exhale and a shift in her typing rhythm that I recognize because I've memorized the cadence of her keystrokes the way other people memorize songs.
She's found something. An opening in the weapon's control structure that Marsh's adaptive protocols haven't closed.
"I can see the core," she says. Her voice is hoarse. Hours of silence make the words rough. "The payload deliverymechanism is connected to a central control node. If I can reach the node and shut it down, the weapon dies."
"If?"
"The node is protected by a kill switch. If the weapon detects an unauthorized shutdown attempt, it triggers a retaliatory surge designed to destroy whatever system is trying to stop it. In this case, our backup server. The only thing keeping us operational."
I stare at the diagnostic feeds. At the damage reports scrolling across the screen. At the fragments of a system I spent years building, reduced to error logs and failure cascades by a man whose competence was unremarkable until the Committee gave him resources and a target.
My system. My work. My identity. Everything I have contributed to this team, to this family, quantified in lines of code and server uptime and the hum that used to fill this mountain and now doesn't.
And underneath all of it, underneath the damage and the loss and the silence where the hum used to be, I hear something I've been trying not to hear since the day Kane put a laptop in my hands and told me to build something worth protecting.
The team didn't form because of what I built.
Kane saw something worth investing in before the first server rack was bolted to the floor. The others trusted what we were building before the infrastructure existed to justify that trust.
Every person in this mountain chose to be here before my systems gave them a reason to stay. The code came after the commitment. The infrastructure was a response to that loyalty, not the source of it.
They aren't here because of my systems. My systems are here because of them.
What I built was always a reflection of what I felt. Every redundancy, every failsafe, every security protocol designed to keep them safe.
The infrastructure was love encoded into function, and Neil Marsh can destroy every server in this mountain and it won't touch the thing that actually holds us together.
"I can reach the node," Dar says. "But the retaliatory surge will try to take the backup server with it. We need a way to absorb the surge without losing our only operational system."