The words carry the particular protectiveness of a man shielding a teammate from a distraction he doesn't need, and the casual authority of someone who has been managing Tommy Hale's threat-awareness for long enough to know that the man processes threats by building defenses, and right now his defense-building capacity needs to stay focused on the weapon that could kill all of them rather than the surveillance team that's studying their grocery habits.
I file Stryker's request underpendingrather thanagreedbecause withholding operational intelligence from the personresponsible for facility security is a decision I'm not comfortable making on someone else's authority.
But I understand the logic. And the logic is an act of care from a man who shows it through tactical decisions rather than words, which is a form of affection I'm beginning to recognize as the native language of this mountain.
The barriers open. The tunnel swallows the vehicle. The mountain closes behind us, and the hum reaches me through the floorboards before we reach the vehicle bay.
I'm back inside. The air is recycled. The light is artificial. And the facility that felt like a cage a few days ago feels, for the first time, like the thing that's keeping me alive.
Days blur when you work inside a mountain and the working rhythm Tommy and I have established feels like some weird combination of hostility and collaboration. I'm aware of his body in a way that's becoming operationally inconvenient.
He arrives at the workspace before dawn, which I know because I'm already there. He drops into his chair with a travel mug trailing steam and a candy bar wedged between his teeth. He doesn't say good morning because we've moved past the pretense that either of us slept. His screens wake in sequence, a cascade of system checks scrolling faster than anyone should be able to read, and his fingers hit the keyboard before the candy bar is finished. The rhythm starts, rapid and even and relentless. I've been listening to it for days, and my brain has started treating it the same as the server hum: baseline noise that means the system is running.
What my brain hasn't treated as baseline is the way he rolls his sleeves up when he works. Forearms. Tendons shifting under skin as his fingers move. The musculature of someone who does more with his hands than type, though I'm not supposed to know that yet. I stare at my own screen and force the observation into a box marked irrelevant, but the box won't close.
My rhythm is different, coming in bursts with long pauses where my hands hover and my mind runs three layers ahead, mapping pathways before I commit a single keystroke. Then a flurry of input so fast my wrists ache from the angle. Tommy noticed the pattern on day two. I caught him glancing sideways during one of my pauses, the kind of look that wanted to ask what I was doing but didn't want to admit he couldn't figure it out on his own.
Good. Let him wonder.
Kane's ground rules sit between us like a demilitarized zone. Shared access to specific sectors. Mutual transparency on methodology. No unauthorized operations. The terms are reasonable, and I understand why Kane set them for both of us instead of just me, because making me the only one under restriction would've confirmed what everyone in this mountain already thinks: that I'm the variable, the unknown, the problem that walked in wearing fingerless gloves and a bad attitude.
Tommy pulls his headphones down around his neck. "I rebuilt the tertiary relay."
"I know. I checked it at four."
His jaw works. "Of course you did."
"Your patch is solid. Better than the original." I keep my eyes on my own screen. The compliment costs me nothing and buys goodwill, and if it also happens to be true, that's incidental. "But you reinforced the north-facing handshake protocol with a redundancy loop that adds latency. Over sustained traffic, that compounds."
"Over sustained traffic from, say, a coordinated multi-vector cyber weapon?"
"Over sustained traffic from anything. Sloppy is sloppy."
He takes a long drink of coffee, swallows, and adjusts his glasses with his ring finger. "How much latency?"
"Twelve point three milliseconds per cycle. More if the secondary relay is under load."
"You measured."
"I measure everything."
The silence that follows should be combative, but it isn't. His mouth twitches at one corner, and he turns back to his screen, and the twelve point three milliseconds hang between us like a shared joke that neither of us is willing to laugh at yet. His mouth, when it does that, creates a problem I don't have a variable for. I notice the shape of it. I notice that I notice. I force both observations into the box that won't close and go back to work.
We work.
The Committee's weapon is more sophisticated than the targeting data suggested, and every layer I peel back reveals another layer beneath it with a design philosophy I recognize. Distributed nodes, redundant pathways, modular deployment capability. Whoever built this didn't just study offensive cyber operations. They studied elegant offensive cyber operations. The weapon's a surgical instrument, and the precision of its design tells me something about its creator that the targeting data alone never could: this person cares about craft.
I hate that I admire it.
"I need you to walk me through your defense matrix." The words come out flatter than I intend. Asking for help doesn't come naturally. Asking Tommy for help, specifically, feels like conceding ground I can't afford to lose. But the weapon's delivery mechanism targets the intersection between his internal systems and the external communications channels, and I can't map the attack surface without understanding what he built.
Tommy rolls his chair sideways until our stations overlap, close enough that I can smell coffee and dark chocolate andsomething underneath both, something warm and clean and distinctly him. My body registers the scent with the efficiency of a system that's decided this information is mission-critical despite receiving no such instruction.
He pulls up a schematic on his center monitor and starts talking.
Rapidly. In layers. With tangential observations that seem irrelevant until they circle back three sentences later and land with the precision of a scalpel. He talks the way he codes: dense, efficient, and threaded with a structural logic that makes my fingers itch to diagram it.
"The primary defense operates on a rotating cipher with a randomization seed generated from environmental data. Temperature readings from the server room, ambient sound levels, barometric pressure from the exterior sensors. Nothing digital, nothing predictable, nothing someone could brute-force without physically being inside the mountain. Secondary layer is behavioral analysis. The system learns normal traffic patterns and flags deviations, but I tuned the sensitivity so it doesn't cry wolf every time Sarah runs a high-volume signals sweep in the middle of the night."
