I stop. Force my rhythm back to my own pattern. The adjustment lasts minutes before the synchronization starts again.
His hands are distracting. That's the part I wasn't prepared for. Long fingers, precise on the keys, moving with a speed and certainty that I associate with people who think through their hands the way I do. When he's working through a complex problem, one hand leaves the keyboard and reaches for his coffee mug without looking, wraps around it, brings it to his mouth, sets it back, all without breaking the rhythm of his other hand on the keys. The coordination is unconscious and practiced and I'm watching it instead of watching my own screen, which is a failure of discipline I correct immediately and then fail to maintain.
His face is a problem too. The glasses hide most of it, reflecting his monitors back at me so that when I glance sideways I see scrolling code instead of eyes. But when he leansback to think, pushing his chair away from the desk and tipping his head toward the ceiling, the glasses ride up and the face underneath is sharper than the rest of him suggests. Good bone structure. A jaw that belongs on someone who takes himself more seriously than Tommy appears to. The brief exposure vanishes every time he leans forward again, replaced by the screen-reflected anonymity of the lenses, and the oscillation between glimpsed and hidden is more compelling than it should be.
He notices things. Of course he does. His job is noticing things, monitoring data streams and communication channels and the digital heartbeat of a facility that depends on his awareness for its survival, and the same attention he gives to his screens extends to the physical space around him. When my Mountain Dew gets low, a new one appears at the edge of my desk. When I adjust my screen angle for the third time, he reaches under his desk and hands me a monitor stand without comment. When I push my chair back and press my palms against my eyes because the code I'm analyzing is dense and my vision is starting to blur, he doesn't ask if I'm okay. He turns down the brightness on the overhead lighting panel and goes back to typing.
Small adjustments. Environmental modifications made with the precision of a system administrator optimizing performance. He's tuning the workspace for me the way he tunes his systems, and the efficiency of it is notable because it means he's been paying attention to me closely enough to identify the variables that affect my output without ever appearing to watch at all.
The realization lands in my gut rather than my head, which is unusual. I process information cognitively. Data in, analysis out, conclusions filed for reference. But the knowledge that Tommy has been studying my patterns with the same quiet thoroughness he applies to his infrastructure doesn't file cleanly.It sits in a space I don't have a category for, somewhere between unsettled and something warmer that I refuse to name.
Nobody has paid this kind of attention to my needs in years. The last person who noticed when I needed a break or a change in lighting was my partner at GCHQ, and the memory is a guardrail I use to pull myself back from whatever edge this feeling is approaching.
I file that too. Along with the hands, and the jaw, and the way his voice drops half a register when he's explaining something technical he cares about, which is everything.
The Committee's weapon is more sophisticated than the targeting data suggested. I spend the afternoon pulling apart the outer layers of the attack while Tommy works on hardening the channel I used to deliver the warning. His defensive methodology is conservative and thorough, the approach of a builder who understands that strength comes from structural integrity rather than aggressive response.
My approach is different. I pick locks. I find the joints and apply pressure until the system reveals its internal logic, and the Committee's weapon has a logic that becomes clearer with each layer I peel.
The delivery mechanism targets human-element vulnerabilities. Communication channels, maintenance routines, the inevitable points of contact between an air-gapped internal system and the outside world. Whoever designed this weapon understood that the strongest wall means nothing if the door opens on a schedule, and Echo Base's doors open on schedules that Tommy manages.
I don't share this analysis yet. The data is incomplete, and incomplete data presented as insight is worse than silence because it creates the illusion of understanding where understanding doesn't exist. I gather. I process. I wait until the picture is complete enough to be useful.
Late that evening, I run a small unauthorized probe against Tommy's perimeter monitoring system.
The probe is subtle. A diagnostic query disguised as routine network traffic, designed to test whether the monitoring system flags internal traffic with the same rigor it applies to external threats. If Tommy's system is watching me the way GCHQ watched me, this probe will trigger a response, and the nature of that response will tell me whether I'm a collaborator inside this mountain or a specimen under observation.
The probe runs clean. The alert system stays quiet, the monitoring feeds hold steady, and Tommy's infrastructure treats my diagnostic query as routine traffic without raising a flag.
I file that with the rest of my data. The absence of response carries information as reliably as a response would. Either his internal monitoring doesn't flag traffic from authorized workstations, which is a vulnerability, or he noticed and chose not to react, which is restraint.
I don't know which interpretation is correct, and not knowing is a condition I find less tolerable than most people because uncertainty is the space where systems fail and people get killed.
By midnight the operations center is empty except for the glow of my screens and the server hum and the deep quiet of a mountain at night. Tommy left an hour ago, and the absence of his keyboard rhythm is louder than the rhythm itself was. My station feels wider with his chair empty. The space between our desks, which felt manageable during the day, registers like a null value where a signal used to be.
Everyone else has retreated to quarters, to sleep, to whatever version of normal life exists inside a military facility inside a mountain where the corridors are carved from rock and the exits require authorization.
I can't sleep. My internal clock is calibrated to screens and deadlines, not the circadian rhythms of a communal schedule, and the mountain hums differently at night. Deeper. The ventilation system drops to a lower setting. The server hum fills the space that daytime activity occupies, and the sound is constant and strange and more intimate than I want it to be, as if the facility is breathing in its sleep and I'm the only one awake to hear it.
I walk the corridors. Fingertips trailing stone. The rock is cold and rough and ancient, and touching it grounds me in the physical reality of where I am in a way that my screens can't. I am inside a mountain. In Montana. Surrounded by armed operators and encrypted servers and a man whose keyboard rhythm I've already memorized.
The overlook appears at the end of a corridor I haven't explored yet. A passage that leads up rather than further in, carved at a steeper angle than the main corridors, and at its end an opening in the rock where the mountain gives way to sky.
Montana fills the gap. Night sky. Stars. Ridgelines cutting black shapes against a blue-dark horizon. The air hits me like a physical force, cold and clean and carrying the smell of pine and distance and things that grow in sunlight. My lungs expand in a way they haven't since I entered the mountain, and the sensation of breathing air that hasn't been recycled through a filtration system is sharp enough to register as something close to relief.
I stand there. The wind moves across the opening and touches my face, and my fingers are still for the first time in hours, hanging quiet at my sides because there is no code to process and no problem to solve and the sky is so vast and uncomplicated that the part of my brain that runs constant analysis doesn't know what to do with it.
The alarm is silent.
That's the first thing I notice, and the noticing comes with a spike of professional admiration because Tommy designed his alert system to differentiate between threats that require audible warning and threats that require quiet mobilization. The alarm that reaches me is visual: a pulse of amber light from the emergency LED strip embedded in the corridor ceiling behind me, three flashes in sequence, a pattern that isn't in any orientation briefing I received.
But patterns are what I read, and three amber pulses with one-second intervals means external perimeter, sector north, human contact.
Someone is outside the mountain.
My body shifts from overlook-stillness to operational-stillness, the difference between the two measured in muscle tension and pupil dilation and the specific redistribution of weight that puts me on the balls of my feet with clear lines of movement to the corridor behind me.
The comm system crackles. Tommy's voice, stripped of humor, running at the clipped frequency I’ve heard him use during intense communications. As much of a jokester as he is, the man does know when the time for humor has passed.
