Echo: Code (Men of Echo Ridge #7)

Prologue

DAR

T he channel closes, and the word I just sent hangs in the air of my loft like smoke from a detonation I can't take back.

Compromised.

One word. Typed and transmitted through a door I spent months building from signal fragments and pattern recognition, aimed at a facility that doesn't officially exist, warning a system administrator I've never met that the Committee is coming for everything he built.

The channel is dead now, the connection severed the moment the message delivered, and the only proof it was ever open is the cursor blinking on an empty field and the knowledge settling into my bones that I just violated every rule I've operated under since the day I walked out of GCHQ, Britain's signals intelligence agency, and swore I would never make myself visible to another institution again.

My hands are in my lap. Still. Dead still on my thighs, fingers motionless, and the stillness is its own kind of alarm because my fingers are never still.

They tap. They drum. They work through problems kinetically, translating code into motion the way other people translate thoughts into speech.

When they stop, it means the problem has exceeded the capacity of background processing and requires every resource I have.

The problem sitting in front of me now is the largest I've faced since the morning I signed a nondisclosure agreement and walked away from the only institution I ever trusted.

The loft is dark. It's always dark. Multiple monitors provide the only light, their glow painting exposed brick and steel beams in shifting blue-white patterns that have become the closest thing I have to windows.

The warehouse glass runs floor to ceiling along the east wall, industrial panes that I painted black from the inside when I moved in.

From the street, the building looks abandoned.

Boarded entry, graffiti on the loading dock, the kind of urban decay that keeps squatters circling and city inspectors filing complaints that go nowhere because the ownership records lead through shell companies to a dead end.

I bought the building through three layers of corporate abstraction.

I'm the only tenant. The paper trail doesn't exist.

The rest of the space reflects the same priorities.

The loft is vast and I use a fraction of it.

My desk and monitors occupy an island in the center, on open concrete floor that stretches to the walls in every direction.

Cables run across the concrete in patterns that look random but follow routing logic I established during the first week and haven't changed since.

External hard drives sit in a row beside the left monitor, each one labeled with a date and an encrypted reference code.

A kitchenette in the far corner holds a coffee maker I haven't used in weeks, boxes of energy bars, and a collection of Mountain Dew cans in various stages of consumption that have spread across the available counter like a colony establishing territory.

The bathroom is the only walled room, a cinder-block box I built myself when I moved in.

The loft holds everything I need for the work and nothing else.

Anything personal would be something to secure, something to protect, something that could be used against me, and I stopped carrying those liabilities the day I left British intelligence after they decided to blame their failure on me—a failure that got my partner killed.

The Committee's targeting data is stored on encrypted drives now, copied and secured and wiped from my primary system.

Hours of analysis distilled into a single conclusion: someone inside the Committee built a digital weapon designed to locate and crack open a facility that has managed to keep its location a secret, and the deployment timeline gives them weeks, not months.

The weapon is surgical, designed to infiltrate through the human element, the communication channels, and the maintenance routines.

Whoever built it studied the facility's system administrator long enough to map the patterns and learn the rhythms and construct a key for one specific lock.

I could have sold that intelligence. The broker market would have paid enough to fund my operation for a year.

Instead I sent a warning to the one person whose code I respect, through a channel I built from the gap between elegance and intention in his relay design, because selling it would have meant the warning arrived too late and the people working out of Echo Base would have died without ever knowing what was coming.

That's the operational justification. Clean, rational, defensible.

The truth underneath it is less tidy.

The system administrator whose encryption I've been quietly studying for months has a distinctive signature.

Clean, efficient, elegant in the way that separates competence from artistry.

Every security protocol carries the same structural philosophy: build it right, build it thorough, build it once.

The approach is conservative in its foundations and creative in its implementations, and the combination produces code that functions like a language spoken by one person, recognizable in any context, impossible to replicate without understanding the mind that produced it.

I've been reading that language for months.

Through intercepted signal patterns, through the encrypted traffic that enters and exits the facility's communications hub, through the digital footprints that even the most careful system administrator leaves when they update protocols and rotate ciphers and maintain the infrastructure that keeps their people hidden and alive.

I know things about this person that they haven't told me and never would.

Their confidence lives in the clean recursive functions and the layered failsafes.

Their uncertainty hides in the patches and workarounds that cover gaps the elegant solutions can't close.

They work late, because the cipher rotations cluster in the hours between midnight and dawn.

They care about the people they're protecting, because the redundancies go beyond standard practice into something that borders on devotion.

Every backup is a backup of a backup, every failsafe nested inside another failsafe, the defensive depth of someone who has imagined losing the people on the other side of the wall built against that loss with everything they have.

Name, unknown. Face, unknown. But their mind is the most familiar thing I've encountered in years, and the knowing has become a habit I can't justify in operational terms because operational terms don't cover the satisfaction of reading someone's code in the dead hours of the night and feeling, for the first time in years, less alone.

That's why I sent the warning. The operational justification is real, but it's a shell around the softer truth: I couldn't make myself be the person who watched elegant code get destroyed by people who corrupt everything they touch.

I tried.

I sat at this desk with the targeting data on my screen.

I calculated the risks. I reviewed my protocols.

I measured the cost against the benefit and ran every analysis I know how to run.

At the end of all of it, my fingers were on the keys and the word was already typed and the send command executed before the analysis caught up.

At GCHQ, the postmortem for the operation that killed my partner ran dozens of pages and concluded with a recommendation to update internal review procedures for vulnerability assessments. Updated procedures.

My partner was dead and the system's response was a process revision that changed nothing because the problem was never the process.

The problem was that the people running the process decided the cost of acting on my warnings exceeded the cost of ignoring them.

They were right. The only cost of ignoring them was one analyst's career and one operative's life, and both of those were cheaper than admitting the system had failed.

I built my life after GCHQ around a single principle: operate alone, stay uninvolved, and never trust a system with the power to decide what happens to me.

The principle held for years. It held through the months of mapping the Committee's digital infrastructure, through the long nights of cracking their encryption and tracing their proxy chains and dismantling their operations one layer at a time.

It held because the work was mine and the risk was mine and the only person who could get hurt by my decisions was me.

Then I found a weapon aimed at a hidden base full of people I've never met, and the principle failed a stress test it wasn't designed to survive.

I just handed power over my safety to a stranger. The system administrator will find the word. His people will trace the channel. They'll find me, because I built the door from their own infrastructure and the routing carries my methodology like a fingerprint.

They'll come looking, and when they find me, I'll be sitting in this loft with flat Mountain Dew and dead takeout and the quiet certainty that my life just changed and the only variable I can't calculate is whether the change will be worth what it costs.

My fingers begin to move again. Slowly at first, then faster, tapping a sequence against my thigh that isn't code but rhythm, the body's way of telling the mind that processing has resumed and the system is coming back online after an unplanned shutdown.

I pick up the Mountain Dew. Take a sip. It's warm and flat and tastes like carbonation that gave up hours ago, and I drink it anyway because it's what's here and what's here is all I've got.

Somewhere inside Echo Base, a system administrator is about to find a word on a channel that shouldn't exist, sent by someone who found a door he didn't know was there. And the person who sent it is sitting in the dark, waiting to see what happens next.

My fingers tap against the can, working through the problem the way they always do, translating uncertainty into motion, converting fear into the only language I trust.