But the knowledge sits in the workspace between Tommy and me like a weight we both carry and neither acknowledges: the Committee isn't just building a digital weapon. They're mapping the physical facility. The attack, when it comes, will target both the infrastructure inside the screens and the infrastructure inside the stone.
Tommy types a new line of code into his perimeter monitoring system. I recognize the function as he writes it: an additional layer on the north-sector sensors, calibrated to detect the specific thermal signature of a single human on the ridgeline approach.
He built it in four minutes. He didn't ask my opinion. He didn't need to.
The hum settles. The screens go green. And the mountain holds its breath a little tighter than it did before.
I return to the overlook hours later, after the alert has stood down and the base has settled back into its nighttime register. The sky is the same sky. The wind is the same wind. But the opening in the rock feels different now, less like a window and more like a position, and the part of me that spent two years operating alone in a loft where the only threat was digital isrecalibrating to a world where the threats walk on two legs and carry cameras.
Footsteps behind me. Deliberate. Not trying to be quiet, which means not trying to startle, which means whoever is behind me wants me to know they're there before I turn around.
Dylan Rourke stands at the corridor entrance. The corridor light catches him from behind, and his face is half shadow, half illumination, the kind of lighting that a cinematographer would use for a character whose intentions are meant to stay ambiguous. His posture is loose in the way that trained operators are loose, the deceptive relaxation of a body that can transition from stillness to violence in a fraction of a second without the intermediary step of tensing up.
His eyes assess me the way they've been assessing me since I arrived. Threat calculation. Risk analysis. The cold, continuous math of a man who has already lost everything that mattered and has rebuilt his life around the principle that the people remaining in his perimeter will not be lost the same way.
I hold the eye contact. My fingers are still at my sides. The mountain wind moves between us.
Rourke doesn't speak. He stands in the corridor entrance and he watches me standing at the overlook, and the silence between us carries the specific weight of a judgment being made by someone whose criteria I haven't been given access to.
I turn back to the sky. Let him watch. He'll either trust me or he won't, and the decision will be based on what I do in the weeks ahead, not what I say tonight in a corridor carved from granite while the stars do their indifferent work above us.
Behind me, Rourke's breathing is even and controlled. A man who has learned to carry grief in his body the way other people carry tension, always present, never put down, and the sound of it mixes with the wind and the distant hum of the serversbelow and becomes part of the frequency of this place that I am beginning, despite every instinct telling me otherwise, to learn.
5
TOMMY
Icatch the probe long after midnight, hours after she ran it, and the delay is what infuriates me.
Not the probe itself. Not the fact that she tested my system without authorization, without asking, without the basic professional courtesy of mentioning it during the hours we spent working side by side while I adjusted her monitor brightness and handed her a Mountain Dew and generally behaved like a man who assumed the person beside him was operating in good faith.
The delay. Hours. She ran a diagnostic query through my internal monitoring system the previous evening, disguised as routine network traffic, routed through her authorized workstation credentials, and designed with enough subtlety that my real-time detection systems didn't flag it during its execution window.
I found it during a routine log review. Not the live monitoring. Not the alert system. Not any of the automated defenses I built to catch exactly this kind of intrusion. I found it manually, reading raw traffic logs in the dead hours before dawn because I couldn't sleep and the logs are what I read when the alternative is lying in bed thinking about the sound of someone else's keyboard in my operations center.
She got hours of clean access to data about my internal monitoring protocols before I noticed, and those hours matter because they represent the gap between what my systems should have caught and what they actually caught, and that gap is my fault.
My system should have flagged internal diagnostic queries that don't correspond to scheduled maintenance. I didn't build that filter because I never anticipated someone running unauthorized diagnostics from inside the facility, because the people inside this facility are people I trust, and trust has been the foundational assumption of my internal security model since the day I started building it.
The assumption held for years. Then Dar sat down at a workstation I assigned her and proved it wrong in less than a day.
I spend the remaining hours before dawn rebuilding the internal monitoring filter, writing code with the focused fury of a man who has just been shown that the wall he built has a gap in it and the person who found the gap is sleeping down the corridor.
The code comes fast. Clean. Angry in the way that good code can be angry, each function precisely targeted at the vulnerability she exploited, each variable named with the clipped efficiency of someone who is engineering a solution while simultaneously composing the confrontation that will happen in the morning.
Dar arrives and begins working. Mountain Dew open, laptop displaying something I can't see from my angle, fingers moving in those rapid bursts that I've already cataloged as her processing pattern. She doesn't look up when I set my coffee down. She doesn't register my presence with any visible change in posture, rhythm, or attention.
"We need to talk about the probe you ran last night."
Her fingers stop. Not gradually, not a trailing deceleration. Full stop. Every digit motionless on the keys, the sudden absence of motion as stark as an alarm in a quiet room. She turns her head and looks at me, and her expression is flat and composed and carrying absolutely nothing that could be mistaken for guilt.
"Took you ten hours."
The correction is precise and delivered without emphasis. She counted from the moment she ran the probe to the moment I mentioned it, not just the gap between execution and detection but the additional hours between detection and confrontation. Every one of them filed as data about my response time. Her face shows nothing. Her mouth is that flat line, her eyes are steady, and the composure is so thorough that breaking through it becomes, for one irrational second, the only thing I want to do. Not professionally. Just because the idea of this woman showing a reaction she hasn't calculated in advance is suddenly and inappropriately compelling.
I push my glasses up. The gesture buys me two seconds and a barrier, and I need both because the alternative is saying something that reflects the specific cocktail of professional indignation and reluctant admiration that her response just triggered.
"You ran an unauthorized diagnostic query against my internal monitoring system. Using credentials I assigned you. Through infrastructure I gave you access to in good faith."
