Chapter 6 #3
The parallel isn't lost on me. I'm looking for vulnerabilities. His happen to be physical.
"Hold this." He hands me a diagnostic cable.
Our fingers overlap on the housing, and his are warm despite the cold, and mine are freezing, and he wraps his hand around mine for a fraction of a second longer than the transfer requires.
The contact sends information through my nervous system that bypasses every analytical framework I have.
"Your hands are freezing."
"My hands are always freezing. It's a feature, not a bug."
"That's my line."
"It's everyone's line. You're not special."
He laughs, short and surprised, and the sound bounces off the server racks and comes back softer. His face when he laughs is open and undefended, the kind of face that makes you want to say things that can't be unsaid, and the urge is strong enough that I bite the inside of my cheek to prevent it.
"Nobody ever accused me of being special."
The lie in that sentence is so transparent I almost call it out.
Tommy built this entire facility's nervous system from secondhand hardware and salvaged parts.
The encryption I've been admiring for over a year was designed by the man currently on his knees with cable dust in his hair and his glasses slightly crooked and his hands sure on connections that keep people alive.
He is special. The fact that he doesn't know it is the most dangerous vulnerability in this mountain, and it isn't one I can patch.
We work side by side in the cold for hours. The diagnostic reveals no hardware compromise, which is good news wrapped in bad: the weapon's purely digital, designed for remote deployment, which means the Committee doesn't need physical access to Echo Base to destroy it.
"The delivery mechanism uses a modified distributed denial protocol," I say, pulling data off the diagnostic tablet.
"But it's designed to infiltrate, not overwhelm.
The denial's a smoke screen. While your systems manage the load, the actual payload deploys through your communication channels and embeds in your internal network. "
"Trojan horse."
"Trojan horse with a postgraduate degree. The payload's adaptive. It learns your system's responses in real time and modifies its approach. Standard countermeasures won't work because it evolves past them."
Tommy's leaning against the server rack beside me, arms crossed, glasses reflecting the diagnostic readouts.
Close enough that I can feel the heat coming off him despite the chill, and my body's oriented toward that warmth the way a cold system orients toward a power source, instinctively, without conscious input.
When he turns his head to look at me, the movement brings his face close enough to make my breath catch before I can suppress the response.
"How long do we have?"
"Based on the deployment timeline in the original directive and the acceleration patterns I've tracked? Weeks at most."
"Weeks to rebuild a defense system against a weapon that adapts in real time."
"Weeks to build something new. Your existing defenses aren't the answer. They're the target. We need to design countermeasures from scratch, based on the weapon's own logic, using its adaptive capability against it."
"We."
The word sits between us, small and loaded.
I've been operating alone for over two years.
The pronoun feels foreign, like a loan word from a language I used to speak but stopped practicing.
The way he says it, quiet, without inflection, without the humor he usually wraps around anything sincere, makes it sound like more than a pronoun.
It sounds like an offer and offers are the most dangerous things in my world because accepting one means trusting the person who made it.
"The weapon targets the interface between your internal systems and your external communications. You understand the internal side. I understand the external side. Neither of us can solve this alone." The admission costs me something. It also happens to be true.
Tommy uncrosses his arms and pushes off the server rack.
In the narrow aisle between equipment, standing in front of me means standing close.
His chest is level with my eyes, and the cotton of his shirt is right there, and the cold air carries his warmth to me in waves I can't ignore.
The overhead light catches the edge of his jaw in a way that makes my fingers twitch against the diagnostic tablet.
"Then we build it together," he says, slowly, without humor, without deflection. His eyes, without the glasses, are on me with the full weight of his attention, and the full weight of Tommy's attention is heavier than I expected.
I hold it for a beat too long, then turn back to the diagnostic tablet because there's a limit to how long I can sustain eye contact with someone whose mind I respect and whose body I'm trying not to think about, and those two boundaries are collapsing into each other faster than I can reinforce them.
I nod once. The agreement costs me more than the word would have.
We walk back to the workspace in silence that vibrates with everything we're not saying. My skin's still cold from the server room. The places where his hands touched mine aren't.
Tommy drops into his chair, opens a new project file, and starts laying the foundation for a countermeasure framework.
I settle into my station, pull up my analysis of the Committee's adaptive protocols, and begin mapping the attack logic into a format his defensive systems can ingest.
Our keyboards start. His rhythm. My rhythm. Two separate patterns, two distinct frequencies, operating independently in the same space.
Sometime later, I realize the patterns have synchronized.
The pauses in my bursts are landing in the gaps between his sustained runs, and his speed picks up when my output increases, and the composite rhythm of both of us typing is something neither of us designed.
It happened organically, without communication, the way two systems start to sync when they're processing the same data stream.
I don't mention it. Neither does he.
Late that night, Tommy reaches under his workstation and pulls a can of Mountain Dew from the mini fridge he's got tucked beneath the desk.
He doesn't look at me when he sets it on the edge of my workstation, doesn't pause his typing, doesn't acknowledge the gesture in any way.
The placement is precise, exactly within my reach, exactly where my hand would naturally land if I reached for a drink without looking away from my screen.
He stocked it. He positioned it. He placed it at the precise moment my energy started flagging, which means he's been monitoring my productivity the way he monitors his systems, noting when output drops and correlating it with probable causes.
He's been studying me the way he studies threat patterns, and the study has produced actionable intelligence, and he's deploying it to manage my environment without asking my permission.
It should bother me. The quiet control of it, the presumption of knowing what I need before I do, the way he's engineering the space around me to keep me functional and comfortable on his terms. It should register as a boundary violation from a man who controls the entire facility I'm living in.
It doesn't bother me. And the fact that it doesn't is the most concerning data point I've collected since I arrived.
I take the Mountain Dew without thanking him, pop the tab, and drink. The can is cold and green and familiar, the one constant from my loft that exists inside this mountain.
The man who put it here is typing at arm's length away with his sleeves rolled up and his glasses reflecting code and his quiet, deliberate attention wrapped around me like a system I didn't notice being built until I was already running inside it.
The server hum holds steady beneath us. The screens cast their light. The weapon we're building against ticks closer to deployment while two people who don't trust anyone learn, keystroke by keystroke, how to work as one system.