The Station Has Politics

Vasht found me in the equipment bay at 0840, which was early enough to mean the meeting had been scheduled before I was awake.

"Compact Command communication in twenty minutes," she said. "Officers from three divisions. You need to be present."

"What's the topic."

"Officially, a progress review on the integration project." She handed me a small data chip, which in Solvari operational shorthand meant: read this before you walk into the room. "Unofficially, several people who have not been involved in this project are about to become very interested in it."

I set down the calibration tool I'd been running over a damaged rack mount and looked at the chip. "What's on this."

"The project's resource expenditure summary for the last six weeks." She watched me the way she watched most things: steady, patient, waiting to see what I did with information before she decided what to say next. "They will have reviewed it before the communication opens."

I turned the chip over once. The data chip was a flat square, matte gray, with one beveled corner to indicate orientation. The Solvari made everything with one deliberate asymmetry so you couldn't insert it backwards. I'd noticed that in the first week and it had told me something about how they thought.

"How many people in the meeting are there specifically to take this project away from you," I said.

She didn't hesitate. "At least two that I can identify from the attendee list."

"And the others."

"Are undecided and will be watching how the conversation develops."

Twenty minutes was enough time to read a resource expenditure summary. I read it in eleven, standing at the equipment bay's secondary console, and the picture it painted was the picture I expected: the integration project was using Sonn's specialized research time, station space, Durrik's training hours, and Vasht's command attention, all for an asset that had not yet produced field results. That was the framing. The summary did not include the fourteen-day assessment data or Sonn's integration readings because those were in a separate classified file that the officers reviewing this particular document had not been cleared for.

Which was interesting.

"The people who scheduled this meeting," I said. "Did they specifically request the resource summary without the integration data, or did they receive what gets sent as a standard package."

Vasht looked at me with an expression I'd learned to read as recalibration. "The standard package for a resource review does not include classified integration data."

"So they may not know what the numbers actually show."

"They may not."

"But you know. And whoever built the attendee list knows."

She said, "The division heads who will be on this communication have varying degrees of access to the project's technical data. The two I am concerned about have access to the resource summary and the initial compatibility assessment from six weeks ago. They do not have access to the last three weeks of integration readings."

"Because those went into a higher classification tier when Sonn flagged the development rate."

"Correct."

I set the chip down. "You put the concerning data where they couldn't see it."

"I classified it at the appropriate level given Sonn's assessment of its sensitivity."

There was a technical truth in that sentence and a strategic one underneath it, and Vasht was too precise to say something technically false, which meant she'd constructed the sentence carefully. I'd been learning to read the gap between what she said and what she'd decided to do, and the gap in that sentence was clear enough.

"Okay," I said. "Tell me the two names."

She told me. Division Head Corrath, who oversaw resource allocation for Compact ground operations, and Sub-Director Fennis of the medical research division, who had been trying to get access to a compatible-biology subject for a separate research track since before my name had appeared on anyone's compatibility list. Corrath's interest was efficiency. Fennis's interest was science. Neither of them was hostile to me personally because I was not yet real to them in the way you became real to people after they'd met you. I was a resource allocation line and a data point.

That would change in about nine minutes.

"Who else is on the communication," I said.

"Commander Orath, who is Corrath's direct supervisor and will be observing rather than participating. Two staff officers I don't expect to speak unless Corrath or Fennis establishes a clear directional consensus. And a representative from the diplomatic office, presence required for any communication involving a non-Compact biological entity."

"That's me."

"That is you."

The diplomatic office representative was there to make sure nobody accidentally said something that violated the terms I'd negotiated in Chapter 3, which meant at least one person in the meeting had read those terms carefully enough to know where the lines were. That was useful.

"I'm going to need to know," I said, "what a military research program would mean in specific operational terms. Not the general description. The actual structure."

Vasht walked me through it in the time we had left: restricted movement, daily monitoring by research staff outside of Sonn's chain, required compliance with assessment schedules I hadn't agreed to, and a reclassification of my legal status from independent contractor to "integrated research subject," which was a category of designation that had specific rights attached to it under Compact law. Fewer rights than independent contractor. More rights than a prisoner, which was apparently a meaningful distinction in the system they operated under.

"Can they compel it," I said.

"Not without your agreement. But they can make the current arrangement untenable by withdrawing resources."

"Meaning if they pull Sonn or restrict Durrik's access, the project stalls."

"Yes."

"And they can do that."

"Corrath controls resource allocation. Yes."

