Chapter 10 #2
"Three vectors." His voice is all business, the vulnerability from thirty seconds ago gone.
What remains is the operator, the man whose hands on a keyboard are the difference between an intact perimeter and a breach.
"Northern relay, tertiary junction, and the communication handshake you identified in the server room. "
"They're testing our response patterns." My fingers fly, offensive countermeasures spinning up. "If we respond with standard countermeasures, they'll record the patterns and feed them to the adaptive weapon."
Before Tommy finishes the sentence, a tertiary probe that neither of us flagged breaches the signals infrastructure on a vector I didn't predict.
The attack bypasses my containment entirely, threading through a maintenance port in Sarah's suite that I hadn't mapped because I was focused on the primary and secondary layers like an analyst who forgot that the enemy has read her playbook too.
Sarah's board goes red.
Not amber. Not the cautious yellow of a degraded system running backup protocols.
Red. The flat, total red of systems that are no longer reporting because the systems no longer exist in a functional state.
Her intelligence feeds — the European contact network that Victoria spent months cultivating, the real-time tracking data on Committee asset movement, the signal intercepts that were feeding the team's operational planning — all of it shredded in the four seconds between the probe's breach and my belated containment response.
"Tommy." Sarah's voice comes through the internal channel, and the sound of it makes my typing falter because Sarah Andrews does not sound like that.
Sarah sounds like steady diagnostics and controlled precision and the professional composure of a woman who treats chaos as data.
The voice on the channel sounds like a woman watching six weeks of source development burn.
"They got my signals suite. European feeds are gone.
The real-time tracking on Committee asset movement is gone.
Those feeds don't rebuild, Tommy. The contacts that sourced them don't rebuild.
Those are people who trusted us with information, and the channels they used to deliver it just got exposed. "
My gut drops. The intelligence feeds Sarah lost aren't data — they're relationships. Human sources who risked their safety to provide information through channels that were supposed to be secure, and the weapon just ripped those channels open like peeling insulation off a live wire.
"Can you reconstruct from cached data?" I ask.
"I can reconstruct a snapshot. Hours old. Static. If the Committee moves assets between now and whenever we need that intelligence, I'll be reading yesterday's newspaper."
Victoria's voice, flat and precise on the comm from the monitoring station: "They will move assets. That's the purpose of blinding us before the primary assault."
My hands are moving, rerouting defensive resources to seal the breach Sarah's suite left in the network topology, but the damage is structural and the seal is a patch, not a repair.
The signals infrastructure was load-bearing.
It supported the intelligence picture that every operational decision in this facility depended on, and now there's a hole where it was that I can't fill with code.
Tommy hasn't stopped typing. His offensive countermeasures are still running, still holding the primary and secondary perimeters, but I can see the shift in his rhythm—the bursts are shorter, the pauses longer. He heard Sarah. He knows, better than anyone, what it means.
We're fighting blind now. Whatever intelligence we had about the Committee's operational posture is frozen at the moment the feeds died, and every minute that passes makes the picture less reliable.
"So we don't respond with standard countermeasures."
"We respond with something they've never seen." My fingers are already moving, the plan assembling as I speak. "Route my output through your defensive matrix. I'll handle the offensive response. You manage containment."
Tommy doesn't hesitate. His fingers redirect system resources, opening a channel between my offensive tools and his defense grid, and the integration is seamless, two systems merging in real time with the fluidity of components designed to work together.
The probe intensifies. I counter. Tommy contains. My attacks flow through his defenses and strike at the probe's source nodes while his containment holds the perimeter.
The rhythm of our keystrokes synchronizes, his steady cadence and my bursting pattern aligning into a composite faster than either of us alone.
The probe retreats. Attack vectors collapse. Tommy's defensive matrix holds. My counterattack traces the probe's routing back through proxy layers before the signal disappears.
Then the lights go out.
Not a flicker. Not the brown-out stutter of a system under strain.
A clean, total cut, every overhead in the workspace dying simultaneously, the screens holding on battery backup while the room plunges into a darkness that lasts three full seconds before the emergency strips along the floor activate in amber.
Three seconds of absolute dark in a room carved from rock with no windows.
My hands lock on the keyboard. Tommy's chair rolls sideways as his body reacts, one hand going to the desk for orientation while the other stays on his keyboard by pure muscle memory.
In the amber emergency glow, his face is all shadow and sharp edges, and his eyes find mine with the intensity of a man who just felt his own nervous system stutter.
"That wasn't the probe," he says. His voice is tight. "The probe was network-layer. This hit the power grid. Physical infrastructure."
"A secondary attack."
"Running simultaneously with the network probe.
Using it as cover." His hands fly across the keyboard, pulling diagnostics from the power management system.
"Someone piggy-backed a physical infrastructure attack onto the digital probe.
The power grid runs on a separate control system from the network, air-gapped, independent.
But the environmental controls that regulate the air-gap aren't independent.
They're connected to the same monitoring layer the probe just tested. "
The implication settles. "They used the network probe to map the connection between your monitoring layer and the physical infrastructure controls."
"And then they hit the physical grid through the gap.
" His jaw is working. "Three seconds. That's how long the backup generator took to spin up.
Three seconds where the ventilation was offline, the blast doors were unsecured, and the biometric locks on every entrance in this facility were running on battery with no network verification. "
Three seconds. Long enough for a door to open. Long enough for a lock to fail. Long enough for anyone positioned at a physical entrance to walk through.
Kane's voice on the comm: "All stations, report."
The check-in runs. Dylan at the armory. Stryker at the vehicle bay. Sarah at the signals suite. Each position reports secure, and each report releases a fraction of the tension that accumulated in the three seconds of dark.
But the fraction is small, because the point of the three seconds wasn't what happened during them.
The point was proving they could be created.
The Committee just demonstrated that their weapon isn't limited to the digital domain.
They can reach the physical infrastructure of Echo Base through the digital channels, and the next time they create those three seconds, they'll have assets in position to use them.
The overheads stabilize. The amber reverts to white. The hum recovers its full frequency.
Tommy is staring at his power grid diagnostic with the expression of a man who just discovered a room in his house he didn't build.
"I need to air-gap the physical infrastructure controls," he says.
His voice is quiet. Devastated in the specific way that Tommy gets devastated: not with grief but with the recognition that something he built has a flaw he should have seen.
"Completely. No connection to any networked system. Hardware isolation."
"That's a twelve-hour rebuild.”
“I’ve set the system to do it automatically."
"Then it’s a good thing you started it now."
The screens settle. Green replaces red. The server hum steadies.
"Your offensive routing gets sloppy when you're angry." Tommy's voice is rough from the adrenaline, but the observation is precise.
"Your containment protocols get conservative when you're scared."
"I wasn't scared. I was managing risk."
"You were scared. Your keystroke rate dropped in the second wave."
"You were monitoring my keystroke rate during an active cyberattack."
"I monitor everything. It's a character flaw."
The silence that follows carries the faintest edge of something that might be a shared almost-laugh, if either of us were the type.
I'm breathing hard. The adrenaline has nowhere to go, cycling through my system with the insistence of a current that has lost its ground.
The workspace is dark and his face is close and the combined residue of the argument and the combat is pressing against the inside of my chest with a force I can't contain.
"We should talk about this." My voice comes out steadier than I feel, clinical and direct, the way I handle every conversation that carries weight. "If this is going to happen."
"If."
"When." The correction is an admission. "I have an IUD. I was tested after my last partner. Clean."
"Same. Clean, and it's been a while."
"Define a while."
"Long enough that this conversation is the most intimate interaction I've had with another person in longer than I want to calculate."
"And I want it understood that this doesn't change the operational dynamic."
"You don't compartmentalize. You told me so yourself. You measure everything."