The Pull-Back Order

Vasht arrived at the forward position three hours after I submitted the integration briefing to the replacement soldiers' shared file, which meant she'd been in transit before the briefing was finished, which meant the comm from Command had come in earlier than she'd told me.

She walked the perimeter circuit first, which I watched from the secondary observation point because I was already there and she was making the kind of inspection that wasn't about the perimeter. When she came inside and found me at the equipment table where I'd been running the secondary defensive geometry notes, she sat down across from me and put a data tablet face-down on the surface between us.

"Command issued a directive this morning," she said. "They want you extracted from the Caleth Corridor."

I looked at the tablet. "Extracted to where."

"A research facility in the Prath system. Controlled environment, full Thuvari integration support, the capability to run accelerated development protocols that the field conditions here can't provide." She kept her hands flat on the table, not touching the tablet. "The language they used is 'accelerated development under controlled conditions.' The subtext is that you performed better than their projected timeline and they want to know what they're working with before you're in another live engagement."

"What they're working with," I said.

"Their language, not mine."

I leaned back on the equipment case I'd been using as a chair. The secondary defensive geometry file was still open on the display beside me, half-finished, the northern choke point annotation waiting for the correction I'd been in the middle of making when I heard her boots on the approach corridor. "And you're telling me rather than just scheduling the transport."

"Because you have a contract," she said. "You know that. No orders you haven't agreed to."

"So this is a request."

She didn't answer that directly. "There's a Command officer on the link right now. He wants to walk through the directive with you." She turned the tablet over and pushed it toward me. The display was showing a comm hold indicator, the kind that meant an open channel with someone at the other end waiting. "His name is Coordinator Palleth. He has operational authority over the research facility placement recommendation."

I looked at the tablet. Then I picked it up.

The officer on the comm link was Solvari, older than Vasht, with the kind of posture that came from years of rank rather than years of field work. He had thin facial scaling along his jaw that caught the light of whatever room he was calling from, and he was sitting very straight, which told me this conversation had a specific purpose and he knew exactly what it was.

"Mr. Caulfield," he said. "I'm glad Commander Vasht was able to arrange this communication."

"What's the research facility?" I asked.

A short pause. He'd probably prepared an opener. "The Tessavar Integration Research Institute. It's a Compact-administered facility that has hosted Thuvari researchers for thirty years. Full diagnostic capability, controlled stress protocol testing, and a development acceleration program that has shown measurable results with integration subjects at your current stage."

"Integration subjects," I said.

"It's a term of classification, not a characterization."

"How long?"

"The standard developmental acceleration program runs eight to twelve weeks."

I set the tablet down on the table but left the comm running so Palleth could hear the room. Vasht was watching me the way she watched things she wasn't sure about, which was attentive and very still. I said, to the room as much as to the tablet, "Walk me through what accelerated development under controlled conditions means in practice."

Palleth's voice came from the tablet. "A structured series of stress protocols, designed to advance your integration development in a measured progression without the unpredictability of field conditions. You would be working with specialists who understand the Aeluun system at a research level, not just an operational one."

"Stress protocols," I said. "Designed by who."

"The Institute's research staff, supervised by Thuvari integration specialists."

"Sonn," I said.

"The Thuvari liaison assigned to your case would be included in the transition briefing, yes."

That wasn't the same as yes, and I noted it. "The directive says extracted. What's the timeline on the extraction order?"

Vasht said, quietly, "Forty-eight hours."

Palleth said, "Commander Vasht is correct. The directive was drafted with an operational urgency consideration given the recent engagement data."

I looked at Vasht. She was still not touching the table. I said, "Forty-eight hours puts the extraction before the replacement soldiers complete their terrain familiarization. The briefing I just finished assumes two days of integration before they're at anything like functional readiness on the northern approach geometry."

"The replacement soldiers will be briefed by—"

"They're being briefed by a file," I said. "A file I wrote. There's a difference between reading an approach geometry briefing and going over the terrain with someone who knows why the coordinates are offset. The secondary observation point at the north corridor primary position has a dead angle that isn't in the survey data because the survey predates the drainage infrastructure damage from the last engagement. If the replacement soldiers don't know about that angle before they're posting observation there, they're going to be behind on any contact that comes from the northeast service corridor."

Palleth was quiet for a moment. "Mr. Caulfield, I understand your concerns about field continuity. The operational unit will have a transition period before their next scheduled engagement."

"Scheduled by who," I said. "The Dominion has two probing contacts on our intelligence log from before the node operation and a surveillance package that's been working this sector for two weeks. The transition period will be however long it takes Eshet to decide the unit is at reduced readiness."

A different kind of quiet this time. Palleth hadn't expected me to know Eshet's name.

Vasht's hands were still flat on the table. She hadn't moved since I'd started talking.

I picked the tablet back up. "What's my legal status at the Institute?"

"You would be classified as a research participant with Compact-contracted specialist status, consistent with your current classification."

