That's new. And inconvenient. And exactly the kind of signal I should be filtering out of my processing, given that this woman breached my security infrastructure and is currently standing in my vehicle bay as a potential threat rather than a person whose shoulder mechanics I should be studying through a camera feed.
The fingerless gloves are practical. The rainbow hair is defiance. The oversized hoodie is armor disguised as indifference. Every element of her visual presentation is a message: I am not part of your world, I do not intend to become part of your world, and any attempt to integrate me will encounter resistance calibrated to the effort.
I've been reading systems my entire adult life. People are just systems with better obfuscation.
Kane shakes her hand. I can't hear the audio from this feed, but I can read the interaction in body language. Kane is being Kane: measured, authoritative, giving her exactly enough warmth to signal respect without conceding territory. She meets his gaze with the direct focus of someone who has dealt with institutional authority before and learned that the appropriate response is neither deference nor defiance but the flat, professional acknowledgment that authority exists and she is aware of it and she has chosen, for the moment, to operate within its parameters.
She scans the bay while Kane talks. Her head moves in small, precise increments, cataloging entry points, camera positions, structural features. Mapping the space the way she maps networks. I can almost see the schematic building behind her eyes, each observation clicking into place like a node in a topology diagram.
Victoria walks with her and Kane toward the operations center. I track them through camera feeds, switching angles as they move through corridors. She touches the walls. I notice that, and the noticing catches on something because it's such a strange, specific gesture. Her fingertips trail the stone as she walks, making contact with the rock itself, and I realize she's grounding herself. Confirming the physical reality of where she is. The mountain is real. The stone is cold. She is inside a facility she imagined had to exist through months of signal analysis, surrounded by people who could decide she's a threat and act on that decision before she reached the nearest checkpoint.
Her fingers keep moving after they leave the wall. Tapping against her thigh, fast and rhythmic, patterns that look too structured to be random fidgeting. She's processing. Working through the input of being inside the mountain, inside the system, inside the space she breached from the safety of a dark apartment probably full of screens, servers, old take-out and flat soda.
They reach the operations center. I'm there, because avoiding the introduction any longer would require an explanation I don't have, and Kane is the kind of commander who notices when his people aren't where they said they'd be.
I stand when they enter. My workstation is behind me, monitors glowing, the familiar configuration of screens and keyboards and the coffee mug with its permanent ring stain all arranged in the pattern I've maintained for years. The main monitoring dashboard occupies the center screen, showingsystem status across every layer of Echo Base's infrastructure: active defense nodes in green, communications relays in blue, passive monitoring feeds in amber, and the full network topology mapped in real time. My territory. My cockpit. The place where I am most completely myself, and right now it feels less like a stronghold and more like a display case.
"Tommy Hale," Kane says. "Our tech and signals specialist. He built the systems you came through to get here."
"Built is generous." My voice comes out the way it always does, light and quick, humor deployed ahead of everything else like a scout sent to check for ambush. "I assembled them from salvaged hardware and unreasonable expectations. They've held up better than I had any right to hope."
Dar looks at me for the first time.
Her eyes are sharp. Dark-lined and focused, and when they land on mine the contact is direct enough that my hand moves toward my glasses before I can stop it. I push them up. The gesture buys me a barrier and a breath, because the full weight of this woman's attention is more intense than I anticipated from the other side of a camera feed.
Up close, the angles of her face are precise rather than harsh, and her mouth holds that flat line of concentration that I've been watching through security cameras, and the translation from pixels to person is carrying a fidelity that my professional composure was not adequately prepared for. She's smaller than she looked on the monitors. Sharper. Realer in a way that sends heat up the back of my neck.
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 greenindicators, 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 hermouth 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.
