27. Roma
ROMA
My ship knows my hand.
The moment my palm settles against the recessed diagnostic plate beneath the navigation console, the dormant interface wakes in layers, its response hidden beneath the harmless surface chatter of routine damage assessment.
The Reaper engineer standing over my shoulder sees coolant pressure, hull stress, and corrupted drive telemetry.
I see the narrow pulse buried three menus deep inside the adaptive navigation loop, the private handshake I designed years ago because I trust people less than I trust systems that can lie on my behalf.
The cockpit is dim under Reaper power restrictions, lit by a skeletal amber glow from Throgg’s override clamps and the softer blue of my own emergency systems running below authorized thresholds.
Burn marks scar the console where their weapons overloaded my shield relay.
One overhead panel hangs loose, exposing braided wiring that sways faintly whenever the docking spine transfers vibration through the hull.
The air smells stale and heated, full of melted insulation, cleaning solvents, and the faint mineral tang of Reaper atmospheric exchange bleeding through the open hatch behind me.
I breathe slowly.
I do not look at the airlock.
I do not look at the place where Dux was taken from me.
The Reaper engineer clicks through his external monitor. “Your system continues unauthorized background activity.”
“My system continues being alive,” I say, sliding two fingers across the console. “The distinction is important.”
“You were instructed to retrieve navigation architecture, not activate independent processes.”
“I was instructed to retrieve what Throgg needs. If you would like to tell him you interrupted the only person aboard capable of extracting it correctly, I will stand here quietly and enjoy that conversation.”
The engineer’s mandibles flex beneath the lower edge of his helmet.
I input a visible diagnostic command with my left hand and a hidden recursion string with my right.
The visible system opens a degraded map of the local core region.
The hidden system asks a question.
Is anyone listening?
Static answers first, a thin wash of radiation and gravitational noise. Beneath it, my father’s signal flickers like a candle glimpsed through a storm.
Then, for less than half a second, another pattern appears.
Crude. Improvised. Familiar in its irritation.
Larson-pattern recursion.
My breath stops in my throat.
Pally.
My father is close enough to receive.
Or someone has his equipment.
Or Dux?—
I clamp down on the thought before it becomes visible on my face.
The Reaper engineer leans closer. “Your pulse increased.”
“Your proximity is unpleasant.”
“You are agitated.”
“You are observant in the least useful way possible.”
“Explain the new data packet.”
“It is a triangulation artifact produced by damaged adaptive mapping routines.”
“You will isolate it.”
“I am already isolating it.”
I bury the incoming pattern beneath a false cascade of corrupted route fragments, then feed the engineer a cleaned version of the map that points toward a region near the Thorn Shelf.
It is not my father’s exact position. It is not safe.
It is not random. It is a carefully chosen intersection between three dangerous things: Pally’s likely salvage corridor, Throgg’s pursuit route, and a Zenos movement band I identified from the predator maps in his engineering archive.
A three-body problem with teeth.
I send the map to Throgg’s command channel before the engineer can object.
He makes a sharp sound. “You transmitted without authorization.”
“I transmitted actionable intelligence.”
“You are not permitted to determine?—”
Throgg’s voice enters through the cockpit comm, calm enough to slice skin. “Bring her to command.”
The engineer goes very still.
I close the panel and rise. “See? He enjoyed it.”
The walk back through the docking spine feels longer than before, though the route has not changed.
Reaper guards bracket me with disciplined silence, their armor whispering softly with each step.
Beneath the floor, the massive vessel vibrates with redirected power, a low predatory thrum that tells me engines are warming above maintenance levels.
Throgg is already moving resources in response to the bait.
Good.
Not enough.
But good.
Command is colder than engineering, or perhaps it only feels that way because every surface has been built to imply judgment.
Displays curve around the central platform in overlapping tiers, each one filled with tactical projections, sensor cones, weapon statuses, and fragments of the core rendered in violent color.
Throgg stands at the center beneath a suspended map, his hands clasped behind his back while my false data rotates in front of him.
He does not turn when I enter.
“You found him,” he says.
“I found evidence of a signal-handling structure consistent with his methods.”
“Careful wording.”
“Accurate wording.”
He lifts one hand, and the map expands. The Thorn Shelf blooms in three dimensions: debris fields, shear currents, heat signatures, and predator movement estimates. My inserted path glows along the outer edge, just close enough to promise pursuit and just dangerous enough to punish impatience.
Throgg turns then, his eyes fixed on mine. “This route leads toward Zenos territory.”
“Yes.”
“You think your father hides near predators.”
“I think my father uses danger the way other people use walls.”
That earns the faintest curve of his mouth. “And you inherited this habit?”
“I prefer doors.”
“You prefer systems you can control.”
“Doors are systems.”
He studies me for the space of several breaths, and I keep my face arranged around irritation rather than fear. Fear would be honest. Irritation is useful.
“Why transmit this immediately?” he asks.
“Because the signal was unstable.”
“You could have hidden it.”
“Yes.”
“You did not.”
“No.”
“Convince me this is not bait.”
I let out a short laugh, controlled enough to sound contemptuous. “Everything in the core is bait. Your ship is bait. My ship is bait. My father’s signal is bait whether he intends it or not. The useful question is whether the bait has a hook in the right place.”
His eyes brighten.
He likes that.
Predators appreciate predatory framing.
I step closer to the projection and point toward the false convergence region.
“This sector has repeating heat anomalies consistent with small-craft operation under intermittent power. The movement pattern avoids your usual patrol cones, which suggests he has mapped your habits. If he detected my ship, he may shift position again within the next cycle.”
“And if I move too quickly?”
“You spook him.”
“If I move too slowly?”
“You lose him.”
Throgg’s gaze remains on me. “And what do you recommend?”
I glance at the map, then at the weapons display, then at the projected Zenos band.
I make sure he sees me calculate. “You take the outer approach through the Thorn Shelf and force him toward this shear pocket. You do not fire on first contact. You show containment and let him believe escape remains possible through the western debris corridor.”
“Why?”
“Because he will take it.”
“And then?”
I move my finger along the route I prepared, drawing him straight toward the collision point. “Then you close the corridor behind him, and he has to choose between your vessel and the Zenos migration band. He will not choose the migration band if he has another option.”
Throgg looks at the path.
“So I become the better danger.”
“Yes.”
He turns toward one of his officers. “Overlay Zenos movement projections.”
The officer complies. The map adds a swarm of red markers flowing along the edge of the Thorn Shelf, their predicted route intersecting with the corridor I highlighted.
Throgg’s stillness deepens.
“This is narrow,” he says.
“Effective plans often are.”
“If your projection is wrong, we enter a hostile convergence with limited maneuverability.”
“If my projection is right, you get my father.”
“And you?”
“I get continued relevance.”
His attention returns to my face. “You want more than that.”
“Obviously.”
“Say it.”
“I want access to him before you put him in a cell and start calling coercion negotiation.”
Several officers shift around the platform.
Throgg’s expression does not change. “You presume much.”
“I know engineers,” I reply. “If you threaten him first, he will become less useful out of spite.”
“Would you?”
“I already have.”
He laughs softly, and the sound carries through command with unsettling ease. “Yes. You have.”
I hold his gaze, feeling the hidden trigger sequence sitting inside my sleeve comp like a live wire against my wrist. My ship accepted the first instruction.
The diagnostic signal is buried beneath damaged telemetry now, quiet and patient.
If Pally scans the right band, he will see my signature folded into the noise.
If Dux is with him, he will probably make some intolerable comment about my handwriting.
I refuse to imagine his voice too clearly.
It hurts.
Throgg steps closer until the projection light cuts sharp lines across his face. “You are manipulating me.”
“Yes.”
The answer lands cleanly.
His eyes narrow with interest rather than anger.
I continue before he can turn that admission into a weapon.
“I am manipulating you toward an outcome that benefits both of us. You want my father’s adaptive knowledge.
I want my father alive. You want escape architecture.
I want access to the only person besides me who can help refine it.
The manipulation is not the problem. The quality of it is. ”
An officer behind him makes a low sound of disbelief.
Throgg lifts a hand without looking away from me.
The room quiets.
“You have remarkable nerve,” he says.
“So I have been told.”
“By the Vakutan?”