Chapter 35
Chapter Thirty-Five
REEVE
It’s Thursday morning, and the monitoring screens are clean.
There was no movement on Viktor’s network overnight. No new shell company activity, no encrypted channel traffic, no financial transfers through any of the entities I’ve been tracking since week one.
His team is positioned and waiting, the same way we’re positioned and waiting, and the silence between us is the silence of two operations that have both finished planning and are now waiting for the same trigger.
Six AM tomorrow. The moment Doc makes the call and the admission goes into the system, both sides move.
We know his plan, and he doesn’t know we know it. That’s the only edge we have, and I’ve been turning it over since Sunday, looking for the places where it could fail, the assumptions built into it that could be wrong.
Dmitri could have given us bad intel, deliberately or because he didn’t have the full picture. Viktor could have changed the approach plan after Dmitri accessed it. The contractor could operate differently than the documentation suggests.
I’ve run all three scenarios.
Dmitri’s intel checks out through two independent verification methods.
Viktor’s network has been dormant for seventy-two hours, a pattern consistent with a team that has its orders and is waiting to execute, not a team that’s been stood down and retasked.
The contractor’s documented methodology matches the approach plan Dmitri provided in every detail I can cross-reference.
The intel is good.
Ghost comes in at eight. He sits across the desk, and I run him through the floor layout one more time, not because he doesn’t have it memorized but because running it again catches things that memorization misses.
The east wing private floor, two access points, four men covering them. Orderly positions confirmed with the hospital administrator yesterday afternoon. Visitor cover for the second pair cleared through Doc’s arrangement with the floor supervisor.
“Elevator shaft access,” Ghost says.
“Covered,” I say. “Maintenance contractor identity confirmed. He’s in position from five thirty AM.”
Ghost nods. “Viktor’s team approach?”
“Patient Transfer Solutions vehicle, Oregon plates, arrives within ninety minutes of the admission trigger. They move through the main entrance, take the elevator to the private floor, and approach from the east corridor.” I pause. “They won’t reach the second checkpoint.”
“If they split the team,” Ghost says.
“Two on the floor, two holding the vehicle,” I say. “If they split differently, you have the contingency.”
He nods once. He’s been running the contingency. He doesn’t need me to describe it.
He leaves.
Jax comes in at nine. He drops into the chair and looks at the screens for a moment before looking at me.
“Social engineering,” I say. “Walk me through it.”
“Hospital front desk has a note on the admission flagging it as a privacy-sensitive case,” he says.
“Media protocol, which means any inquiry about the patient gets routed to the floor supervisor, who is Doc’s contact, who routes it to me.
Any external personnel claiming medical authorization gets the same treatment.
” He pauses. “If Viktor’s team tries to move through official channels instead of force, it goes through me first.”
“Response time.”
“Thirty seconds from flag to my phone,” he says. “I’m in the hospital from five forty-five.”
“Position.”
“Main lobby, service desk. I look like a hospital administrator. I’ve done harder covers.”
I look at the brief. “One scenario,” I say. “Viktor’s team presents credentials that clear the front desk before the flag triggers.”
Jax looks at the ceiling for a moment. “Credentials that clear the front desk have to go through the system. The system has the flag. The flag triggers regardless of credential quality.” He looks back at me. “It’s covered.”
“Good,” I say.
He goes.
Doc comes in at ten with his medical bag and the monitoring data from last night’s simulation run.
He puts the data sheet on the desk. I look at the numbers.
Mira’s vitals through the half-strength simulation, blood pressure, heart rate, and fetal monitoring.
All within acceptable range. The baby’s readings are clean throughout.
“Full strength tonight,” Doc says. “Ten PM. I’ll monitor through to four AM, confirm presentation, and clear her for admission.”
“Risk to the baby at full strength.”
“None if we monitor correctly,” he says. “And we will monitor correctly.”
He says it the way he says everything medical, flatly and without hedging, the voice of a man who has been doing this for thirty years and knows the difference between a real risk and a theoretical one.
“Blood pressure,” I say. “Hers has been elevated for weeks.”
“Monitored,” he says. “If it spikes during the simulation, I stop it. We have contingencies.”
“If it spikes during the operation.”
“Then I pull her,” he says. “Viktor is secondary. I don’t care what stage the operation is at.”
“Cade will tell you the same thing,” I say.
“I know he will,” Doc says. “That’s why we’re having this conversation now instead of tomorrow morning.”
He picks up his bag and goes.
The nurse rotation variable. I’ve been working on it since I flagged it days ago. The east wing duty nurse rotation on Fridays runs twenty minutes off the standard schedule, narrowing the intercept window from the planned two hours to approximately one hour and forty minutes.
Seventeen minutes of buffer gone.
Not fatal. But tight enough that a deviation from Viktor’s approach timeline, if his team moves faster than the documented methodology suggests, creates a window where Ghost’s second checkpoint is unconfirmed before the team reaches the floor.
I spent last night building around it.
The solution is a position adjustment on Ghost’s third man.
Instead of covering the stairwell access from the landing, he covers it from inside the floor corridor, which extends his sightline by forty feet and closes the gap the rotation creates.
It adds exposure risk for the third man but removes the timing vulnerability entirely.
I run the numbers one more time. The adjusted position works.
I update the brief and send Ghost the revised placement.
His reply comes back in four minutes. One word.
Confirmed.
Cade comes in at noon. He doesn’t sit. He stands at the window, hands loose, eyes forward, giving me the profile of a man who is running something in his head and doesn’t need to perform it for the room.
I run him through the full brief. Every element, every position, every contingency, every variable I’ve identified, and the response I’ve built for each of them. He listens without interrupting, the way he always listens, and when I finish, he looks at the screens for a moment.
“Viktor’s personal involvement,” he says. “Unknown.”
“Yes,” I say. “He may direct from Seattle. He may be in Montana already. The contractor operates independently regardless, but if Viktor is physically present, it changes the elimination timeline after the intercept.”
Cade looks at the screens. “If he’s here,” he says.
“Then Ghost and I handle it the same day,” I say. “Before he can rebuild.”
Cade nods. “Collateral.”
“The hospital floor is isolated. Doc’s contact has cleared it. The civilian presence on the floor is minimal and controlled. Ghost’s team is trained for low-exposure environments.” I pause. “Risk exists. It’s as low as I can make it.”
He nods again.
I look at the brief on the screen. “She’ll be safe,” I say. “We’ll end this.”
Cade looks at me. “She better be,” he says.
He says it without heat, without threat. Just a statement of what is required and what is not negotiable, delivered in the register of a man who has put everything he has behind a single operational outcome and is holding me to the same standard he holds himself.
I hold his eyes. “She will be,” I say.
He goes.
I close the brief.
If I haven’t found the gap by now, the gap isn’t there. And if it is there and I haven’t found it, another hour won’t change that either. The plan is built. The team is ready. Tomorrow will be what tomorrow is.
I close the laptop and sit in the security office in the quiet of a compound that is as ready as it’s going to be, and I think about every variable I’ve identified over eight weeks of running this operation and the variables I haven’t identified because you can’t identify what you don’t know is there.
That’s the part you can’t plan for.
The unknown variable. The thing Viktor has built into this that Dmitri didn’t know about or didn’t tell us. The deviation from the documented methodology is introduced by contractors because contractors adapt, and professionals don’t follow plans exactly when the conditions change.
I don’t know what that variable is.
That’s the nature of it.
What I know is that Ghost’s team is the best security detail I’ve ever run. What I know is that Doc hasn’t lost a patient in thirty years of operating in situations that would have broken most physicians.
What I know is that Jax can social engineer his way through any institutional environment he’s ever walked into, and that Cade’s command decisions in the field are faster and more accurate than anyone I’ve worked with.
And I know Mira.
I know she ran the code phrases until they were automatic. I know she held the complicated register in the third scenario without breaking. I know she read the completion clause, understood exactly what it meant, and said to use it anyway.
She’s ready. The plan is ready. Tomorrow, it either works or it doesn’t, and everything we’ve built over the last month is why it will.
The one variable I haven’t fully resolved sits at the back of my mind, where I keep things to watch.
Viktor’s personal involvement.
Unknown.
Tomorrow we find out.