We had two minutes. I followed Vasht to the communications room, which was a small compartment off the station's command section with a fixed display and four chairs arranged in a configuration that Solvari apparently considered appropriate for formal communications. Three chairs were for Vasht's use and the station's communications officer, who handled the technical side. The fourth was for me, positioned slightly to the left of center, which I suspected was a decision someone had made deliberately to indicate that I was present but not seated at the table.

I moved the chair to center before I sat down.

The communications officer, a young Solvari named Edrin whose scales ran toward orange rather than the blue-gray that was more common, noted the chair position and did not comment. Vasht took her chair and did not comment. I sat down.

The display opened on three faces: a Solvari with the heavy facial scaling that indicated age, who would be Corrath; a Navari with the four-lobed cranial structure I'd been cataloguing since my first week on the ship, who would be Fennis; and three others arranged behind them in the formation of people who were present to watch rather than lead.

The Compact used no pleasantries in formal communications. Corrath opened directly.

"Commander Vasht. We're reviewing the resource allocation on the human integration project. Six weeks of dedicated research support, training hours, and station space have produced a preliminary integration and a development assessment. We'd like to understand the current trajectory."

Vasht's voice was the same as it always was: short, no apology. "The integration is proceeding ahead of projected schedule. The subject's development rate is in the highest range documented in any Aeluun case file. We are preparing for the first operational deployment within two weeks."

Sub-Director Fennis leaned forward slightly. "The development data you're referencing. The last readings I have access to are from three weeks ago. They showed promising results but pre-operational capability. Do you have more recent data?"

"The most recent integration readings are classified at a level above this communication's access tier," Vasht said.

Fennis's cranial lobes shifted, which was a Navari expression I'd seen before. Not quite a frown. Something that translated roughly as: that's inconvenient. "I'd like to request elevation of that access for this review."

"That request would need to go through Compact Intelligence, given the sensitivity of the data. I can facilitate the process after this communication."

Which meant Fennis wouldn't see the recent readings for at least a week, during which time the operational deployment would have happened, and the data from an actual field engagement would supersede the question of what the training readings showed. I watched Vasht manage this with the economy of someone who had been doing it for years and didn't need to be obvious about it.

Corrath came back in. "Regardless of the current development status, the resource question stands. We're running a six-person research and training support structure for a single untested asset. I want to understand the justification for continuing that structure rather than consolidating the project into the research facility in the Ninth Station cluster, where the infrastructure already exists and the costs are amortized across multiple programs."

And there it was. Not a hostile seizure. An efficiency argument.

I said, "What's the legal status designation under the Ninth Station research facility's protocols."

Three faces on the display shifted toward me simultaneously. The two staff officers who hadn't spoken straightened slightly. The diplomatic representative, who had been at the edge of the display, became more attentive.

Corrath said, "You are the human subject."

"I am," I said. "And you're proposing to move me to a facility. I'm asking what my legal designation would be under that facility's operational protocols."

There was a pause. Fennis said, "Integrated research subject classification. It's a standard designation for non-Compact individuals participating in Compact research programs. The rights structure is well-established and compliant with the Compact's biological welfare treaties."

"What does it allow me to do that my current contractor status doesn't."

Fennis opened their mouth and then closed it. They'd been prepared to describe the benefits of the research program. They hadn't been prepared to answer the question in the comparative direction.

"The designations have different structures," Fennis said. "They're not directly comparable."

"Sure they are," I said. "What can I do as an independent contractor that I couldn't do as an integrated research subject." I let that sit for a second, then answered it myself: "I can end my participation. In writing, with fourteen days notice, under the terms I negotiated with Commander Vasht six weeks ago. What's the equivalent provision under integrated research subject status."

The diplomatic representative spoke for the first time: "The research subject classification does not include a unilateral withdrawal provision for ongoing studies."

"So you'd keep me."

"It's not a matter of keeping. It's a matter of program continuity. The integration process, once begun, creates certain obligations with respect to monitoring and ongoing care. It wouldn't be appropriate to simply end oversight mid-development."

"Who decides whether the oversight is appropriate."

"The program directors, in consultation with relevant medical oversight."

"Not me."

"You would have significant input."

"Input," I said.

Nobody added anything to that word.

I'd been in enough conversations about property rights and land use with county authorities to recognize the architecture of what I was being offered. Input meant they listened to you before doing what they'd already decided. It was a courtesy structure, not a power structure, and calling it significant didn't change what it was.

Vasht had been quiet during the exchange. She was sitting with her hands flat on the table in front of her, her expression the specific neutral that meant she was watching a situation develop that she had prepared for but could not fully control.

"I appreciate the interest," I said to the display. "I'm going to stay with the current arrangement. I'll be operational in the field in two weeks, at which point the resource question becomes a different calculation."

