Logan
The data didn’t spike.
That was the problem.
No surge in power. No scramble in comms. No panicked repositioning like before. The feeds stayed steady—too steady. Sentinel had stopped reacting.
Which meant he’d startedacting.
I stood over the table, hands braced, eyes unfocused as the room worked around me. Boone was talking—something about air corridors and secondary teams—but his voice faded into background noise.
Because the silence had changed.
Not gone.
Focused.
“He’s not moving her anymore,” I said.
Boone stopped mid-sentence. “How can you tell? We lost direct trace two hours ago.”
“Exactly,” I replied.
I straightened slowly, that familiar cold clarity settling into place—the one that only came when things turned lethal.
“Sentinel doesn’t go quiet unless he’s satisfied.”
Russ frowned. “Satisfied with what?”
“With leverage.”
I tapped the map, zooming out—not geographically, but conceptually. Patterns over time. Cause and effect. Predator behavior.
“He escalated,” I said. “But not physically.”
Boone’s jaw tightened. “Psychological.”
“Yes.”
I pictured Scout in that room. Upright. Observing and refusing to give him fear.
“He didn’t break her,” I continued. “So now he’s changing the environment. Showing her consequences. Making her responsible for outcomes she can’t control.”
Russ exhaled sharply. “That’s cruel; he’s working with her mind.”
“That’s Sentinel.”
I turned to Boone. “Any changes in internal routing? Power priority shifts?”
Boone scanned his tablet again, slower this time. “Actually… yes. There’s a new allocation. Deep-level systems are coming online. Not security. Not medical.”
“Then what?”
Boone swallowed. “Data processing. Simulation frameworks.”
My stomach dropped.
“He’s using her expertise,” I said quietly. “Forcing her to engage.”
