Page 68 of Obsessed Bratva's Pregnant Claim
Enough for ‘what,’ I still did not have the answer to.
I stepped out of the elevator into the lobby and kept my face directed forward, my stride even, and my shoulders back. I did not look for the covered position on the east side of the building because looking for it would tell the watcher I had found it, and I needed the watcher—whoever the watcher was—to believe they still had the version of me that didn’t know.
I turned right.
The plan was mine. The execution was mine. I had built it out of what I had, which was incomplete information, a suitcase I’d repacked, and the stubbornness of someone who had been portable her whole life and had not lost the skill of it even after two weeks of believing, briefly, that she had found somewhere she could stop moving.
I was moving again.
I walked in the direction of the bus stop and did not look back at the building.
I’ll have to face whatever comes out of this.
Chapter Twenty-Two
Viktor
I fed Cruz the first piece of misinformation on Friday morning.
It went through a channel his network monitored—a communication line between two of our mid-level operations managers that we had identified as compromised eight weeks ago and had been using, carefully, as a one-way pipe ever since. Not frequently enough to pattern as planted, not infrequently enough to lose its credibility. The content this time: a timeline for a cash transfer moving through the Golovin operation’s eastern distribution on Saturday night. The timeline was false. The transfer was real, but two days earlier, already complete, the money was already where it was going. Cruz’s people would move resources to intercept a transaction that had already happened and find nothing, and that would cost them the resources they had moved.
Small. Precise. The kind of disruption that did not announce itself as disruption—that looked like an intelligence failure rather than an active countermeasure, which was important because the distinction told your adversary things about your exposure that I did not want Cruz to know yet.
The second piece went out through a different channel at noon. A false vulnerability in the casino’s south perimeter—a shift change overlap that didn’t exist, a window in the security rotation that had been closed six months ago, but that Cruz’s network, working from older intelligence, might believe was current. I had Sergei adjust the actual rotation to ensure that anyone probing the false window found coverage they hadn’tbeen told to expect. Not a trap. Just a door that didn’t open, encountered by people who had been told it would.
The third piece was more complex.
I had spent Thursday building it from the communication logs seized at the Meridian Linen facility. The logs contained, among other things, the structure of how Cruz’s network managed its asset communications—the specific protocols, the timing rhythms, the language conventions that their handlers used with the people they ran. I had learned those conventions, and I used them to construct a message that looked, to anyone familiar with the network’s internal language, like it had originated from a handler rather than been received by one.
The message was addressed to the contact point that Sofia’s secondary phone had been communicating with.
Sergei came in later in the afternoon.
He closed the door, which he did when the conversation required it.
“The misinformation architecture is running,” he said. “Cruz’s team has taken the first piece—we have confirmation they moved two people toward the eastern distribution point last night.” He paused. “The perimeter probe happened at 3. They found the coverage.” Another pause. “The handler message was received. No response yet, which suggests they’re verifying through a separate channel before acting on it. That’s expected—it’ll take them six to eight hours.”
“The window holds until tonight.”
“Tonight,” he confirmed. He looked at his folder, then at me. “Boss, the asset management logs from the Meridian servers. My people finished the full decryption this morning.”
“And?”
“The escalation timeline on Sofia’s asset file.” He opened the folder to a specific page and turned it toward me. “The deadline was not discretionary. It was structural—built into the asset management protocol at the point where a recruited asset’s cooperation drops below a threshold. The protocol triggers automatically when the asset stops providing actionable intelligence.”
I looked at the page.
“It triggered eight days ago,” Sergei said.
Eight days. After that, the Monarch Club logs showed no further actionable intelligence from Sofia’s contact channel. Surface content, metadata confirmed. Nothing Cruz’s people could use.
“She stopped,” I said.
“She stopped providing actionable content eight days ago,” he confirmed, his voice precise. “The escalation to in-person pressure—the Monarch Club meeting—was the protocol’s response to the drop-off. The deadline was the protocol’s next trigger.” He paused. “She didn’t cooperate at the Monarch Club meeting. The logs don’t have the content—that meeting was conducted without a digital record—but the follow-up handler traffic indicates non-compliance. The asset was non-cooperative.”
I digested that.
“So the deadline,” I said.