Corrath said, "That timeline is contingent on the current training structure continuing at its present cost."

"It is."

"And if the resource allocation is adjusted."

"Then the timeline adjusts. And Eshet's Dominion unit continues operating in the Caleth Corridor while you work through the facility transfer paperwork." I wasn't being sharp about it. I was just making the arithmetic visible. "I checked the sector casualty rate for the last four months before I came in here. The Compact unit holding that sector has lost thirty-one percent of its effective strength in attritional engagements. That's the problem this project exists to address. The question of whether the addressing happens through the current structure or a research facility is, in my view, secondary to whether it happens fast enough to matter."

Corrath and Fennis exchanged a look. I couldn't read Solvari-to-Navari visual communication at this range, but the content was accessible through the pause that followed: they were deciding whether the efficiency argument was worth the friction of the counter-argument.

The staff officers were definitely not going to speak. The diplomatic representative was writing something.

Commander Orath, who had been observing from the back of the frame the entire time, spoke for the first and only time: "Commander Vasht. Your operational timeline is two weeks."

It wasn't a question. But it was also not the phrasing Corrath had used. Corrath had said contingent. Orath said timeline, which was different.

"Yes, Commander," Vasht said.

"Then this conversation has a natural review point in two weeks." Orath's tone closed the subject the way a door closes: complete, without drama. "Sub-Director Fennis, the access elevation request through Intelligence will give you a clearer picture of the development data when it processes. Division Head Corrath, I'll review the resource projection you've prepared and we'll discuss it separately."

The communication closed.

The display went to neutral gray. Edrin, at the technical console, began the shutdown sequence with the focus of someone deliberately not commenting on what had just happened in the room.

I pushed back from the table. My back was tight from the equipment bay work I'd been doing before Vasht found me, and I rolled my shoulder once to work out the specific knot that the calibration work always put between my shoulder blade and my spine.

"Orath shut it down," I said.

"Orath makes decisions based on operational outcomes," Vasht said. "You gave him one to point to."

"Two weeks."

"Two weeks is what we have."

She stood up. Her posture was exactly what it had been when she'd walked into the equipment bay: controlled, economical, nothing wasted. But something in the set of her jaw was different, and I'd been reading Vasht long enough to know that the difference meant she'd spent something in the last twenty minutes that she couldn't recover easily.

"Fennis is going to get the access elevation eventually," I said.

"After the field deployment, the data will be what it is. The deployment results will speak more clearly than the training readings."

"And Corrath."

"Corrath will review the resource projections with Orath, who will evaluate them in the context of whether the project produced a usable operational result in the Caleth Corridor." She moved to the door, stopped with her hand on the frame. "You said thirty-one percent."

"Thirty-one point four," I said. "Over four months. I did the math off the briefing documents this morning."

"I know the number."

"I figured."

She looked at me for a moment. "You understood what was at risk in that conversation."

"You handed me a resource summary and told me two of the attendees wanted to move me to a research facility. It wasn't difficult to work out."

"No," she said. "But working it out and being willing to say it on a Command communication are different things." She paused. "You should know: that communication is on record. Your statement about the legal designation is now part of the project's official documentation."

"Good," I said.

She waited to see if I'd add anything. I didn't.

"Durrik is on the training deck at 1000," she said, and left.

I sat in the communications room for another minute after she went, looking at the neutral gray display. The diplomatic representative had been writing something during the exchange, and the specific moment they'd started writing was when I'd asked what an integrated research subject status allowed me to do that my current status didn't. That was the question that had landed in the official record the way a foundation stake lands: once it was in, the structure around it was committed to that position.

I was an independent contractor on record in a Command communication. Not a research subject, not a military asset. The distinction was small in some ways. In the specific ways that mattered, it was everything.

The Solvari's one beveled corner on the data chip was still in my hand. I set it on the table next to the chair I'd moved to center and left the communications room.

The corridor outside was regular station morning: the maintenance worker on this shift with a different gait than the overnight rotation, two Solvari crew members running a cable check between the command section and the forward compartments, the ventilation pulling its cycle at the forty-nine-second intervals I'd stopped consciously tracking sometime in the second week. My pattern recognition ran its quiet inventory of movement and position. None of it flagged as threat. All of it registered at the elevated baseline resolution that was the permanent new normal.

I took the corridor toward the research bay because Sonn would want to know the outcome, and also because there was a reading from this morning's pre-meeting work session that I'd wanted to ask about and hadn't gotten to before Vasht appeared.

