Chapter 37
Chapter Thirty-Seven
REEVE
Ghost confirms cleanup complete at two seventeen PM.
Four personnel from Patient Transfer Solutions were detained, processed, and removed from the hospital premises through the service exit without a single member of the public seeing anything that required explanation.
The hospital administrator has a privacy incident on record that will close without investigation. The floor is cleared. Doc has signed off on Mira’s discharge, stress-related false alarm, mother and baby healthy, no further intervention required.
Clean.
I open the message interface.
The encryption takes forty seconds to complete.
I’ve built the routing through three relay points, each one untraceable back to this compound or any entity connected to it.
When Viktor reads this message, it will appear to have originated from a server in Helsinki that is not connected to anything he can identify.
I type the message.
Your retrieval team has been detained and will not be returning.
Mira Volkov remains on Ruthless ground and under Ruthless claim.
This matter is now closed. Any further attempts to access her or the child she carries will be met with permanent resolution.
No further communication is required or will be accepted.
I read it twice. Every word is deliberate.
Retrieval team, not extraction team, because retrieval implies she was something to be recovered, which reframes his entire operation as a failure of asset management rather than a territorial violation.
Detained and will not be returning is precise enough to convey everything to him without stating it directly.
Permanent resolution is not a threat. It’s a description of what has already been decided.
I send it.
Then I open the monitoring feed, and I watch.
* * *
Viktor’s network shows nothing for the first twenty minutes, which is expected.
A man like Viktor doesn’t react to bad news immediately.
He processes. He runs the calculation. He maps the implications from every angle before deciding how to respond, which is why he has survived as long as he has in a world that eliminates men who react before they think.
At the thirty-minute mark, his primary encrypted channel activates briefly. Not a message outbound. An inbound check, which means someone on his team is confirming receipt of something. The channel closes in eleven seconds.
He knows.
I watch the feed for another hour.
Nothing.
No counter-message. No outbound communication on any of the channels I’ve been monitoring for the past month.
No financial activity through any of the shell company entities remains active after the counterstrike.
No legal team activity through the filing systems I’ve been tracking since he pivoted to the emergency protective services framework.
Complete silence.
I sit with that.
Silence from Viktor means one of two things. Either he has accepted the operational loss and is cutting his exposure, which means withdrawing his network’s involvement, closing the shell companies, and distancing himself from anything that connects him to any of this.
Or he is calculating his next move, which means the silence is not acceptance but preparation.
The problem is that both scenarios produce the same silence.
I can’t tell from the monitoring feed which one I’m looking at.
That uncertainty is why I pick up the phone.
* * *
Cade comes in at four.
He doesn’t sit. He stands at the window, his hands in his jacket pockets, looking down at the compound below: the men moving between buildings, the perimeter rotation along the fence line, and the gate where two men are on their posts.
I run him through it sequentially.
The message sent, the routing, the language, and why I chose each word. Viktor’s network response, the brief channel activation at thirty minutes, and the silence since. The two possible interpretations, and why I can’t determine from the available data which one is correct.
He listens without interrupting.
When I finish, he looks at the compound for a moment.
“He lost his team,” he says.
“Yes.”
“No deniability. No operational distance. The Bratva will ask questions about where the four men went, and he won’t have an answer that preserves his standing.”
“Correct,” I say. “A man in his position inside the Bratva structure can’t afford an unresolved operational failure of this magnitude. His standing depends on being the man who solves problems cleanly. He hasn’t solved this one cleanly.”
Cade looks at the gate. “Retreat or personal move,” he says.
“Yes. If he retreats, he cuts his losses, distances himself from the operation, accepts the reputational damage internally, and moves on. If he makes a personal move, he comes here himself or sends someone he trusts outside the contractor network, someone we haven’t identified, and tries to resolve it through a channel we haven’t anticipated. ”
“Timeline?” he says.
“If he’s retreating, we see network closure within twenty-four hours. If he’s preparing a personal move, we see nothing until he executes, which could be anywhere from forty-eight hours to two weeks, depending on how quickly he can resource an alternative approach.”
Cade turns from the window. “We can’t wait two weeks,” he says.
“No,” I say. “The birth permanently ends his custody options, removing his operational justification for further action. But two weeks is enough time for a man with his resources to find a method we haven’t planned for.”
“And if we move first?”
“We remove the variable,” I say. “Permanently.”
The office is quiet.
Cade looks at the desk. “End it,” he says. “Clean. No exposure, no blowback, no ripple into the club’s operations or into her life after.”
“Understood,” I say.
“Ghost?”
“Already planned to bring him in,” I say. “I need his logistics capability for the disposal side. The elimination itself I can handle.”
Cade looks at me. “You don’t have to,” he says.
“I know,” I say.
He holds my eyes for a moment and then nods once and goes to the door.
“Cade,” I say.
He stops.
“Thirty-six hours maximum,” I say. “If Viktor is preparing a personal move, he’s already started. We need to be ahead of it.”
“Thirty-six hours.”
He leaves.
* * *
Ghost comes in at five. He sits across the desk, and we build the plan.
Viktor’s pattern over the last eight weeks has been consistent in one respect. He moves through legitimate channels when they’re available and through his own network when they’re not.
With his contractor team gone, his shell company structure compromised, and his legal team’s filings on record with federal agencies, his legitimate channels are significantly narrowed.
What he has left is his own presence and his own resources.
And a reputation inside the Bratva that requires him to resolve this personally if he’s going to resolve it at all.
“He’ll come here,” Ghost says.
“Yes,” I say. “Not to the compound. He knows he can’t reach the compound. But he’ll come to Montana. He’ll try to find a leverage point outside our perimeter, somewhere we have to respond to, something that forces us to come to him rather than him coming to us.”
“Which means he shows himself,” Ghost says.
We look at the county map on the screen. The compound at the center, the rural roads running out from it in four directions, and the businesses and properties that connect Ruthless to the surrounding area.
“The auto shop,” Ghost says.
“Rebuilt,” I say. “And he already used it once. He won’t repeat a method that’s been identified.”
“Supply chain.”
“Disrupted and restored. He knows we closed that vector.”
Ghost looks at the map. “He’ll use a person,” he says. “Someone is already in our orbit. A supplier, a business contact, someone whose presence near the compound doesn’t raise flags.”
“Yes,” I say. “Which means we watch the edges. Anyone who has regular contact with this compound’s operations gets a monitoring flag starting tonight.”
Ghost nods.
We work through the rest of it. The logistics of removal, location requirements, disposal methodology, and communication to the Bratva afterward that preserves Viktor’s face publicly while making the internal message clear.
Operational failure on Ruthless ground. Matter resolved. No further correspondence required.
The Bratva won’t escalate over one strategist who miscalculated territorial sovereignty. The math doesn’t work in their favor. Viktor’s standing was already damaged by the contractor’s operational failure. His disappearance will be absorbed as a natural consequence of overreach.
That’s the plan.
By six thirty, it’s built.
I sit in the security office after Ghost leaves, and I look at the monitoring screens. Viktor’s network is still quiet. No movement, no signals, no indication of what he’s decided.
The silence is still running.
I don’t know yet whether it’s the silence of a man standing down or the silence of a man loading a weapon.
Thirty-six hours.
We find out which one it is before the window closes.
I open a new monitoring protocol for the compound’s peripheral contacts, and I start running names. One of them will lead me to him.
I’m going to find it before he moves.