Chapter 9 Zara
We come out of the Drift Margin into the Thessan border system and immediately I know something is wrong.
Not with the ship. Fen has the Rust Bucket running better than it has in years, Voss's words. The engines purr. The coolant system flows smoothly. Even the atmospheric processor sounds different, cleaner, like the ship is breathing properly for the first time.
What's wrong is the traffic. My logistics brain, which runs continuous background diagnostics on every system I observe the way some people's eyes automatically read any text they see, has been parsing the scanner data since we cleared the Margin's exit point. And the parser is throwing errors.
The Thessan border system is supposed to be quiet. Voss's charts show it as a transition zone, a handful of mining operations and a relay station, low population, minimal enforcement. The kind of system people pass through, not stop in.
There are forty-seven ships on the scanner.
"That's not normal," Voss says, pulling up the long-range display. "Thessan border usually has single-digit traffic. This is a fleet."
"Helix?" My stomach drops.
"Mixed signatures. Some Helix, some independent, some I don't recognize. And..." she pauses, reading the scanner data, "there's a checkpoint. At the gate crossing into Thessan proper. Someone has set up an inspection point."
"That wasn't there before?"
"It was not there three weeks ago when I last transited this system." Voss leans back and stares at the display. "Helix is locking down the corridor. They've moved enforcement assets into the transition zones. This isn't just about finding you, Zara. This is a systematic tightening."
"The debris field," I say. "In the Drift Margin. Someone is hitting their transport ships. Helix is responding by increasing security on all their routes."
"Which means the covert routes and the official routes are both under heavier patrol."
I pull up my navigation charts and start recalculating.
The original plan had us transiting through Thessan to the Haven sector gate on the far side.
That gate is beyond the checkpoint. To reach it, we'd have to pass through the inspection point, which means manifest checks, ID verification, and a very thorough scan that would find one human fugitive, one bonded Vorath, one freed Keth prisoner, and a ship full of evidence linking us to the biggest corporate embarrassment in Helix's recent history.
"Can we go around?" I ask.
"Around the checkpoint? In-system, maybe. It depends on how wide they've set the sensor net." Voss studies the traffic patterns. "The checkpoint is at the gate, but they'll have patrol ships running sweeps out to a perimeter. Standard enforcement cordon."
"How far?"
"Two hundred thousand klicks, usually. Maybe more if they're serious."
"They're serious."
"Then maybe more." Voss pulls up a secondary display showing patrol patterns. "The checkpoint ships are running a standard enforcement grid. Predictable, but dense. They're covering the approaches with overlapping sensor fields."
I study the patterns. My brain switches to the mode that Kael once described as "watching a system boot up," the rapid, involuntary processing of spatial data into route options.
I can't help it. Give me a map with obstacles and my mind starts finding the paths through them.
It's not bravery. It's pattern recognition with consequences.
"There," I say, pointing at a gap in the sensor coverage. "Between the second and third patrol orbits. There's a window. Sixty-seven minutes every cycle where the overlap thins."
"Sixty-seven minutes isn't much."
"It's enough. If we time it right."
"Then maybe more."
I close my eyes and think. The logistics part of my brain, the part that was trained to find routes where none obviously existed, goes to work.
Thessan is a binary system. Two suns, complex gravitational fields.
The gravity wells create zones where sensor performance degrades because the electromagnetic interference from the binary interaction floods the detection spectrum.
"Gravity shadow," I say. "Between the two suns. The binary interaction creates an EM dead zone. If we fly through it, their sensors can't distinguish us from the background noise."
"That's insane," Voss says. "The gravity shadow is a nightmare to navigate. The tidal forces alone..."
"Are predictable. The binary orbit is well-documented. I can calculate the tidal patterns and plot a course that rides the interference zone from our current position to within fifty thousand klicks of the Haven gate."
"Fifty thousand klicks is still inside their perimeter."
"But it's the closest we can get while invisible. The last fifty thousand, we sprint. Full engine burn. By the time they detect us and respond, we're through the gate."
Voss looks at me with an expression that combines professional admiration and personal concern.
"You want to fly through the gravity shadow of a binary star system, navigating tidal forces that could rip this ship apart, so we can sprint through a Helix enforcement perimeter before they can catch us."
"Yes."
"That's a logistics plan?"
"It's a routing optimization with elevated risk parameters."
"It's insane."
"Do you have a better option?"
She doesn't. We both know it. Going back through the Drift Margin adds weeks. Approaching the checkpoint means capture. Waiting means Helix tightens the net further.
"I need six hours to calculate the route," I say. "The tidal forces shift on a cycle. I need to map the current phase and project the safe corridor."
"You have four hours. After that, the patrol pattern brings a sweep ship too close to our current position."
Four hours. I've done more with less.
I commandeer the navigation console, Voss's personal chair, which she vacates with a grumble and a muttered comment about logistics coordinators taking over the universe.
I pull up every database I have on the Thessan binary system: orbital mechanics, gravitational models, EM interference patterns, historical sensor performance data. Then I start building the route.
It's the most complex navigation problem I've ever tackled.
The tidal forces in the gravity shadow are not constant.
They pulse with the binary orbital frequency, creating windows of relative calm between peaks of intense gravitational shear.
The ship needs to be in the calm windows and out of the shear zones, which means the route isn't a straight line, it's a series of timed segments, each one calibrated to the binary rhythm.
I think of it like a shipment schedule. Each segment is a delivery window. The cargo is us. The delivery address is the Haven gate. The constraint is that we get torn apart if we miss a window.
Simple, really. In the most terrifying possible way.
Kael appears in the cockpit doorway during hour two.
He's been in the cargo bay, doing his stillness thing, but I can tell through the bond, and yes, I'm starting to feel things through the bond now, just faint impressions, emotional weather forecasts rather than specific feelings, that he's been aware of my concentration spiking.
"You are working on something difficult," he says.
"I'm plotting a course through a binary gravity shadow while calculating tidal windows with a margin of error of plus or minus forty seconds per segment."
"Forty seconds is not much margin."
"No, it is not."
He looks at the navigation display, which is covered in my route calculations, a web of colored lines and timing markers that probably looks like abstract art to anyone who doesn't think in logistics.
"I do not understand the specifics," he says. "But the pattern of your work is similar to the pattern I felt when you freed us. Organized. Precise. The same mind applied to a different problem."
"Thanks for the pep talk."
"I do not know what a pep talk is. I am observing that you are capable."
"That was the pep talk."
He pauses. "Is this another instance of humans saying the opposite of what they mean?"
"No, actually. That one was genuine."
"Ah. The distinction is difficult."
"It is for us too, honestly."
He stays in the doorway. Not intruding, not leaving.
Present. I'm starting to realize that this is his version of support.
He doesn't offer solutions because the problem isn't in his domain.
He doesn't offer encouragement because Vorath don't process motivation through verbal reinforcement.
He offers presence. The simple, immovable fact of him being there.
It helps. I won't tell him that, but it helps.
Hour three. The route is taking shape. Seventeen segments, each one timed to a tidal window, each window between forty and ninety seconds of relative calm. The total transit time through the gravity shadow is eleven hours. Eleven hours of precision flying through a region that wants to crush us.
"Voss," I call. "I need you to look at this."
She comes to the console and studies the route. Her eyes move along the segments, the timing markers, the tidal peak indicators. She's a pilot. She reads routes differently than I do. Where I see logistics, she sees flight dynamics.
"You're asking me to fly seventeen segments with forty-second windows through gravitational shear that exceeds the Bucket's structural tolerance."
"The shear is only at peak. Between peaks, the forces are within tolerance."
"Barely within tolerance."
"Within is within."
"That's a very logistics way of looking at not dying."
"It's the only way I know how to look at it."
She stares at the route for a long time. Then she nods.
"I can fly this. It's going to be ugly, but I can fly it."
"And the sprint? The last fifty thousand klicks?"
"Full burn, straight at the gate. The Bucket can sustain max power for eighteen minutes before the engines overheat. At full burn, fifty thousand klicks takes... fourteen minutes. Four-minute margin."
"That's tight."