Sonn was at their primary monitoring station, surrounded by the overnight data I'd left them generating. They looked up when I came in, which was their habit: they tracked entry with the same deliberate attention they gave to their displays, not surveillance, just the natural awareness of someone who processed their environment carefully.

"The Command communication," they said. Not a question.

"Finished. I'm staying on the current arrangement. Two weeks before the next review."

Sonn absorbed this with a nod that meant they'd already run several scenarios for the meeting's outcome and were now filing the actual result. "Vasht managed the data access question."

"She classified the recent readings appropriately," I said, giving Vasht the same technical truth she'd given me.

The corner of Sonn's mouth shifted in what I'd learned to read as the expression they used when they registered something that was accurate and also incomplete and didn't feel the need to press it. "Sub-Director Fennis will eventually receive access."

"After the field deployment. By then the question is what the field data shows, not what the training readings projected."

"That's the correct sequencing," Sonn said. "Vasht knows that."

"She does."

Sonn was quiet for a moment, making a small notation in their monitoring log with the precise economy of motion that was their physical signature. Their hands were four-fingered, the joints placed differently than a human hand, and they wrote with a downward pressure that was more even than a human grip, nothing varying between strokes. I'd spent enough time watching Sonn work that these details had moved from conscious observation into the background register where the pattern recognition kept all the information I wasn't actively using.

"The cascade risk briefing," Sonn said. "You told me to inform Vasht this morning."

"Did you."

"Yes. She received the information with, I would say, more equanimity than I expected." They paused. "She asked the same question you asked last night: what are the early indicators."

"And."

"I gave her the same information I gave you. She asked whether the daily monitoring protocol would produce actionable data in time to intervene if the indicators appeared. I told her that was the intent."

"What else."

Sonn set down the notation tool. "She asked me whether I believed the development pace was a net risk or a net asset given the operational timeline. I told her my honest assessment was that I didn't know, and that the honest answer to a question about unknown territory is that the map runs out."

"She'd have liked that answer."

"She said approximately the same thing you just said." A pause. "She also told me to continue the daily monitoring protocol and to tell her directly, not through a report, if I saw the early indicators appear. She was specific about the directly."

Vasht building her own parallel notification chain, bypassing the report structure, so that the information moved in real time rather than through documentation latency. She'd done the same thing with the classified data tier and the meeting structure this morning: she understood exactly where the system's procedural mechanisms worked in her favor and used them without ceremony.

"She's good at this," I said.

"Yes," Sonn agreed, with the tone of someone who had not always found this a comfortable fact.

I crossed to the secondary display, where the morning's pre-meeting readings were still showing. The specific pattern I'd wanted to ask about was in the third hour of the overnight data: a slight increase in the pattern recognition's baseline activity during what my sleep log showed was a period of lighter rest, around 0340. The activity wasn't the early indicator Sonn had described, it wasn't the intrusive kind, it wasn't the threat-response firing on neutral stimuli. It was more like the system running a low-level maintenance inventory on its own processing channels.

"This," I said, and pointed to the 0340 reading.

Sonn came around to look at it. They were quiet for a moment, which was the processing pause, not evasion. "That's within normal range for integration activity during low-rest states. The system uses lighter rest periods to consolidate the day's processing inputs. It's the equivalent of what human sleep architecture does with memory consolidation, but for sensory and pattern data rather than declarative memory."

"It doesn't match the early indicator description."

"No. It's the opposite, in functional terms: the system is doing appropriate background processing at an appropriate intensity level. If the indicator were appearing, you'd see this same activity level during full rest states, or you'd see it spike during waking periods where there's no threat input. What you're seeing here is contextually correct."

"Good," I said.

"You checked the reading before the meeting."

"I check things before meetings."

Sonn's expression moved through the not-quite-a-smile that meant they'd registered something as both specific to me and also something they'd predicted I'd do. "Your grandfather taught you that."

"My grandfather taught me to check the rifle before the hunt and the fence before the storm. The principle extends."

"Yes," Sonn said. "It does."

I had forty minutes before the 1000 training session. I spent twenty of them with Sonn going through the overnight data in the detail that the pre-meeting time crunch hadn't allowed, asking about three other minor readings that had flagged my attention and getting the same kind of answer for each: within normal range, contextually appropriate, not the indicator, here is what distinguishes it from the indicator. Sonn answered each question with the precision I'd come to rely on, the kind of precision that didn't pad the answer or soften the edge of it to make it easier to receive.

The last twenty minutes I spent back in the equipment bay, finishing the rack mount calibration I'd started before Vasht arrived.

