Chapter 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."
"Correct."
"That's a violation of the terms Kane set."
"Kane's terms assume I trust your system." She pivots in her chair, and the full focus of her attention lands on me with the concentrated precision of a laser finding its target. "I don't trust anyone's system. That's why I'm still alive."
The operations center is empty except for us.
Sarah won't arrive for a while yet. Kane's morning rounds haven't brought him past this section.
We are alone in a room full of screens and servers and the cold hum of infrastructure that suddenly feels less like my territory and more like a contested space.
The gap between our workstations has never felt this small.
She's angled toward me in her chair, and from this distance I can count the small silver earrings climbing her left ear, and I should not be cataloging her jewelry during a security confrontation, and yet here I am, furious and fascinated in equal measure and unable to determine which response is winning.
"You're inside my facility. Using my infrastructure. Eating food my team cooked and breathing air my ventilation system recycled. The minimum standard of professional conduct is not running covert operations against the systems you're supposed to be helping me protect."
"The minimum standard of professional competence is catching an internal probe in real time rather than during a manual log review six hours after execution."
My jaw tightens. The retort is ready, loaded and aimed, something sharp about the difference between a probe run from a position of trust and a probe run from the outside, about the gap between testing a system and betraying the access you've been given, about the specific flavor of hypocrisy involved in accepting collaboration with one hand while undermining it with the other.
Instead I hear myself say: "Why?"
The question comes out quieter than I intended. Less angry. More genuinely curious, which is not the tone I was going for and reflects a failure of emotional regulation that I would normally cover with a joke.
Except the part of my brain that generates jokes is currently occupied with the problem of understanding why a woman who sent me a warning, traveled voluntarily into a mountain full of people who don't trust her, and spent a full day working beside me in productive silence would then test my defenses the first chance she got.
Dar's expression doesn't change. Her fingers are still motionless on her keyboard, and the stillness carries the same weight it carried the first time I noticed it through a security feed: deliberate, controlled, the physical signature of a mind operating at full capacity on a problem it considers important enough to require every available resource.
"Because I need to know whether you're watching me."
The words land clean, stripped of embellishment and justification, a flat honest statement delivered with the precision of someone who has learned that clarity costs less than ambiguity.
"I need to know whether the system I'm operating inside is surveilling my activity, logging my keystrokes, monitoring my communications, and building a profile of my behavior without my knowledge or consent.
I need to know because the last system I operated inside did exactly that, and then it used the data it collected to construct a narrative that blamed me for a failure I predicted in writing, and my partner died because that system decided institutional self-preservation was worth more than one analyst's documented warnings. "
The operations center hum fills the silence that follows.
The servers breathe their constant breath.
The ventilation system pushes air through ducts carved into stone.
Every sound I've built into this place fills the space between us while I process what she just said and what it means and what it costs her to say it.
"I'm not watching you," I say. The irony of this statement, delivered by a man who has spent time memorizing her keyboard rhythm and learning what her hands do when she's hiding something, is not lost on me.
But there's a difference between surveillance and attention, and the difference matters even if the distinction is getting harder to maintain by the hour.
"The probe suggests that's true. Your internal monitoring doesn't flag traffic from authorized workstations. That's either a deliberate design choice reflecting a trust-based security model, or it's an oversight."
"It's a design choice."
"I know. That's why I needed to test it. Because a trust-based internal security model tells me something about the person who built it, and what it tells me is more useful than any briefing document."
I take my glasses off. Clean them on my shirt. The world goes soft and unfocused without them.
For a moment the woman across from me is a blur of color and angles and the sharp outline of someone who just explained, without apology, that she tested my defenses because she needed to know what kind of man I am before she could decide whether to trust me.
The anger isn't gone. It's still there, sitting beside the understanding she just provided like two incompatible files trying to occupy the same directory.
She violated the terms of her access. She also did it for reasons that I understand in a way that makes the violation more complicated rather than less.
"Kane needs to know," I say.
"Agreed."