Chapter 3 #3
Her gaze moves past me to the monitoring dashboard on my center screen, and I watch her read it the way I watch analysts read signal intercepts, with the focused absorption of someone extracting meaning from structured data at speed.
Her eyes track across the network topology.
Pause on the node map. Move to the active defense layer and its green indicators, then to the communications relays in blue, then to the amber passive monitoring feeds.
I can see her correlating the nodes, cross-referencing which feeds report to which defense layers, identifying the data flow between passive collection and active response.
"Your encryption rotation is elegant," she says.
Her voice is flat. Precise. Stripped of anything that doesn't carry functional weight.
"Your tertiary relay node is collecting traffic data but it's not feeding to your active defense layer.
The node is amber on your dashboard, which means passive monitoring only.
No alerts, no automated response, no integration with the systems that would flag anomalous traffic passing through it.
" She looks at me. "That's a blind spot. I'd fix that."
My glasses are suddenly very interesting.
I push them up, which is what I do when I need a barrier between my face and whatever is making me feel exposed, and this woman just walked into my operations center and read a vulnerability off my own monitoring dashboard in the time it might take me to deliver a self-deprecating joke.
"The tertiary relay is passive by design," I hear myself say.
"Separating passive monitoring from active defense prevents cascading failures.
It's a feature." I hear the sentence land and add: "And yes, I'm aware that 'it's a feature, not a bug' is what every engineer says right before someone demonstrates that it's definitely a bug. "
"It's a door," she says, and the correction is delivered without mercy or amusement. "Passive nodes that don't report to active defenses are gaps in your perimeter. You just don't know they're open until someone walks through one."
The room holds its breath. Kane is watching with the patient attention of a man who is learning something useful about both of us. Victoria has the ghost of something at the corner of her mouth that might be approval or might be amusement, and with Victoria the distinction is mostly academic.
I want to argue. The tertiary relay is passive by design, a monitoring node positioned to collect traffic data without interacting with the active defense layer, and the separation between passive and active systems is a deliberate choice I made to prevent exactly the kind of cascading vulnerability that occurs when too many nodes are interconnected.
I want to explain this. I want to defend the decision with the technical reasoning and the operational logic and the three years of flawless performance that validate it.
Instead I say, "I'll look at it."
Because she's right. The relay is a blind spot.
I built it that way on purpose, and I was wrong, and the fact that she read it off my own dashboard in less time than it takes me to finish a cup of coffee is a piece of data that I need to process before I can respond with anything other than defensive sarcasm.
Kane assigns her a workstation. Adjacent to mine, because the project requires collaboration and collaboration requires proximity and proximity, in a facility inside a mountain with limited workspace, means sitting close enough to hear each other breathe.
She sits down without ceremony. Pulls a laptop from her bag with the practiced efficiency of someone who has set up workstations in hostile environments before and considers a military compound full of armed operators merely the latest variation.
The laptop is stripped down and hardened, the casing bare of stickers or decoration, functional in a way that contrasts with the rainbow hair and the punk aesthetic like two different operating systems running on the same hardware.
Her fingers find the keyboard and start moving.
No permission requested. No protocols observed.
No acknowledgment that she's sitting in someone else's workspace, in someone else's facility, surrounded by someone else's systems. She opens her laptop and begins working as if the desk has always been hers and the mountain has always been her mountain and the space between her screen and mine has always been this narrow.
I sit down at my own station. My monitors glow. My keyboard is where I left it. The coffee mug with the ring stain sits at my hand, and the second drawer where I keep the dark chocolate is closed, and everything about my workspace is exactly the same as it was an hour ago.
Except for the sound.
Her keyboard has a different rhythm than mine.
My typing is rapid and even, a steady percussion that Sarah once described as sounding like a very fast, very focused rain.
Dar's typing comes in bursts. Rapid-fire clusters separated by pauses of variable length, the pattern of someone who thinks in concentrated intervals and then executes in focused sprints.
The sound of her keyboard fills the gaps in the sound of mine, and the combined rhythm is something I've never heard in this space before.
A duet where there's only ever been a solo.
I stare at my screen and the code I should be writing and the channel I should be hardening and the blind spot I should be reassessing, and instead I'm listening to the sound of someone else's fingers on keys beside me.
The rhythm is already filing itself into the background frequency of my operational environment alongside the server hum and the ventilation system and the echo of boots on stone.
She's inside the mountain. Inside my workspace. Close enough that I can catch something faintly citrus underneath the recycled air, close enough that when she shifts in her chair the motion enters my peripheral vision and I track it involuntarily, the way my systems track anomalies.
She corrected my defensive philosophy in fewer sentences than most people need to order coffee, and my pulse is still running at a rate the situation doesn't justify.
I'm choosing not to examine why, because examining it would require admitting that being outperformed by this woman is producing a response that has very little to do with professional humiliation and quite a lot to do with the fact that competence has always been the thing that undoes me, and Dar Atterly is the most competent person who has ever sat this close to me.
I start typing. Focus on the channel. Focus on the code.
Focus on the work, because the work is where I'm solid and certain and not at all unsettled by the fact that someone who thinks in systems the way I do is sitting close enough to touch and the rhythm of her keyboard is already becoming part of the frequency of this room.
The sound of two keyboards fills the operations center, her bursts and my steady rain, and the rhythm they make together already sounds like trouble.