The work was straightforward: the mount had a misaligned tensioning mechanism that was causing intermittent contact failures in the storage array it supported. The fix required resetting three tension points in a specific sequence and then running a contact test to confirm the alignment held. It was the kind of mechanical problem that had a clean solution once you understood the mechanism, and understanding the mechanism was mostly a matter of looking at it carefully before you touched anything.

My pattern recognition, at the elevated baseline it now operated from, put the storage array's component layout in a spatial register that hadn't been available to me six weeks ago. I noticed the third tension point's position relative to the frame before I'd physically checked it, which let me stage my approach without the extra step of measurement. It saved maybe ninety seconds. The ninety seconds didn't matter on this particular task.

They would have mattered in the Caleth Corridor.

I finished the calibration, ran the contact test, confirmed the alignment held, and set the tool back on the equipment bay's wall rack in the correct position. The Solvari organized tools by size and function on a grid system with color coding, and after six weeks I didn't need to look for the right position anymore. My hands went to it.

That was also the system, probably. The spatial precision that had been threading itself into the background of everything I did.

At 1000 I was on the training deck and Durrik was already there, running through the footwork drills he used as his own warm-up, methodical and unhurried. He looked up when I came through the door.

"Meeting happen," he said.

"Finished."

"You still here."

"I'm still here."

He nodded once and went back to the footwork drill, and I began my own warm-up, and the training deck's familiar geometry settled into its familiar register around us, and nothing needed to be said about the Command communication or Fennis or Corrath or the two weeks we now had, because the training deck was where the actual preparation happened and everything else was the condition the preparation had to exist inside, and Durrik's opinion of conditions he couldn't directly affect was to acknowledge them once and then work the problem he could work.

That, I'd figured out three weeks into training, was why Durrik and I had developed whatever it was we had. Not friendship exactly. Something more functional than that: two people who solved problems the same way and had the respect for each other that comes from watching someone else do the same work you do and do it cleanly.

"Vasht tell you about the deployment timeline," Durrik said, midway through the first drill sequence.

"Two weeks."

He nodded, made a correction to my lead position without breaking the drill rhythm, and moved on. The correction was two centimeters of foot placement that changed my weight distribution through the follow-through. It was the kind of correction that had a name in formal martial instruction that Durrik never used; he just moved your foot and kept going.

"We're adding live scenario work this week," he said. "Full communication integration, not just movement."

"The tactical comm system."

"And the unit protocol for the specific Compact structure you'll be attached to. Greel runs his unit on a modified framework. I've got the specs."

Greel's name. The Chethari officer who commanded the unit in the Caleth Corridor. This was the first time the name had come into the training deck rather than the briefing room. It was a small thing. It made the Caleth Corridor more specific in a way that the sector maps and casualty statistics hadn't.

"What's the modification," I said.

"He shortened the communication cycle. Standard Compact protocol has a twelve-second check-in window; Greel runs six. Faster tempo, more responsive to engagement changes, harder on new personnel who haven't internalized the baseline sequence." He paused in the drill, looked at me. "You'll need to internalize it before you're in the field. I don't want you thinking about the comm cycle when you should be thinking about the ground."

"How long to internalize."

"Most people: four days of drilling. You." He considered this the way he considered operational facts, without sentiment. "Probably three. Possibly two if the pattern recognition does what I think it does with repetitive sequential inputs."

"You've been talking to Sonn."

"I've been reading the assessment reports I'm authorized to read," he said, which was a different statement with the same information. He restarted the drill. "Two minutes on the sequence, then we run it at tempo."

I ran it at tempo after two minutes, and Durrik made one correction in the first pass and none in the second, and after the third he said we were moving to the communication integration work, which meant the rest of the morning was going to be drilling Greel's six-second protocol until it sat below the level of conscious attention.

By 1200 I'd run the comm sequence forty-seven times. By 1300 I'd stopped counting.

Somewhere in the Ninth Station cluster, Sub-Director Fennis was filing an access elevation request with Compact Intelligence. Somewhere in the resource allocation division, Corrath was reviewing the projection documents with Commander Orath. The diplomatic representative's notation from the morning's communication was part of the project's official record, and my legal status was documented in a way that would require formal Compact proceedings to change.

I was an independent contractor on record, in the field in two weeks, drilling a six-second comm cycle in a training deck with a man whose opinion I trusted because he'd earned it the only way I knew how to measure trust: by telling me what was true without any apparent interest in whether it was comfortable.

The integration ran its inventory. The drill ran its sequence. The forty-nine-second air cycle, which operated on every Solvari station in the Compact's network at the same interval, counted its time.

Two weeks.