Chapter 5 #2
Kane's response is measured, precise, and exactly what I should have expected from a man who has spent decades managing the intersection of operational security and human psychology.
He listens to both of us in his office, Dar standing with her hands still at her sides and me sitting in the chair across from his desk with my glasses back on and my code rewrite already uploaded to the monitoring system.
"The probe was unauthorized," Kane says.
"The reasoning is sound. Neither fact cancels the other.
" He looks at Dar. "You're inside my facility under terms I set.
Those terms exist because the people in this mountain depend on the integrity of these systems with their lives.
If you have concerns about surveillance or monitoring, you bring them to me or to Tommy.
You don't run covert diagnostics against infrastructure you're supposed to be helping us protect. "
"Understood."
"Tommy." Kane's gaze shifts. "The internal monitoring gap she identified is real. Fix it."
"Already done."
"Good." Kane leans back. The chair creaks.
"New ground rules. Shared access to sectors directly relevant to the Committee weapon analysis.
Mutual transparency on methodology. If she runs an unauthorized operation against internal systems again, her access drops to supervised only.
Every keystroke logged, every query approved before execution.
She works in a sandbox instead of on live infrastructure.
" He looks at Dar. "I don't think either of us wants that. "
The terms are clear. Kane delivers them with the flat authority of a man who expects compliance and will enforce consequences without hesitation if compliance isn't provided. Dar nods. I nod. The meeting ends.
In the corridor outside Kane's office, Dar stops walking. I stop because she stops, and the corridor is narrow enough that continuing past her would require a proximity I'm not prepared for right now.
"The internal filter you built overnight," she says. "The one that flags unauthorized diagnostic queries from authorized workstations."
"What about it?"
"It's good. But it has a timing dependency in the third function that creates a half-second window during the query validation cycle. I'd tighten that."
I stare at her. She stares back. The corridor is narrow enough that we're standing closer than the operations center ever requires, and from this distance her eyes aren't just sharp, they're specific, reading me with the same focused precision she applied to my code, and the sensation of being read by Dar is intimate in a way I wasn't braced for.
She holds the contact for a beat longer than assessment requires.
Her fingers tap once against her thigh, a single rhythmic pulse, and then she turns and walks toward the workspace.
I watch her go. The corridor feels wider after she leaves it, the way a frequency sounds different when a harmonic drops out.
Half a second. She read my code, identified a timing vulnerability in a function I wrote in the dead hours of the night while furious, and delivered the assessment as casually as someone mentioning a typo.
The code is hours old. She's been awake for a fraction of that.
The analysis happened during the walk from Kane's office to this corridor, which means she was reviewing my filter in her head while simultaneously processing Kane's new terms and navigating the political implications of being reprimanded in a facility she didn't choose to enter.
I return to my station. The monitors glow.
The coffee is cooling. The keyboard waits with the patient familiarity of the one tool that has never failed me, and my fingers settle on the keys and start pulling up the filter code because she's right about the timing dependency and I need to fix it before the half-second window becomes another six-hour gap.
The fix takes minutes. Tight, precise, the kind of focused work that happens when the objective is clear and the motivation is a complicated mixture of professional pride and the specific irritation of being corrected by someone whose corrections are, consistently and infuriatingly, accurate.
While the filter recompiles, Dar shares her preliminary analysis of the Committee weapon.
She does it without fanfare, pulling data onto the shared display between our workstations and walking me through the attack vectors she's identified in the weapon's outer layers.
Her methodology is surgical. Clean. She dissects the Committee's code the way a pathologist dissects tissue: looking for the cause of death before the patient has finished dying.
The human-element vector is what catches my attention.
The weapon is designed to exploit the points of contact between Echo Base's air-gapped internal systems and the outside world.
Communication channels. Maintenance protocols.
Signal traffic that enters and exits the facility through routes I manage on schedules I set.
The weapon is designed around me. Not me personally, not yet, but around the functions I perform and the patterns I maintain and the routines I've established over years of running this facility's communications infrastructure.
Whoever built this weapon studied how Echo Base breathes, and the breathing is my responsibility.
I sit with that realization while Dar continues her analysis, her voice flat and precise and carrying information that reconfigures my understanding of the threat with each sentence.
The weapon isn't a battering ram aimed at our walls.
It's a key designed for our locks, and the person who cut it knows which doors we open and when.
The collaboration that follows is reluctant, uncomfortable, and productive in a way that neither of us would admit if asked.
She identifies patterns I missed because her perspective is offensive rather than defensive.
I identify structural elements she overlooked because my knowledge of the internal system she's analyzing is comprehensive in ways her external mapping never could be.
The pieces fit together with the precision of two halves of a mechanism that was built to interlock, and the picture that emerges when we combine our data is clearer and more alarming than either of us produced alone.
By evening the analysis is documented, encrypted, and queued for Kane's morning review. Dar closes her laptop and stands, and the motion breaks the working rhythm that held us for hours in a bubble of shared focus and mutual, grudging respect.
She leaves without saying good night. I watch her go and then I turn back to my screens and pull up the vulnerability she exploited last night, the one in the tertiary relay that she identified on her first day inside the mountain.
I rebuild it. Stronger. Better. Hardened against the specific methodology she used to breach it, the routing logic she favors, the proxy patterns she defaults to when she's probing a system for weaknesses.
Each layer of the new defense is calibrated against what I know of how she thinks, and I'm four functions deep before I recognize what I'm doing.
I'm designing against her. Building defenses shaped by her methodology, hardened against her approach, informed by the intimate understanding of her technical patterns that I've accumulated in less than two days of working beside her.
My code is learning her the way my ears learned the rhythm of her keyboard, automatically and comprehensively and with an attention to detail that has nothing to do with threat assessment and everything to do with the fact that her mind is the first thing I've encountered in years that makes mine work harder.
I stop typing. Push my glasses up. Stare at the screen where my code sits half-finished, every function a map of how she operates and every variable a record of what I've noticed.
I'm already learning her. The realization sits in my chest alongside the residual anger and the grudging respect and the memory of her voice saying 'I need to know whether you're watching me' with the flat honesty of someone who has been watched before and survived it and refuses to let it happen again.
I'm not watching her. My system doesn't surveil authorized workstations.
But I'm paying attention to her in ways my system doesn't need to capture, because the data I'm collecting isn't digital and the pattern I'm recognizing isn't in the traffic logs.
I sit in front of code that knows more about Dar than I'm ready to admit. Eventually I save the file and close the editor and go to bed.
Sleep takes a long time to come.