Chapter 11 Zara
The Rust Bucket develops a problem twelve hours from Haven.
"Port-side thruster coupling is failing," Fen reports from the engine room, her voice carrying the particular calm of someone describing a crisis without emotional investment.
"Stress fracture in the mounting bracket.
The gravity shadow transit weakened it. It has been degrading for the last six hours. "
"How bad?" Voss asks from the cockpit.
"We lose the port thruster, we lose maneuvering capability. The ship can still fly straight. It cannot turn effectively."
"Can you fix it?"
"With the right parts. Which we do not have."
"Can you reinforce it?"
"With the wrong parts? Possibly. I need four hours and access to the structural fabricator."
"We don't have a structural fabricator."
"I know. I was listing what I need, not what we have. What we have is adhesive bonding compound, two spare mounting bolts, and Kael."
"Kael?" I say.
"The mounting bracket requires physical force to realign while I reinforce it. The force required exceeds human capability. Kael's upper arms have the necessary strength."
I look at the ship schematic on my datapad.
The port thruster is mounted on the exterior hull, accessible through an external maintenance hatch.
Fen would need to work in the gap between the inner and outer hull, which is barely wide enough for a Keth, while Kael applies pressure to the bracket from inside the cargo bay, pushing through an access panel.
"Will it hold?" I ask. "The reinforcement."
"Long enough. To reach Haven. After that, it needs a proper repair facility."
"Do it. Voss, can we reduce speed to lower the stress on the coupling?"
"We can. Adds four hours to the transit."
"Four hours is better than losing a thruster."
We slow down. Fen and Kael begin the repair. I coordinate from the cargo bay, monitoring structural stress readings on my datapad while relaying Fen's instructions between the engine room and Kael's position at the access panel.
Watching Kael work is educational.
He peels back the access panel cover with his upper arms, the force pair, bending the metal edge as easily as I'd fold paper.
Then he reaches into the gap between hull layers with his lower arms, the precision pair, and feels for the mounting bracket.
His eyes close. He's working by touch, his long fingers tracing the fracture line in the bracket with a sensitivity that seems impossible for someone his size.
"I feel the fracture," he says. "It extends fourteen centimeters along the primary stress line."
"Can you press the bracket back into alignment?" Fen's voice through the intercom.
"Yes. What is the target position?"
"Three centimeters port-ward and two centimeters aft. Hold that position while I bond the reinforcement."
His upper arms brace against the cargo bay wall. His lower arms push, carefully, precisely. The metal groans. I watch the structural readings on my datapad shift as the bracket moves back toward alignment.
"One centimeter port. One and a half aft," I report, reading the sensors. "More port. Half centimeter. Hold."
He holds. Perfectly still, all four arms engaged, two bracing and two positioning, the muscles in his shoulders and arms defined with strain. The blue markings in his skin pulse brighter with the effort, illuminating the cargo bay in rhythmic waves.
I'm staring. I know I'm staring. I make myself look at the datapad.
"Fen, he's in position. Bonding window is now."
Twenty minutes of Fen working in the hull gap, applying the compound and bolting the reinforcement brackets, while Kael holds the alignment without moving.
Twenty minutes of absolute stillness under load.
His breathing doesn't change. His arms don't waver.
He holds the position with the disciplined focus of someone trained to endure.
When Fen signals completion, Kael withdraws his arms and flexes them, all four, in a sequence that ripples from upper to lower. The markings dim back to their resting pulse.
"Bracket aligned and reinforced," Fen reports. "It will hold at reduced speed."
"Nice work, everyone," Voss says.
I look at Kael. His skin is sheened with something that might be Vorath perspiration, a faint luminescent residue that makes him look like he's been dusted with starlight.
"You held that for twenty minutes without moving," I say.
"Vorath musculature is designed for sustained force application. Twenty minutes is not exceptional."
"It's exceptional for any species I've ever worked with."
"You have worked primarily with humans."
"And machines. You're somewhere between the two, in terms of reliability."
"You are comparing me to a machine."
"I'm comparing you to a very good machine. Take the compliment."
He tilts his head, considering. "Among the Vorath, to be compared to a well-functioning system is a meaningful praise. We value reliability. I accept the compliment."
"You were supposed to pretend to be offended so I could be funny."
"I do not pretend."
"I know. That's your whole thing."
The banter is becoming easier. I notice this the way I notice supply chain patterns, with the analytical remove of someone who catalogues changes in systems. Six weeks ago, conversation with Kael was like talking to a dictionary that had been given a body and sent into the world without context.
Now it has rhythm. Call and response. His literalness bouncing off my sarcasm and creating something that neither of us would generate independently.
I'm building a communication protocol with an alien. My logistics brain categorizes this as a fascinating interoperability challenge. The rest of me, the part I'm less practiced at listening to, categorizes it as something warmer that I'm not ready to file under any heading.
The repair buys us time but adds a new variable to my planning. The thruster is functional but fragile. Any hard maneuver, sudden acceleration, or impact could fail it. Which means our approach to Haven needs to be smooth, predictable, and entirely free of surprises.
Given how the rest of this trip has gone, I'm not optimistic.
Murphy's Law is the unofficial governing principle of this journey: anything that can go wrong has gone wrong, and several things that shouldn't have been able to go wrong found creative ways to do so anyway.
I have started including a "Murphy's margin" in all my calculations, a percentage buffer for the universe's apparent commitment to complicating my plans.
I spend the next four hours at the navigation console, refining the approach to Haven Station.
Voss has given me the coordinates, which are stored in her personal charts, not on any public nav database.
Haven doesn't exist on official maps. It's a ghost station, visible only to the people who know where to look.
The coordinates place it in a region of the Haven sector that's dense with asteroid fields and dead moons. Perfect for hiding a station. Terrible for approaching with a damaged thruster.
"The approach corridor is narrow," I tell Voss. "Asteroids on both sides, gravitational interference from the dead moons. We need precise maneuvering."
"Which we have limited capability for."
"Which is why I'm plotting the approach in segments with pre-calculated correction points. Each segment is a straight line between two asteroids. The corrections happen at nodes where the gravitational forces balance and we can adjust heading with minimal thruster use."
"You're turning my approach run into a logistics route."
"I'm turning your approach run into a survivable approach run. You're welcome."
She looks at the route. Studies it. Nods slowly.
"This is good. The correction nodes are well placed. You've accounted for the moon gravity?"
"All three moons. Plus the residual gravity from the main planet, which is tidally locked with the largest moon and creates a standing wave in the gravitational field that affects navigation at these speeds."
"You know what, Zara? When this is over, you should teach a class."
"In what?"
"In being terrifyingly competent under pressure."
I take that as the highest compliment I've received in my life and immediately deflect it. "It's just math. The math doesn't care about pressure."
"But you do the math under pressure. That's the part that matters."
The hours pass. I check each correction node as we reach it.
The adjustments are minimal, a degree here, half a degree there, the ship threading through the gravitic interference like a needle through cloth.
Each successful correction confirms the math.
Each confirmation settles something in my chest that I didn't know was unsettled.
This is what I'm good at. Not running, not fighting, not making dramatic decisions in cargo holds.
Planning. Routing. Finding the path through the obstacles and ensuring that the people I'm responsible for survive the transit.
It's not heroic. It's mathematical. And I've never needed it to be heroic. I've only needed it to work.
We creep toward Haven at reduced speed, the damaged thruster holding, the ship groaning occasionally in ways that Fen assures us are "within tolerance, barely.
" I eat ration packs at my console and drink recycled water that tastes slightly better than it did before Fen fixed the atmospheric processor.
Kael brings me food twice without being asked.
The first time is a ration pack, heated, with the water portion already measured into a cup.
The second time is something different: a combination of items from the ship's supplies that he has arranged on the tray with an attention to presentation that stops me mid-calculation.
The protein bar is centered. The fruit portion is to the left, where my dominant hand naturally reaches.
The water is placed where I won't knock it over when I turn back to the console.
He has been watching how I eat. Not what I eat. How. The spatial relationship between my body and my food, the hand I reach with, the side of my workspace that I leave clear for non-work items. He has built a model of my eating behavior and optimized the tray layout accordingly.
This is the most romantic thing anyone has ever done for me and I refuse to acknowledge it as such because acknowledging it would mean admitting that tray optimization is my love language, and that's a level of self-awareness I am not prepared for at 2 AM in the cockpit of a damaged freighter.
Both times, I say thank you. Both times, he nods and withdraws. The rhythm of it is becoming familiar, comfortable even. He provides. I plan. The functions complement without overlapping.
I catch myself thinking of us as a system and immediately reject the thought because thinking of a relationship as a system is probably the most me thing I've ever done and I'm embarrassed by it.
But it is a system. A good one. He handles the physical variables, I handle the informational ones. Together, our coverage is comprehensive.
I'm a logistics coordinator. I can't help seeing efficiency in partnership. It doesn't mean anything beyond operational recognition.
It doesn't.
I check the sensor display. Eight hours to Haven. The asteroid field is visible on the long-range scanner, a dense cluster of rocks and debris surrounding the coordinates Voss provided. Somewhere in that cluster, hidden and protected, is a station where people like us go to stop running.
I think about what that means. Stopping.
The word itself feels wrong in my mouth, like a command my operating system doesn't recognize.
My entire adult life has been structured around movement, optimization, the identification and resolution of the next problem.
Even at Helix, in the boring years before the cargo hold, my days were defined by throughput targets and routing efficiency and the constant, quiet satisfaction of making a system run better than it ran yesterday.
What does my brain do when there's nothing to plan against? When the route is complete and the cargo is delivered and the system is at rest?
I don't know. I've never been at rest. Even before the escape, I was always planning, always optimizing, always finding the next inefficiency to solve. It's not just what I do. It's how I exist.
"You're thinking too hard," Voss says without looking at me. She can read a room the way I read a database. "You've got that look."
"What look?"
"The one where you're trying to logistics your feelings and it's not working."
"I'm thinking about Haven."
"You're thinking about what happens at Haven. Different thing."
"What does happen at Haven?"
"You rest. You breathe. You figure out what you want to do with the rest of your life now that the running part is potentially over. It's the hardest part, actually. The running keeps you busy. The stopping makes you think."
"I think all the time."
"You plan all the time. That's not the same as thinking. Thinking means sitting with uncertainty and not trying to organize it into a spreadsheet. It means letting things be messy."
"I don't do messy."
"I know. That's why Haven is going to be interesting for you."
She says this with the cryptic confidence of someone who has delivered many refugees to Haven and watched them all go through the same process. The decompression. The reckoning. The slow, painful realization that survival is just the first problem and everything after it is harder.
I look at the asteroid field on the scanner. Eight hours.
I pull up my datapad and start a new document. Not a plan. Not a list. Just a blank space.
I stare at it for thirty seconds, then close it and go back to the navigation route.
Baby steps.