Chapter 16 Kael
The station prepares for war.
I use the word deliberately. What Helix intends is not a negotiation or a recovery operation.
The intelligence Fen intercepts over the next two days paints a clear picture: Director Asha Orin, head of Special Projects, has authorized a tactical team to locate and neutralize Haven Station.
"Neutralize" in Helix parlance means destroy, dismantle, and erase from the record.
They do not want to recapture the station. They want to ensure it never existed.
This is personal to Director Orin. I learn this from Zara, who has been analyzing the intercepted communications with the same precision she applied to shipping manifests. The pattern she identifies is not just operational; it is vendetta.
"Orin's communications reference the breakout specifically," Zara tells the council meeting.
Sira, Thresh, Voss, Zara, and I are gathered in the operations center.
Fen listens through the intercom from the antenna array, where she has been living for two days.
"She doesn't just want Haven. She wants me.
The breakout embarrassed her division. Seven specimens lost, a logistics coordinator who made her security look incompetent, and now evidence that the escape has inspired increased resistance activity.
The Drift Margin attacks on Helix transports started after the breakout. Orin sees a connection."
"Is there a connection?" Sira asks.
"Not from us. But Helix thinks in systems. A breakout here, transport attacks there, Haven operating here. They see a coordinated network. They're wrong, but it doesn't matter. Orin is treating this as an organized threat and responding accordingly."
"What are they sending?" Thresh asks.
Fen's voice through the intercom: "Based on the communication patterns and fleet movements I've tracked, an enforcement cruiser and four support vessels. Total personnel estimated at two hundred. Weapons complement includes ship-to-station ordnance sufficient to breach Haven's shields."
"Two hundred against a station of seventy-three," Thresh says flatly.
"Seventy-three including children and non-combatants," Voss adds. "Effective defenders, maybe thirty."
"Twenty-eight," I say. They look at me. "I have assessed the station's combat-capable population. Twenty-eight individuals with meaningful combat training or experience. The remainder are civilians, children, or personnel whose skills lie outside direct confrontation."
"Like me," Zara says.
"You are the most important person in this room," I tell her. "You do not need to fight. You need to plan."
The council discusses options. Evacuation is still on the table, but Zara's analysis shows that Helix's search pattern will cover the sector within seventy-two hours. Even if we evacuate, the fleeing ships will be detected and pursued. Running is not safe.
"Then we defend," Thresh says. "Buy time. If we can hold long enough to get the civilians out on Voss's ship and two other vessels in the docking bay, we can scatter the non-combatants while the defenders hold the station."
"That's a rearguard action," Voss says. "The defenders stay and fight while the civilians run."
"It's the only option that protects the most lives."
"I disagree," Zara says. Everyone turns to her. She has her datapad in hand and the look on her face that I have come to recognize as the one that precedes a plan that sounds insane and works perfectly.
"There's a third option," she says. "We don't evacuate and we don't just defend. We do both. Simultaneously. But we make Helix think we're only evacuating."
She pulls up a holographic display of the station and its surrounding asteroid field.
"Haven's position in the asteroid field is its greatest asset. The approach corridors are narrow. Helix can't bring all five ships to bear at once. They'll have to approach through the corridors one or two at a time."
"That buys us time, but doesn't change the math," Thresh says.
"It changes the math if we use the corridors. Fen, the mining charges in storage bay nine. How many?"
"Forty-seven industrial mining charges. Designed for asteroid fragmentation."
"Can they be repurposed as directional munitions?"
"Yes. With modifications. I would need thirty-six hours."
"You have thirty. Thresh, the sensor array. Can we extend the detection range into the corridors?"
"With Fen's modifications, yes. We can track approaching vessels through the asteroid field from at least two hundred thousand klicks."
"Good. Here's the plan." She taps the display and corridors light up in color.
"We place mining charges at choke points throughout the approach corridors.
Not to destroy the Helix ships, we don't have the firepower for that.
To collapse the corridors. Drop asteroids into the approach paths. Close the doors behind them."
I see it. The plan crystallizes in my mind the way Vorath battle strategies crystallize, not as a sequence but as a shape. A structure.
"You want to trap them," I say.
"I want to slow them. If we collapse the forward corridors after their lead ships enter, we split their force. The ships in the corridors are cut off from the ships behind them. We deal with a fraction of their force instead of the whole."
"The trapped ships will still attack the station."
"One or two ships, not five. And our turrets and shields can handle one or two ships long enough for the civilian evacuation to complete.
" She highlights escape routes on the display.
"Three ships leave the station from the rear docking bays.
They exit through corridors that I've mapped as too narrow for Helix's larger vessels.
By the time Helix clears the collapsed approach paths, the civilians are scattered. "
"And the defenders?" Voss asks.
"The defenders hold the station until the evacuation is complete, then withdraw on remaining vessels. The station can be reclaimed later. Or rebuilt. But the people survive."
The room is quiet. Sira studies the holographic display.
Thresh does the same. They are both seeing what I see: a plan that is not military but logistical.
It does not rely on superior firepower or warrior skill.
It relies on chokepoints, timing, and the precise placement of forty-seven mining charges by a woman who thinks in shipping routes and delivery windows.
"The charges must be placed precisely," Fen says through the intercom. "Incorrect placement will fail to collapse the corridors or will collapse them too soon."
"I've calculated the placement," Zara says. "Each charge has specific coordinates based on the asteroid density, composition, and gravitational dynamics of each corridor. The detonation sequence is timed to the millisecond."
"You've already calculated it."
"I've been calculating it for two days. Since Thresh told us Helix was coming.
" She says this matter-of-factly, the way she says everything that other people would consider extraordinary.
Two days of parallel operational planning.
Six simultaneous workstreams. A defensive system designed from scratch using mining equipment and spreadsheet logic.
And she presents it like a quarterly logistics report, as if anyone could do this, as if the ability to hold six complex plans in active memory while sleeping three hours a night is not a form of genius but merely adequate time management.
"You said you were working on communication protocols."
"I was. And this. Simultaneously."
I feel a surge of something through the bond that is not mine. Pride. Not in herself, she rarely feels pride in herself, but in the plan. In the system she has built. The pride of a logistics coordinator who has turned an asteroid field into a defensive weapon using spreadsheets and mining charges.
"There's one more element," she says. "The decoy."
She highlights a section of the asteroid field opposite the civilian evacuation routes.
"Before Helix enters the approach corridors, we send a single ship in this direction.
Running hard, broadcasting an emergency signal.
Helix will read it as the evacuation. They'll split their force.
Some ships pursue the decoy, some enter the corridors. "
"Fewer ships in the corridors means better odds for the defense," Thresh says.
"Who runs the decoy?" Voss asks.
Silence. The decoy ship will be pursued by Helix vessels. It will need to outrun or outmaneuver them long enough for the real evacuation to complete. It is the highest-risk element of the plan.
"I will," Voss says. "The Rust Bucket is the fastest thing in the dock. And I've outrun Helix before."
"Mira..." Sira begins.
"Don't. I've been doing this for twelve years. I'm not stopping because the stakes got higher."
The plan is accepted. Work begins immediately.
Fen modifies the mining charges with assistance from the fabrication shop team.
Thresh reorganizes the security team into defensive positions.
Voss prepares the Rust Bucket for the decoy run.
I coordinate the twenty-eight defenders, assigning positions, reviewing capabilities, building a defensive structure that maximizes our limited resources.
Zara works from the operations center, where she has transformed the holographic display into a three-dimensional tactical map that tracks every charge placement, every ship position, every timing variable in real time.
She coordinates between teams with the same calm efficiency she brought to shipping manifests, except the cargo she is routing now is explosive and the delivery window is measured in milliseconds rather than hours.
She eats at her console. She sleeps in shifts of two hours.
She does not complain, because complaining requires acknowledging a state of distress, and Zara does not acknowledge distress.
She manages it. She routes around it. She turns it into a line item on a spreadsheet and optimizes until the distress fits within acceptable parameters.
I am not the military commander here. Thresh holds that role.
But I bring the Vorath understanding of battle, which is not a human understanding.
Human military doctrine relies on hierarchy, orders, chains of command.
Vorath martial philosophy relies on resonance.
Each defender understands their position not through orders but through awareness of the whole.
I cannot share resonance with non-Vorath, but I can share the principles: know your position, know your neighbors, trust the system.
On the second day of preparation, I find Zara in the operations center at three in the morning, surrounded by holographic models of the asteroid field, her eyes red with fatigue but her hands steady on the datapad.
"You should sleep," I say.
"Detonation timing. I'm recalculating for the third time. The margin of error on charge seven is too wide."
"How wide?"
"Four hundred milliseconds."
"That is a very small margin."
"It's too wide. Four hundred milliseconds of delay on charge seven means the asteroid fragment doesn't reach the corridor in time. The lead Helix ship gets through before the collapse. One extra ship in the engagement changes the defensive math from survivable to dangerous."
I sit beside her. Not to help, the calculations are beyond my expertise. To be present. To let the bond carry my steadiness to her and offset her fatigue.
She leans against me without stopping her work. One of my lower arms settles around her waist. She types with one hand and holds my arm with the other.
"I won't let them take this place," she says. "Haven is the first place that made sense to me. The first place where what I do is valued for what it actually is. I'm not losing it."
"You will not lose it."
"You can't promise that."
"I can promise that I will stand between this station and anything that threatens it. That is within my capacity to guarantee."
She looks up at me. The fatigue and the fear and the fierce determination are all visible, layered, unsorted.
She is too tired to organize her emotions.
They are raw, exposed, and underneath all of them is the simple, structural love of a woman who is staying up until three in the morning to narrow a four-hundred-millisecond margin of error because the lives of seventy-three people depend on her spreadsheet.
"I love you," she says. "I should say that more. In case."
"There is no 'in case.' We will survive this."
"You can't know that."
"I know you. And you do not build systems that fail."
She turns back to the datapad. The calculation continues. I hold her and I feel the plan taking shape around us, not just in the data but in the station itself, in the people who are working through the night to place charges and prepare ships and reinforce shields.
They are working because she gave them a plan. Not a general's plan. Not a warrior's plan. A logistics coordinator's plan, built from routes and timing and the precise understanding of how systems flow.
Tomorrow, Helix comes.
Tonight, we prepare.
And the woman in my arms narrows the margin of error from four hundred milliseconds to two hundred, and then to one hundred, and then she falls asleep against my shoulder with the datapad still in her hands, the final number on the screen a margin so tight that only someone who refuses to accept imperfection could have achieved it.
I carry her to bed. All four arms, steady and gentle.
She weighs nothing. She weighs everything.
Her body in my arms is the smallest and most important cargo I have ever carried, and I navigate the corridor to our quarters with a care that exceeds anything I have brought to combat or duty or the centuries of service that preceded this moment.
I set her on the bed. Pull the blanket over her. Her hand finds my arm in her sleep and holds on, the grip of someone who does not let go of things, even unconsciously.
Through the bond, I feel her dreaming. Not the content, which is hers alone, but the emotional texture.
She is dreaming about systems. About routes and timing and the clean satisfaction of numbers that align.
Even in sleep, her mind is working. Even in sleep, she is planning the survival of seventy-three people.
Tomorrow, we fight.
Tonight, I hold the planner and I let her rest.