"Your instinct was right. You just needed the structural model to support it."
He gathers his laptop with the careful movements of someone who treats borrowed equipment with more respect than his own, and as he turns toward the door something catches in my chest like a hook finding fabric.
Callum taught the junior analysts this way. Questions instead of answers. Leading them to the solution rather than handing it over, because the path mattered more than the destination and understanding built resilience in a way that memorization nevercould. I watched him do it a hundred times in the Cheltenham offices, leaning over someone's monitor with that particular patience he carried like a tool, and I absorbed the method without realizing I was absorbing it until this moment, in a room inside a mountain, watching a kid walk away with a piece of knowledge that arrived through a chain of hands that starts with a dead man in a foreign country who never got to see what his teaching became.
The memory doesn't hurt the way it usually does. It fits. Like a line of code I wrote years ago finally finding the function it was meant to serve.
Khalid leaves, and I feel a pull behind my sternum that I recognize from a version of myself I thought I'd deleted. The version that wanted to teach, that believed knowledge was worth sharing because understanding builds systems that don't break.
The version that existed before GCHQ proved her wrong.
Tommy is watching from his station. His expression is unguarded in a way he probably doesn't realize.
What's on his face is warm and specific and aimed at me with an intensity that makes my skin prickle.
"Stop looking at me like that," I say.
"Like what?"
"Like I just did something that matters."
"You did do something that matters."
"I helped a kid debug a routing protocol. That's baseline human decency, not a character revelation."
"Agree to disagree." He turns back to his screen, and the softness in his voice when he says it lodges somewhere behind my ribs like a piece of code I can't delete.
Victoria sends an updated intelligence packet that evening. The data is blunt: Committee cyber division operatives relocating to a centralized operational hub, resource allocationpivoting from development to deployment. The weapon isn't being refined anymore. It's being loaded.
The timeline we estimated has compressed, and Victoria's tracking suggests the Committee could be operational within days.
Tommy reads the packet at his station. I read it at mine. His typing speed increases by a fraction, and my fingers tap a sequence on the desk edge that carries the rhythm of urgency rather than algorithms.
Around midnight, when the workspace is empty and the hum is at its lowest register, I find the subroutine.
I'm deep in the countermeasure code Tommy built against the framing component, tracing logic paths, when a branch leads somewhere unexpected.
A separate module, nested inside the countermeasure framework, designed to activate independently of the primary defense.
I read it, then I read it again. Then I read it a third time, slowly, the way I read code that matters, following each logic path to its terminus and mapping the full scope of what someone built here.
The workspace is dark except for my screen. The blue-white glow catches the edges of my fingerless gloves and the Mountain Dew can beside my keyboard and the stone wall behind my monitors. The hum is low, almost subliminal at this hour, and the code scrolling past my eyes looks different from the surrounding countermeasure framework. Cleaner. More deliberate. The careful, unhurried work of someone who was paying close attention to what he was protecting and why.
The subroutine is a failsafe designed to protect my workstation, my access credentials, and my personal data partitions in the event that the Committee weapon breaches Echo Base's primary defenses.
While the main countermeasures protect the facility's critical infrastructure, this module protects me. My systems, my work, my connection to the network that keeps me functional inside this mountain.
Tommy built my safety into the bones of the base's defense.
He did it separately. He did it deliberately. A piece of code that exists for no operational reason other than his decision that my protection was worth building a dedicated system around.
His coding style is distinctive, clean and efficient with occasional dry annotations that make his code readable in a way most security infrastructure isn't. The comments on this module are minimal and functional, stripped of the dry humor and sarcasm he threads through everything else he writes.
He coded this one without his usual deflection, which means he wrote it from somewhere honest enough to scare him.
My fingers are still on the keyboard. The absolute stillness that only Tommy would read for what it actually means.
I should be angry. This is control.
