Chapter 15 Zara
I wake up in a room painted in blue light with four arms around me and my first thought is: I need to recalculate the sleeping arrangement.
Not because it's bad. Because I'm a logistics coordinator and I just discovered that sleeping with a Vorath involves spatial considerations I hadn't accounted for.
His arms create a cage, a warm, protective, structurally impressive cage, and extracting myself without waking him requires strategic maneuvering.
I manage it. Barely. One of his lower arms twitches as I slide out, his fingers reflexively closing on empty air where I was. The markings in his skin pulse, a sleepy flare of blue, and then settle.
I stand in the shared living area between our rooms and I look at the data I was reviewing last night, the network models and communication protocols, and I realize I don't care about any of it right now.
Not because it isn't important. Because something more important happened and my brain is trying to catch up.
I slept with an eight-foot alien. A four-armed, bioluminescent alien who communicates through vibration and who loves me in a way that I can literally feel inside my chest.
The feeling is still there. Not the memory of feeling, the actual, present-tense feeling, a warmth in my sternum that pulses in rhythm with the sleeping Vorath in the next room.
The bond's secondary channel, the one he said would take months to develop, is broadcasting at a frequency I can no longer pretend I don't hear.
I know he is sleeping. I know his body temperature has dropped slightly, which is normal for Vorath rest cycles.
I know his emotional state is what I can only describe as contentment in low-power mode, a deep, structural satisfaction that requires no maintenance.
I know all of this because the bond is feeding it to me like data from a sensor array, and my logistics brain is absolutely delighted to have a new stream of information to process, even if that information is the emotional state of the person I just had mind-blowing interspecies intimacy with.
My logistics brain immediately tries to categorize this. Relationship: established. Status: intimate. Variables: species difference, bond mechanics, height differential, arm count. It's absurd. I'm trying to spreadsheet a love life that involves an alien whose skin lights up when I touch him.
I make coffee. Haven's galley supplies include actual coffee, grown in the greenhouse dome, and the normalcy of pouring a cup and drinking it while standing in a kitchen is grounding.
I am a person who drinks coffee. I am also a person who just experienced a biologically amplified intimacy feedback loop, but I am drinking coffee and that makes me a person in a kitchen and that's manageable.
Kael emerges twenty minutes later. He has to duck through the doorway and turn sideways to navigate the living area without knocking things off shelves, and the domesticity of it, the bigness of him in this small, normal space, makes something warm bloom in my chest that I don't fight.
"Coffee?" I offer.
"I do not consume human stimulants."
"Right. Vorath blood destroys foreign chemicals."
"This includes caffeine. I would process it before it reached my neurological system."
"So coffee is useless to you."
"The act of consuming it with you is not useless. I will have coffee."
I pour him a cup. He holds it in one of his lower hands, the precision pair, and the mug looks like a thimble. He drinks. His expression does not change.
"It tastes like heated water with a chemical component," he says.
"That's exactly what it is."
"Humans enjoy this?"
"Humans need this. There's a difference."
The morning is quiet. Domestic. Two people in a kitchen drinking coffee, except one of them is eight feet tall and the other is a fugitive from a megacorp and neither of them planned to be here.
I check my datapad. Three messages from Thresh about security updates, two from Sira about network operations, and one from Fen that reads: "The fabrication shop has a Type 4 plasma welder. I am content."
Haven is beginning to feel like a place. Not just a destination, a place. Somewhere with routines and messages and coffee in the morning.
I'm terrified of how much I want it to stay.
"I need to tell you something," I say.
Kael sets down his thimble of useless coffee. "Yes."
"The bond. The secondary channel. I've been feeling it for days, but last night it was... I could feel everything. Not just emotions. Sensations. When you touched me, I felt your response to touching me. When I touched you, you felt mine. It was a complete circuit."
"Yes."
"Is that normal?"
"For imprinting bonds that have evolved to kai'thenn, it is normal. For bonds of our duration, it is exceptional."
"What does that mean? Practically?"
"It means the bond will continue to deepen. Over time, the shared perception will extend beyond intimacy. You will begin to sense my physical state as well as my emotional state. Injury, fatigue, hunger. And I will sense yours with greater acuity."
"We're becoming... linked."
"We are linked. We are becoming more linked."
I sit with this. The logistics brain wants to model it, to project the curve, to understand the endpoint. But some systems don't have endpoints. They have asymptotes, always approaching, never arriving, infinitely deepening.
"Are you okay with that?" I ask. "Permanent deepening?"
"Zara. I told you last night that I would choose this without the bond. The deepening is not a complication. It is a gift."
"Gifts don't usually come with biological imperatives."
"Among the Vorath, the best ones do."
I finish my coffee and start working because if I don't start working, I will sit in this kitchen and think about what it means to be permanently, biologically, increasingly linked to someone who holds me with four arms and lights up when I touch him, and I will lose the entire day to feelings.
Feelings are not on my schedule. I have a refugee network to optimize.
On day four, Kael joins the station's security detail for a training session.
I watch from the observation deck because I told myself I was passing through and then stopped passing.
He moves through combat forms with Thresh and two other defenders, adapted for a training space that was not designed for someone with four arms and a reach advantage measured in feet rather than inches.
The other fighters circle him. He flows.
There is no other word for it. The four arms create patterns that make solo combat look like choreography, each pair performing independent functions that combine into a unified defense that the other fighters cannot penetrate.
Thresh, afterward, says: "He could hold a corridor alone against six."
"I know," I say. "He held a hull breach against four Helix enforcers during the battle. He didn't kill any of them. He chose not to."
"That level of restraint during combat is... not typical."
"He's not typical."
Thresh looks at me with the evaluating expression that security professionals use when they are reassessing a variable. "No," he agrees. "Neither are you."
The work absorbs me. For the next several hours, I'm in the operations center with Thresh and Sira, reviewing Haven's communication infrastructure.
The current system uses encrypted burst transmissions routed through a chain of relay points.
It's effective but slow. Messages take hours, sometimes days, to move through the network.
"The problem is latency," I explain, pulling up my models on the main display. "Each relay point adds processing time. The messages are secure but they're not fast. In a crisis, you need both."
"What do you suggest?" Sira asks.
"Parallel routing. Instead of sending one message through a chain of relays, split the message into fragments and route each fragment through a different path.
They recombine at the destination. It's faster because no single relay handles the full message, and it's more secure because intercepting one fragment gives you nothing. "
"That sounds like what you did with the escape shuttles," Thresh says. "The scatter pattern."
"It is. Same principle. Distribute the risk. Complicate the tracking."
"Can you build it?"
"I can design it. Fen can build the hardware modifications for the relay points. Voss can distribute the updated protocols to the network on her next run."
"How long?"
"Two weeks for the design. A month for full implementation."
Thresh and Sira exchange a look. It's the look of people who have been waiting for someone like me without knowing it.
"Do it," Sira says.
I work. The days develop a rhythm. Mornings: coffee with Kael, where he drinks a beverage his body immediately destroys and I pretend not to find his commentary on human habits devastatingly charming.
Daytime: operations center, building the parallel routing system, coordinating with Fen on hardware specs and Voss on network logistics.
Evening: dinner in the common area, where the station population gathers and I slowly learn names and faces and the particular rhythms of a community built from people who had nowhere else to go.
Nights: Kael.
The nights develop their own rhythm too.
We combine the rooms, as I planned, creating a sleeping space that accommodates both of us with what I call "optimized spatial utilization" and what Kael calls "you moved the furniture while I was training.
" The bed is his, the oversized reinforced one, and I sleep in the curve of his arms, which have become the most architecturally complex blanket in the Lattice.
I am, against every expectation and probably against my better judgment, happy.
Happiness is alarming when you've spent weeks running.
It is an unfamiliar system state, and my brain treats unfamiliar system states as potential errors.
It runs diagnostic checks. It searches for the malfunction that would explain why everything feels stable when nothing in my recent history suggests stability is a reasonable expectation.
It finds no malfunction. The stability is genuine.
And the genuineness of it is the most disorienting thing I've experienced since the cargo hold.
It feels like forgetting to check the rearview mirror. My brain keeps searching for the threat, scanning the perimeter, waiting for the other shoe to drop.
On the eighth day at Haven, the other shoe drops.
I'm in the operations center when Thresh enters with a face that I have come to recognize as his crisis face: calm, focused, everything but his eyes perfectly composed. His eyes are sharp.
"We've got a problem," he says. "Helix knows about Haven."
The room goes cold.
"How?" Sira asks.
"Intelligence intercept. Fen's been monitoring Helix communications since she fixed our antenna array. She picked up a coded transmission referencing 'Haven Station' by name. Not a general sector reference. The actual station name and its approximate coordinates."
"Approximate?"
"Within a few hundred thousand kilometers. They don't have the exact position, but they know the sector and they're narrowing it."
"How long before they find us?"
"If they send a search team? Days. If they send a fleet? They could blanket the sector in hours."
I'm already at the console, pulling up data. "How did they get the name? Haven doesn't appear in any public database."
"It appears in Helix's internal database," Thresh says. "Because Helix captured a refugee two months ago who knew the name. A Keth trader who was trying to reach us and got intercepted at the Thessan gate."
The room is quiet. Sira's translucent skin shifts color, the Delosi stress response.
"Options," she says.
"Evacuate," Thresh says. "Move the station population to backup locations, scatter the network, rebuild somewhere else."
"That takes weeks," I say. "And we lose the infrastructure. The fabrication shop, the greenhouses, the communication array. Everything that makes Haven functional."
"Or we defend," Thresh says.
"Against Helix?"
"Against whatever they send. This station has defensive systems. Modest, but functional."
I think about the station's defenses. I've mapped them. Two automated turret emplacements, a shield generator that covers the station core, a sensor array that Fen has significantly improved. It's not nothing. But against a Helix assault team, it's not much.
"We need more information," I say. "When are they coming? What are they sending? We can't plan a defense without knowing the threat scale."
"Agreed. Fen is monitoring. As soon as we have more, we'll reconvene."
I leave the operations center and find Kael in the training room. He reads my expression, or more accurately, my emotional frequency, and is on his feet before I speak.
"What has happened?"
"Helix knows about Haven. They have approximate coordinates. They're coming."
His markings flare. Bright blue, combat-ready. I feel the resonance shift through the bond, the protective instinct surging forward, and beneath it, something colder, something I've only felt once before, on the cargo ramp at Beacon Point.
Readiness to fight.
"When?" he asks.
"We don't know yet. Days, maybe."
"I will coordinate with Thresh on defensive posture."
"I'll work on the logistics side. Evacuation plans, supply caching, communication protocols for dispersal."
We look at each other. The morning coffee, the combined rooms, the happiness I was just getting used to, all of it suddenly fragile.
"We knew this could happen," I say.
"We did."
"I just wanted more time."
He crosses the room and takes my face in his lower hands, the precision pair, gentle. His upper arms rest on my shoulders, steady.
"You will have more time," he says. "Whatever comes, we will face it. And you will plan. And I will protect. And together we will ensure that Haven survives."
I lean into his hands.
"Together," I say. "That's the key variable."
"It is not a variable. It is a constant."
I take a breath. Then I pull away and lift my datapad.
"Okay. We have work to do. Let me show you what I need."
We begin.