Chapter 1
TOMMY
M ercer's extraction window is closing, and the corridor outside the consulate is not empty.
"Two contacts, south entrance. Closing fast." My voice is level because level is the only option when someone's life runs through the wire between my screen and their earpiece.
Three monitors track the situation: satellite thermal on the left, building schematics center, Mercer's bio signal on the right, his heart rate controlled and steady in a way that tells me he's aware of the contacts and trusting me to do my job.
"Hold position. Let them pass."
Silence on the line. Mercer holds. I can hear him breathing through the comms, shallow and measured, each exhale controlled with the discipline of a man who understands that sound travels in enclosed spaces, and the intimacy of listening to someone hold very still when stillness is the only thing between them and a firefight fills my earpiece with a weight that settles in my own lungs.
The thermal signatures drift south. My jaw is clamped tight enough to ache.
Both hands hover over the keyboard, one on the comms override, one on the emergency channel that would flood the frequency with Kane's voice and mobilize the secondary team.
The signatures pass Mercer's position and keep moving, their trajectory carrying them away from the service corridor, and the seconds between each step register in my chest like a countdown I can't control.
"Clear. Move now, service exit on your right."
He moves. I track him through the building, adjusting his route twice when the thermal overlay shows activity he can't see. The service door opens. The vehicle is waiting.
"Package secure," Mercer says. "Headed to rally point."
The operations center exhales. Kane nods once. Sarah pulls her headset down around her neck. Dylan uncrosses his arms.
The collective decompression of people who just watched one of their own navigate a kill zone with nothing between him and a body bag except my infrastructure and my voice.
My hands are steady on the keyboard. They're always steady when it matters.
The room clears over the next few hours. Kane first, then Dylan, then Sarah with a look over her shoulder that checks on me the way she checks signal integrity, quietly and out of habit.
I stay because the overnight diagnostics are mine and because the post-operation silence is when I do my best work, alone with the servers and the knowledge that the system performed.
The relays held. The comms were clean. Mercer is alive because the infrastructure between my screen and his earpiece delivered the right words at the right time.
That infrastructure is mine. I built every layer of it, and tonight it held.
The base settles into its deep-night rhythm, the corridors emptying until the only sounds are ventilation and the steady hum of the servers below my feet, and I settle with it, shifting from the focused intensity of a live operation to the quieter vigilance of the overnight watch.
The anomaly appears on my secondary monitor at 3:47 AM, a flicker in a system that doesn't flicker.
I almost miss it. My primary screen is running the overnight diagnostics I wrote months ago, the ones that crawl through Echo Base's communication relays and log every packet that crosses the threshold between our network and the outside world.
The digital equivalent of checking the locks before bed, except I check them every few hours because sleep is a suggestion and paranoia is a professional requirement.
The flicker is on monitor three. Not the main display, not the threat board, not any of the feeds that would trigger an audible alert if something crossed a threshold.
Monitor three runs my personal watchdog, a background process I built during the first year at Echo Base when the walls were still bare rock and the server room was three machines held together with zip ties and optimism.
The watchdog monitors traffic patterns on channels that don't officially exist. Ghost frequencies. Dead drops in the digital landscape that I maintain like spiderwebs, delicate and deliberately invisible, designed to catch anything that brushes against the edges of our infrastructure.
Something just brushed.
I set down my coffee. It's cold. It's been cold for hours, but the mug is a fixture at this point, a ceramic monument to the ambition I felt when I poured it.
My fingers find the keyboard without looking. The watchdog's log shows a single entry, timestamped minutes ago.
A data packet arrived through a channel I built as a tripwire, a frequency so deeply buried in our communications stack that finding it would require someone to map the entire relay system, identify the one thread that doesn't connect to any active process, and recognize it as a door rather than a wall.
Someone found the door.
My stomach drops. I push my glasses up and lean closer to the screen, pulling the log entry apart with keystrokes that come faster than conscious thought.
The packet is small. Tiny. A single word, encrypted with a cipher that takes me longer to break than anything I've encountered in years.
The key rotation alone burns through my initial decryption approaches in minutes.
I keep trying, adjusting parameters, feeling the shape of the cipher's logic with each failed attempt the way a safecracker feels tumblers through fingertips.
Whoever designed this understood the same cryptographic principles I build my systems on, and they applied them with a fluency that makes my throat tight, because every failed decryption tells me more about the mind behind it, and what it tells me is that this mind is operating at a level I rarely encounter outside my own work.
The cipher finally gives. The characters resolve on screen, one word, and the operations center contracts around me, the hum of the servers suddenly too loud, the air suddenly too still, the space behind my chair suddenly occupied by the weight of someone else's knowledge of this place.
Compromised.
I stare at it.
The server hum fills the silence, and for the first time since I built this place, the sound registers differently.
Less like a heartbeat. More like breathing in a room where I just realized I'm standing next to someone I can't see.
One word. No sender identification, no routing metadata that survives more than surface analysis, no digital fingerprints beyond the cipher itself.
Whoever sent this knew how to strip a message down to its skeleton and still make it speak.
My hands are already moving, pulling the intrusion path apart layer by layer. The packet entered through the tripwire channel, which means someone mapped our external relay system with enough precision to find the one thread I never documented.
The relay design is mine. I built it, I maintain it, and the only complete blueprint exists in my head and in an encrypted file on a drive that never touches a network.
Nobody has that blueprint. Nobody should have that blueprint.
The routing is clean. Efficient. Whoever built this path understood distributed relay systems at a level that narrows the suspect pool to a handful of people on the planet, and I know most of them by reputation.
The cipher is elegant in a way that makes my jaw tight, because elegance in encryption is a signature as distinctive as handwriting, and this handwriting is fluent in a dialect I recognize.
The cipher is government trained, a signals intelligence product. The structure carries institutional fingerprints, the kind of disciplined key rotation methodology that comes from working inside a national signals program rather than learning it freelance.
European, probably. Possibly British.
The modifications suggest someone who absorbed an institutional framework thoroughly and then departed from it with the confidence of a person who understood the rules well enough to know which ones were wrong.
I can narrow the origin to a region but not to a specific agency, and the agency matters, because the agency tells me the training pipeline, and the training pipeline narrows the candidate pool to a list short enough to work with.
I sit back in my chair and push my glasses up again. The gesture buys me a few seconds of looking at something other than the word on my screen, and I use every one of those seconds.
If the message is accurate, someone is telling me Echo Base has a vulnerability I missed.
If it's a provocation, someone is testing whether I'll react and how fast and in what direction.
If it's a trap, it's the most sophisticated piece of bait I've ever seen, and I have seen bait designed by intelligence agencies with budgets larger than most countries' GDP.
The intrusion path is what keeps pulling at me. I trace it again, slower, mapping each relay point, each proxy, each handoff. The routing spans continents. More than a dozen proxy chains. Every single one is clean, anonymized with precision that borders on artistic.
But there's a structural logic underneath the randomness, a pattern in the proxy selection that tells me the person who built this path thinks about networks the way I think about them.
As living systems. As organisms with circulation and pressure points and vulnerabilities that cluster at the joints where different systems meet.
Whoever found my door didn't break in. They knocked.
That distinction is what keeps the cold sweat going. A break-in would mean brute force, automated systems, the kind of industrial-scale operation that nation states deploy against each other. I know how to fight that.
I have been fighting that since Kane handed me a laptop in a room full of bare rock and said he needed someone to build something that didn't exist yet.
Every firewall, every intrusion detection layer, every tripwire in Echo Base exists because I spent years imagining the worst things the worst people could throw at us and engineering countermeasures before the threats materialized.