"Would I have the right to terminate my participation?"

"The research program has structured exit protocols that—"

"That's not a yes," I said. "What are the exit conditions."

Palleth's tone had gone cooler. Not angry, just precise in the way people got when they were revising their approach. "The standard exit protocol requires a review period of fourteen days after a termination request is submitted, during which the research staff completes any open diagnostic procedures."

"So no."

"The review period is a safety measure to ensure—"

"I have a contract," I said. "The contract says no orders I haven't agreed to and the right to walk away if the device integration causes permanent harm. A fourteen-day review period on a termination request isn't the right to walk away. It's the right to wait two weeks while someone decides whether they'll let me leave." I set the tablet back down. "I'm not going."

Palleth let the silence sit for a few seconds. When he spoke again, the precision was still there but something underneath it had shifted, the kind of shift that meant he was reaching for a different lever. "Mr. Caulfield, the operational situation has changed significantly since your contract terms were negotiated. The sensor data from your recent engagement has been reviewed at Command level. Your development timeline has exceeded projections in ways that create both opportunity and risk. The Institute is the appropriate environment for managing that risk responsibly."

"Managing it for who," I said.

Vasht made a small sound, not a word, just a breath that said she'd seen this coming and had been hoping I'd stop before I got here.

"The Compact's research interests are aligned with your safety," Palleth said. "The accelerated protocol exists to ensure your development proceeds in a way that doesn't cause the kind of integration cascade documented in Thuvari historical—"

"I read the same historical records you're referencing," I said. "The cascade conditions were high-intensity repeated stress over a compressed period. If you want to prevent cascade conditions, the accelerated stress protocol at a research facility is not obviously better than field deployment. It's faster. Faster is the problem, not the field."

Palleth said, "The Institute's protocols are designed to prevent exactly that outcome."

"Designed to, yes," I said. "By people who have never run a human integration before. I'm the first one. Whatever they designed those protocols for, they designed it for a data set that doesn't include me. Sonn told me that in week one."

The comm was quiet for long enough that I could hear the faint carrier signal underneath the hold indicator. Then Palleth said, "I want to be clear, Mr. Caulfield, about the operational context here. The Dominion has escalated its presence in the Caleth Corridor specifically because of your integration readings. The threat environment around your current position is increasing, not static. Compact Command's directive to extract you is partially a security measure."

"I understand that," I said. "If the threat environment gets bad enough that my presence is creating more risk for the unit than my capabilities are offsetting, I'll tell Vasht and we'll make a different decision. That's a field call based on field conditions, not a directive issued from a comm relay three systems away."

Palleth said, "That is not how Compact command structure functions."

"I know. That's why I'm not Compact military. We've been clear on that since the beginning."

The silence this time lasted longer. I watched Vasht's face. She was looking at the table, not at me, not at the tablet. She had the expression of someone running calculations on a problem that doesn't have a clean answer.

Palleth said, "I'm going to need to discuss this with the operational review board and revert to Commander Vasht."

"That's fine," I said. "Thank you for the call."

I set the tablet down. The comm indicator went to closed.

Vasht didn't move for a moment. Then she picked up the tablet and held it without looking at it. "Derek."

"I know," I said.

"You cost me something in there. You know that too."

"Yes."

She stood up. She held the tablet by one edge, the way you hold something you're deciding whether to put away or throw. "Palleth is going to go back to the review board with a recommendation to reclassify your contract status. They have legal standing to argue that the operational situation has materially changed since the contract was negotiated."

"Do they have standing to win that argument."

"I don't know," she said. "Maybe. It depends on which officers are on the review board and whether they want the political cost of forcing a compliance issue with an asset who's generating this kind of operational data." She put the tablet in her field bag. "It also depends on whether I can make the case that field deployment is producing better developmental results than controlled research conditions would, which is an argument I've been making for two weeks and the node engagement data is the best evidence I've ever had for it."

"Then make the argument."

"I am making the argument. I have been making the argument." She slung the bag over her shoulder. "What I need from you is not to make it harder to make."

I looked at her. "I'm not going to agree to conditions I can't walk away from."

"I know that."

"Then we agree on the thing that matters."

She studied me for a moment in the way she did when she was deciding how much of what she was thinking to say out loud. She said, "You're not wrong about the controlled protocol conditions. You may not be right about your judgment being better than the collective analysis of people with more experience in integration development. Both of those things are true at the same time and I need you to understand that the second one is real, not political cover."

I said, "I know."

She left. The approach corridor carried her footsteps until it didn't.

Durrik was in the corridor, which I knew because I'd seen him through the observation port when Vasht came in, and because Durrik stationed himself where he could hear things he thought he should hear without making it look like that's what he was doing. He walked in a minute after Vasht left and went to the far end of the equipment table and started checking the status readouts on the communications array there, which didn't need checking.

I went back to the secondary defensive geometry file and pulled up the northern choke point annotation.

