Page 50 of Cipher: Lethal Algorithm

14

The Controlled Burn

JULIAN

The secure lineconnects on the second ring.

Hutch always answers on the second ring. Not the first—that would suggest he waits. Not the third—that would suggest he isn’t. Two rings is the answer of a man in control of every room he enters for twenty-two years and plans to continue retaining that control.

It’s a signature of authority that usually settles my nerves. This morning, it just feels like another layer of the cage.

I give him the name. “Thomas Calder.”

The silence that follows lasts exactly eleven seconds. I count them by habit, not nerves. Silence on a secure line is data, and Hutch’s silence has more texture than most people’s entire sentences.

This silence reads like a man who already staged the conversation, built the answer before I called, and decided which version of the truth to give me. Eleven seconds is a long time for a man like Hutch to decide. It tells me the shape of the answer before he opens his mouth.

“I’ve known that name was on the ledger for eighteen months.”

Something cold moves through the architecture of everything I thought I understood about this operation.

Eighteen months.

Hutch knew for eighteen months—which means Task Force 9 was always aimed here. He built the weapon knowing the target.

“The HSM.” My voice sounds tight in the small kitchen.

“Bring it home.” A pause. “The window is narrower than we thought. I’ll call back.”

The line goes clean.

I set the phone on the desk next to the cold coffee and lean back in the chair. The springs groan under my weight, a weary protest matching the ache in my lower back. Out through the shutter slats, the morning works itself into something—gray softening toward actual light, the sea doing its relentless thing, beating against the rocks below.

I’ve been a node in Hutch’s architecture this whole time. The eleven-week hunt, the Macau operation, the specific geometry of sending me after a ghost hacker who burns money and leaves a vine signature.

None of it was improvised. I was part of a weapon aimed at a target I didn’t have the full profile on.

I examine the irritation. It isn’t just that Hutch kept Calder’s name close. I understand operational compartmentalization.

I practice it myself.

There are good arguments for not putting a Deputy Attorney General’s name in the briefing documents of a rogue task force. It isn’t even that he used me without full disclosure; every operation has parameters the operators aren’t briefed on.

What bothers me is that Ivy was in that math too. Three years of her burning the Consortium’s money, running her solo exit. At some point, Hutch knew her name and calculated she was a more useful lure than a person to be protected. He let her stayin the wind, terrified and alone, because her flight path led to Calder.

Professionally, I’m moderately bothered.

Personally, the lid is coming off.

The physical memory of her from last night is a distraction I can’t afford. The heat of her skin. A woman finally dropping the armor.

The sex was supposed to be a release, a moment of friction to burn off the stress of the operation. The heat hasn’t dissipated. It settles in my chest and shatters the clean, clinical lines Hutch expects of me.

I pull up the partition data from the Luxembourg breach and look at the Architect’s suppression architecture glowing on the secondary monitor. Ivy’s code, taken further than Ivy took it. Someone studied her and upgraded the results. The implication becomes unavoidable.

Three possible outcomes for the Architect. I run them the way I run competing exploit paths—clean, distinct, held open until the environment resolves one.

First: the Architect runs a parallel operation against the Consortium from a position preventing direct action. They can’t reach Calder without exposing themselves. They need deniable hands. Ours are the most deniable available—because they belong to a rogue US Marshal and an off-books hacker who technically doesn’t exist.