"I need to finish rebuilding the defensive framework from scratch." My voice is steady because I make it steady. The glasses are a barrier, and the barrier is holding, and behind it my mind is running contingencies at a speed that has nothing to do with calm and everything to do with the systematic refusal to panic. "The current system is compromised as a design target. The weapon was built against it. Any defense I mount using existing protocols plays into their approach. We need something new, something that doesn't exist until we build it, so there's no baseline for them to study."
"We." Kane says the word without emphasis, but the observation is clear.
"Dar and I. Her offensive capability and my defensive framework. The weapon adapts, and our countermeasures need to adapt faster. That requires two minds, and hers is the only one in this room that operates at the necessary level."
The statement is factual. It is also, in front of my entire team, an admission of need that I have never made before about anyone.
Dar doesn't react visibly. Her face maintains the clinical mask.
Her fingers, still at her sides, move in a tiny, almost invisible rhythm against the seam of her pants, one tap, then two, the opposite of the dead stillness, and I read it because I've been learning her the way she's been learning my code.
The briefing ends and the team files out.
Dylan stops in the doorway. He doesn't touch me or look at me. He looks at the display still showing the fabricated version of my coding signature and says, "When we find whoever builtthat, they answer for it," with the flat certainty of a man making a promise rather than a threat. Then he walks out.
The room empties until it's just Dar and me and the display showing my stolen signature.
Dar pauses at the door and turns back.
"The fabrication is good." Her voice is quiet, dropped into the register she used in the gym when she told me my blind spot was a philosophical choice. "But it's not you. Anyone who's actually read your code would know the difference in six lines."
She walks out. The door closes, and I stand in the briefing room staring at the display, at the ghost of my own work reproduced by a stranger with malicious intent, and what I'm thinking about isn't the weapon or the frame job or the threat to everything I've built.
I'm thinking about six lines. About the devastatingly precise way Dar just told me she knows my mind better than the person trying to destroy it.
About the fact that the most dangerous woman in this mountain can distinguish me from a near-perfect copy in six lines of code, and that capability is terrifying, and the terror feels exactly like the moment the server hum shifted after she sent her warning.
I pull up my system terminal and start building. The countermeasures need to be unprecedented, designed from the ground up by two people working in tandem.
My keyboard rhythm is rapid and even. Somewhere in the corridor, heading back to our shared workspace, Dar's rhythm will resume in bursts. The composite output of both of us, asynchronous but complementary, is the only thing standing between the Committee's weapon and the destruction of everything I've spent years building.
Everything, including whatever this is becoming between us.
10
DAR
Ihave been avoiding the implications of my own expertise for days, and the avoidance is becoming structurally unsound.
The forensic comparison tool requires deep immersion in Tommy's code. Not the surface layer, not the external-facing protocols and defense matrices that any competent analyst could study from the outside, but the deep code. The core systems, the foundational logic, the decisions he made in the earliest days of Echo Base's construction when the facility was bare rock and possibility and a man with a laptop and a mandate to build something that could keep people alive.
Reading someone's code at this depth is an act of intimacy that most people outside the technical world would never understand. Code is thought made visible. It carries the fingerprints of every decision, every compromise, every moment of brilliance and frustration and middle-of-the-night desperation that went into its creation.
Tommy's early code is rougher than his current work, built with the urgency of someone who didn't have time for elegance, and the evolution from those early functions to the sophisticatedsystems he runs now tells a story about who he was becoming while he was building this place.
I can see where he was confident. The encryption modules are clean, decisive, built with the certainty of a man who knows his strengths. I can see where he patched over uncertainty, places where the code forks into redundant pathways because he wasn't sure which approach would hold under pressure, so he built both.
I can see the elegant solutions, the moments of genuine brilliance, and the comments he left at those moments:
// this works and I don't entirely know why. don't touch it.// if this breaks, future Tommy owes past Tommy a drink.// Kane needs this by 0600. Sleep is for people who don't hold lives in their hands.
"'Sleep is for people who don't hold lives in their hands.'" The comment leaves my mouth before the decision to speak passes through any approval process. Reading someone's code is one thing. Quoting it back to them crosses a line I didn't intend to cross.
Tommy's typing doesn't falter. "Quoting my code comments is a form of surveillance I haven't consented to."
"Your code comments are a cry for therapy."
"My code comments are documentation. The fact that they occasionally read like a memoir is a feature."