He said, without looking up from the array, "Command's going to push that argument again."

"I know."

"Next time Palleth won't be the one on the link. It'll be someone with legal staff in the room."

"Probably."

He turned a calibration dial that was already calibrated. "You were right about the fourteen-day review period."

"Yes."

"Being right and being useful aren't the same thing," he said.

The annotation cursor was sitting on the dead angle coordinate. I moved it to the correct offset and typed in the infrastructure damage note. "I know," I said.

He turned another dial. "Vasht's got less credit to spend than she did this morning."

"I know that too."

The equipment array made the small cycling sound it made every four minutes when it ran its self-diagnostic. Durrik watched it, then looked over at me, and I'd been working with him long enough to know what that look meant, which was that he'd said the things he came to say and he was deciding whether there was a third one.

He decided there wasn't. He checked the array's output display, logged something on his field recorder, and walked out.

I finished the dead angle annotation and moved to the next item in the geometry file, which was the drainage channel coverage from the service corridor's secondary approach vector. The replacement soldiers needed to know where the channel's depth changed, because the survey data showed it as uniform and it wasn't, and an ungifted soldier caught in the shallow section of what they thought was a four-meter-deep drainage channel was in a different kind of trouble than one caught in the deep section.

The file took another forty minutes to finish. I read it through twice, adjusted three coordinate entries where I'd used the equipment-row unit system inconsistently, and submitted it to the replacement soldiers' queue with a note that the northern approach geometry section should be priority reading before their first perimeter rotation.

Then I sat with the display off and the equipment bay quiet and the Aeluun interface running its low background hum that I heard as much through the right side of my skull as through the air, and I thought about what Vasht had said.

She was right. Both things were true at the same time. I knew the controlled protocol conditions were a real problem; I also knew I was a sample size of one and the collective research of people who'd spent thirty years studying Thuvari integration cases was not nothing. The fact that no one had run a human integration before meant I was the most relevant data point, but it also meant I was running on a map drawn from neighboring territory, and the researchers at Tessavar had at least been to the neighboring territory, which I hadn't.

The tactical question was the same one it always was: which risk was real and which was management, and how much of my certainty about the answer was evidence and how much was the same resistance to being managed that had been creating friction since week one.

I didn't have a clean answer to that. I had the fourteen-day review period, which was concrete, and I had Sonn's specific concern about high-intensity compressed stress as the cascade trigger, which was also concrete, and I had the pattern recognition telling me that a research facility designed around a different species' integration data was going to optimize for the data it had rather than the variable it didn't.

Those were the things I was working from. They were enough to be certain about the decision. They weren't enough to be certain I was right.

I thought about what Vasht had given up to keep me in the field this long, and about what it would cost her if Palleth went to the review board and they reclassified the contract, and about whether there was a version of this where I made it easier for her to argue what she was already arguing without giving up the thing that made the argument worth having, which was the operational independence that was producing the results she was using as evidence.

There probably was. It probably required something I wasn't doing yet, which was giving Command something they wanted that I could actually afford to give them, so they felt like they'd gotten something from the exchange rather than just being told no by a civilian with a signed contract.

I'd think about what that looked like. Not tonight, but before Palleth called back with a legal officer on the line.

The perimeter rotation changed outside, boots on the approach path, the brief exchange of status between the outgoing and incoming walkers. The new walker was one of the original soldiers, the one who'd learned the drainage channel coverage in the four months before I arrived. He'd be rotating out in six days.

Six days. Long enough for the replacement soldiers to get the briefing file integrated and run one perimeter rotation with someone who knew the terrain. Not long enough to learn the terrain the way the original soldiers knew it, which was through months of it going wrong in specific ways.

The Aeluun interface ran its quiet frequency in the bone behind my right ear. The replacement briefing file was sitting in the queue, ready to be read. The dead angle at the north corridor primary position was documented, corrected, marked for priority review.

I'd done what I could do tonight.

The defensive geometry for the eastern choke point was still incomplete, the part covering the elevated rail line approach that Eshet's probing contacts had been using as cover. I pulled up the next file and started drafting the notation for the rail line's sight-line constraints, specifically the section where the overhead structure created a coverage gap at ground level that the standard firing position didn't account for.

The notation needed to be simple enough that a replacement soldier reading it cold could apply it in the first thirty seconds of a contact. I wrote it three ways and picked the simplest one, which was also the one that required the most confidence in the reader's ability to translate a description into a firing arc without having seen the terrain.

I added a coordinate diagram. It took eight minutes to draw accurately. Then it was right, and simple enough, and I submitted it.

The equipment bay was quiet except for the array's cycling self-diagnostic and the integration's background hum. Outside, the grey afternoon light of the Caleth Corridor was doing whatever it did when no one was watching it, which was the same thing it always did.

I had four more notation sections to finish before the replacement briefing package was complete. I opened the next one and got to work.