The Gap Between Training and Real

Durrik pulled me off the training deck at 0700 on a Tuesday, which I knew only because I'd started marking time by the station's light cycle rather than any clock. He didn't explain where we were going until we were in the corridor, and even then he kept it short.

"Live-fire environment," he said. "Opposition personnel. Two Compact soldiers, both infantry-qualified. You'll have a standard-issue Compact sidearm and a short-range comm unit running Greel's six-second protocol."

"Who are the opposition."

"Trained personnel. Not enhanced." He glanced over, brief. "Don't shoot them with intent to permanently damage. Rounds are marked, not live. The environment will score hits."

The simulation facility was four levels down from the training deck, through a section of the station I hadn't been authorized to access before. The corridor walls gave way to something that looked less like a ship interior and more like the inside of an unfinished industrial building: exposed conduit, concrete-analogue paneling, variable lighting rigs mounted at ceiling level that could replicate anything from full illumination to near-dark. The space was about sixty meters across and irregular, broken up by partial walls and equipment bays and one narrow passage that ran the length of the central section like a gap between close-set fence posts.

Two soldiers were already there when we arrived. One was Solvari, taller than Vasht, with the kind of physical economy in her movements that said she'd been doing close-quarters work long enough to stop thinking about it. The other was Navari, shorter, with four arms folded in a configuration I'd come to recognize as standard rest posture rather than anything emotional. Neither of them introduced themselves and Durrik didn't introduce them. That was information too: this wasn't a meet-and-greet exercise.

Durrik handed me the sidearm. It was lighter than I expected, grip calibrated for a hand shape that was close to human but not quite, which meant I'd be compensating slightly in the draw. I checked the chamber, checked the safety, checked my sightlines in the space out of habit.

"Objective," Durrik said. "You are the defensive element. Opposition will attempt to move a marker object from the east end of the environment to the west extraction point within twelve minutes. You will prevent this. Standard comm protocol applies. Any questions."

"How are they running. Together or split."

"Your assessment to make."

I looked at the space. The narrow central passage was the obvious route: fastest line between east and west. Which meant anyone running opposition against a solo defender with the passage available would probably split, one moving as bait through the obvious route while the other worked the longer way around the exterior.

"Understood," I said.

Durrik walked to an elevated observation platform at the room's north end, which had a direct sightline to the whole environment. I marked his position and moved.

The comm unit went live with a two-second tone and the exercise started.

I didn't go to the obvious defensive position, which would have been the western end of the central passage where I could cover the extraction point directly. I moved instead to a partial wall about two-thirds of the way back from the east end, which gave me a sightline down the passage and also a partial view of the exterior left route, and which had a junction point where two equipment bays created a ninety-degree corner I could use if I needed to break contact and reposition.

For forty seconds nothing moved. I counted the air-recycling interval out of habit, the same forty-nine-second cycle as every other Solvari installation I'd been in. The Aeluun integration ran its background inventory quietly, no active pattern recognition yet because there was no pattern to read.

Then both soldiers moved at once, which confirmed the split. The Solvari came through the central passage at a pace that was fast but controlled, not a sprint, which meant she was bait who knew she was bait and was doing it professionally. The Navari went left, exterior route, which I could track by sound through the equipment bay wall: four-limbed movement has a different rhythm than two-limbed movement, and the Navari's stride pattern put him at roughly the midpoint of the exterior route.

I let the Solvari come twelve meters into the passage before I fired twice from behind the partial wall. Both rounds scored on her center mass according to the environment's auditory feedback, two soft tones that meant hits. She stopped, moved to a side wall, called her status on the comm. Hit, compromised, still functional in the simulation's parameters, which meant she'd keep moving but slowly.

The comm cycle ticked. Six seconds. I checked in, gave my position code, moved before the transmission was finished.

The Navari was coming around the exterior left at a pace that expected me to still be behind that partial wall. I wasn't. I'd moved to the equipment bay junction, which put me at the edge of his approach vector rather than in front of it, and when he came around the bay's corner I had a clean sightline at under four meters and he had an angle that required him to pivot before he could acquire me.

He pivoted fast, faster than I'd estimated. One of the four arms got a shot off that scored on my left shoulder before I scored two center-mass hits on him.

Both hits registered. He stopped, called status.

The Solvari had used the exchange to cover the last section of the passage and was now five meters from the extraction point. I had a compromised shoulder in the simulation's parameters and a six-second comm cycle that was ticking toward the next check-in.

The extraction point was the west end. The marker object was still in the Solvari's hands. She was moving deliberately slow to let the comm cycle complete before she made the final push, which was tactically correct because the check-in would tell her where I was.

I didn't check in.

Instead I moved backward, which looked wrong from the extraction-point perspective: I went deeper into the environment rather than toward the threat. Through a secondary bay, around a support column, through the same narrow passage but from the far end, which put me behind the extraction point rather than in front of it.

The Solvari cleared the passage and moved to the extraction point and stopped.

I was already there. I had the sightline. She was three meters away looking at a position I wasn't in.

"Hit," I said, without the comm unit, just direct. It wasn't within the simulation parameters but it was accurate.

She stopped. Looked at me. Said something in Solvari that the station's translation layer rendered as an expression of professional surprise that also contained mild profanity.

Durrik was silent on the observation platform for a moment. Then: "Reset."

We ran it twice more. The second run, both soldiers adapted: they anticipated the backward movement and set a block on the secondary bay approach. I didn't get behind the extraction point. Instead I went high, using the equipment bay shelving as a ladder to a position that wasn't in anyone's assessment of the space as a defensive surface, and scored on the Solvari from above while the Navari was covering the approach routes at ground level.

Third run, they blocked high too. I didn't find a clean route and by minute eleven the Solvari reached the extraction point with the marker. Simulation over.

Durrik came down from the observation platform while the two soldiers reset the environment. He stood in the center of the space with his hands behind his back and looked at me with the expression he used when he was doing arithmetic.

"Communication and unit integration," he said. "You dropped a check-in in run one. You dropped two in run two. In a real engagement with a multi-element unit, those dropped check-ins put your teammates in positions based on incomplete information."

"Acknowledged."

"Positioning and mobility: above what I projected." He said this the way he said everything operational, no warmth in it, just the fact. "You read the environment faster than trained opposition personnel who had the full layout in advance."

"They told you their routes?"

"Standard for opposition-force briefings. They knew the environment. You didn't." He looked at the narrow passage, then at the equipment bay shelving I'd climbed. "Where did you learn to read ground like that."

It wasn't a compliment, exactly. It was a question with the specific texture of someone who had watched a skill operate and wanted to know its origin. The kind of question Durrik asked when he was filing information rather than evaluating character.

"My grandfather," I said. "He taught me to hunt."

The words came out flat, which was how they were supposed to come out, and Durrik heard the flatness and filed it the same way he filed the answer. He didn't push on it and I didn't expand on it, and we moved on to the debrief.

Grandfather had been the one who taught me that terrain doesn't care about the plan you made for it. You had to look at what was actually there: where the ground dipped, where the sight lines opened, where the wind came from in the morning versus the afternoon. He'd spent forty years reading Cocke County's ridges the way some people read text, automatically, without conscious effort, until the landscape's logic was just part of how he processed being outside.

I'd inherited the habit without knowing it was unusual until Durrik pointed it out. It was the same thing that made the backward movement make sense in run one: not retreat, repositioning. Not losing ground, choosing different ground. The deer taught you that. You didn't push a deer into a corner because a deer in a corner was a deer that did something unexpected. You moved with the terrain until the terrain gave you the moment you wanted.

I didn't say any of this to Durrik. He'd gotten the relevant part of the information, which was the source, and the rest was mine.

The debrief ran forty minutes. Durrik used the environment's scoring system to walk through each engagement in the order it happened, stopping at the decision points to ask what I'd been tracking and why. The dropped comm check-ins were the longest section. He made me walk through the exact moment in run one when I'd chosen to move instead of transmit, and then made me articulate why that had felt like the right decision, and then told me precisely why it was wrong in a unit context regardless of whether it had worked.

"In a solo exercise, your judgment is the only one at risk," he said. "In a unit, a dropped check-in tells every other element that either you're incapacitated or you've gone dark for a reason, and they have to make decisions based on that uncertainty. You put Greel's six people in a position where they're operating on incomplete information at the worst possible moment."

"Understood."

"You said that already."

"Because I understood it the first time." I looked at him. "I dropped the check-in because transmitting would have given away my position to the Navari who was on an intercept approach. I made a tactical decision with incomplete unit doctrine. The fix is internalizing when the check-in costs more than the dropped information."

Durrik was quiet for a moment. "Correct," he said. "Which is not the same as always transmitting."

"No."

"There is a decision matrix for this in Greel's modified protocol. I'll add it to this afternoon's drill sequence." He looked at the environment again, scanning it the way he scanned everything, looking for the thing he hadn't assessed yet. "The ambush on run one. Walk me through the calculation."

I walked him through it: the split confirmation, the passage bait, the Navari's position from sound alone, the geometry of the junction point. He listened without interrupting and when I finished he nodded once.

"You calculated the Navari's position from movement sound."

"Four-limbed stride pattern through the equipment bay wall. Rhythm is different."

"That is not a skill included in any training module I run."

"No."

"Is it the integration."

I thought about it honestly. The Aeluun pattern recognition had been running background inventory the whole exercise, doing what it always did: tracking positional variables, cataloguing movement signatures, the low-level hum of the system reading the environment through my sensory input. Whether the sound calculation was me or the integration amplifying my spatial awareness was not a clean distinction. The two had been operating together long enough that separating them required deliberate attention.

"Partly," I said. "Partly I've been listening to how things move in limited visibility since I was twelve years old."

Durrik nodded again. "Useful," he said, which from him was the equivalent of an enthusiastic endorsement. He turned toward the exit corridor. "Run two worked until the opposition adapted. Run three didn't. What's the lesson."

"A trick works once. Doctrine works repeatedly."

"Close." He pushed open the corridor door. "A trick works once against opposition that doesn't adapt. Against opposition that adapts, a trick is how you get the first engagement while you're still developing doctrine." He let the door close behind him. "You don't have doctrine yet. You have instincts. The next several weeks are converting instincts into doctrine without destroying the instincts. That is a more difficult process than it sounds."

It sounded fairly difficult already. I didn't say that.

We went back up to the training deck and ran the six-second comm protocol for two hours in various simulated environmental contexts, Durrik calling position-change scenarios and me transmitting within the cycle window regardless of what the simulated tactical situation was doing. He interrupted the drill once to make a correction and zero times after that.

At 1400 he called a break and we sat on opposite sides of a folding table in the training deck's equipment section with two containers of the station's food processor output, which had improved marginally since the first week but was still identifiable primarily by texture rather than taste.

"Tomorrow we run the live environment again," he said. "Same opposition, different layout. I want to see whether the ground-reading transfers to an unfamiliar configuration or whether it was environment-specific."

"It'll transfer."

He looked at me across the table. "Confident."

"It's not the specific environment I'm reading. It's the geometry. Change the furniture, the geometry is still there."

He ate whatever the food processor had provided, which had the texture of something that had once been grain, and was quiet for a moment. "In three days," he said, "I'm scheduling you for a full exercise with four-element opposition. Multiple coordination variables, pressure on the comm cycle, contested objectives."

"What's the objective structure."

"Acquisition and extraction. You're the extraction element. Your role is to keep the acquisition team alive long enough to reach the extraction point." He looked at me. "This is close to the actual role you'll be running in the Caleth Corridor. Not a simplified version. A scaled version."

The Caleth Corridor again. Greel's name had been in the debrief materials twice this week, and now the corridor by name. The geography of what came next was sharpening.

"What's Greel like," I said.

It wasn't the kind of question I usually asked. I asked operational questions, logistical questions, training questions. Asking about someone's personality was usually the kind of thing I let develop through direct experience rather than advance information. But Greel was going to matter, and I was going to be operating under his tactical decisions in a situation where my margin for error was small, and knowing what I was working with mattered more than maintaining the habit of finding out in person.

Durrik set down his container. Considered the question the way he considered all questions: as something with a correct factual answer rather than an opinion.

"Greel," he said, "has been holding that unit together for four months in attritional engagement conditions that would have fragmented most command structures. He runs the six-second protocol because in his assessment a faster comm cycle is the difference between an ordered retreat and a rout. He has lost soldiers and he names them in his after-action reports, which is not standard Compact protocol and is completely consistent with how he runs everything." He picked up his container again. "He will not treat you as a specialist asset. He will treat you as a member of the unit. If you're useful, you'll know it by what he asks you to do. If you're not, you'll know it by the same measure."

"What does he expect from me specifically."

"I told him what I know and what I assess. He expects the ground-reading. He knows about the pattern recognition." A pause. "He doesn't know what to expect from the integration in live engagement conditions. Neither do I. Neither does Sonn. You'll be the first data point."

First data point. I was aware that was the accurate framing and I'd been operating under that framing since Chapter 3 of however this story was being written about me in some Compact assessment file. The integration was running. The development curve was moving. Nobody had seen a human with compatible biology in a live engagement before, which meant every assumption about how I'd perform was a projection rather than a prediction.

The difference between a projection and a prediction, in practical terms, was the difference between what you thought might happen and what you could bet on. Durrik was being honest about which one we were working with.

"Fair enough," I said.

He nodded. "There is one more thing." He looked at me with the expression he used when information carried weight he wasn't going to explain. "I have scheduled a briefing for Friday. You, Vasht, Sonn, myself. The Caleth Corridor sector situation, current. Not the summary version."

The summary version was what I'd had so far: sector maps, casualty statistics, unit positions, general tactical picture. The current-situation briefing was the step before operational orders. The step before you stopped calling it training and started calling it deployment.

"Friday," I said.

"0800."

I filed it. The food processor's grain-adjacent substance sat in its container and I ate the rest of it without particular attention because the body required fuel regardless of what it tasted like. The integration ran its inventory. The air cycle counted its forty-nine seconds.

The three simulation runs had told me several things, most of which Durrik had already surfaced in the debrief. The comm discipline gap was real and fixable with drilling. The ground-reading was real and had already transferred once to an environment I hadn't seen before and would transfer again. The backward movement, the repositioning to ground that looked like retreat, was the kind of decision that worked in ambush conditions and failed against opposition that had time and space to adapt.

What the exercise hadn't told me, and what no training environment could tell me, was the part Durrik had named directly: first data point. How the integration performed under real fire, with real threat of consequence, with real people depending on the comm cycle running correctly, was information that existed only in the Caleth Corridor.

I thought about Greel running a six-second protocol because it was the difference between a retreat and a rout. About four months of attritional losses. About soldiers whose names went into after-action reports rather than being listed by number.

My grandfather would have understood Greel, I thought. He was the kind of man who kept track of costs by name, too.

I cleared the food container and ran the comm protocol sequence in my head twice, not as drill but as the same pre-check I ran on any tool before I relied on it: making sure the process sat below conscious attention, which was the only level at which it was actually useful. Durrik had said three days to internalize. Two if the pattern recognition did what he thought it would with sequential inputs.

He was right about the two days. I'd known it since the first day of drilling. But there was something useful in the difference between knowing a thing was ready and being certain enough of it to bet on it, and I wanted the extra day for the certainty rather than the knowledge.

Friday. The full sector briefing. The real picture of what was happening in the Caleth Corridor rather than the version calibrated for someone who was still in assessment phase.

Durrik believed I could be operational. He hadn't said this directly, but the Friday briefing was his version of saying it: you scheduled the real briefing for people who were going to use the information, not for test subjects who needed to understand the general shape of the situation. The invitation was the statement.

It wasn't the same as thinking I was ready. He'd said that too, or the equivalent of it, in the gap between his assessments of what I could do and what I hadn't done yet.

But useful and ready weren't the same measure, and the Caleth Corridor didn't have the luxury of waiting for ready. It had what was available, which at the current moment included one human with a Aeluun integration that had outpaced its projections and a ground-reading skill his grandfather had spent thirty years teaching him on ridges in Cocke County, Tennessee.

I went back to the training deck after the break. Durrik ran me through two more hours of the comm cycle in dynamic context, calling variables, making it harder. I dropped one check-in in the first twenty minutes and zero after that. When he dismissed me at 1700, he made no comment on the improvement. He just said he'd see me in the morning and walked out.

Which, from Durrik, was its own kind of statement.

The corridor outside the training deck was the usual Solvari station configuration: functional, spare, lit at a level that was adequate without being generous. I walked it back toward the research section where Sonn had set up permanent monitoring equipment for the integration readings. I hadn't planned to stop there but my feet made the decision before I'd consciously framed the question.

Sonn was at the monitoring station when I pushed open the research bay door, doing something with a data display that required both of their hands and their full attention, and they looked up with the expression they used when they'd been deep in something and were resurfacing.

"Derek." They set down the input stylus. "The live exercise was today."

"Three runs. I'll let Durrik's report tell you the details."

"He'll file it by 1800." Sonn's hands were still. "How did the pattern recognition perform in a dynamic environment."

"Background inventory the whole time. Position tracking. The sound calculation on the Navari's route was partly the system, I think, and partly something I'd have done anyway."

Sonn nodded slowly. "The integration between your baseline spatial processing and the system's positional augmentation has been consolidating," they said. "I have been watching the readings. It is becoming difficult to distinguish which portions of your enhanced situational awareness are system-generated and which are your own amplified."

"Durrik asked me the same question."

"What did you tell him."

"Partly both."

"That is an accurate answer." Sonn looked at the data display, then back at me. "Friday is the sector briefing."

"Durrik told you."

"Vasht told me. I will be attending." They were quiet for a moment, and I could see them deciding whether to say the next thing or hold it. They said it. "Derek. The current integration readings show a stabilization pattern that is consistent with pre-active-development consolidation. The system is preparing to develop further. The next significant capability expansion will likely be triggered by sustained high-stress engagement."

"Like combat."

"Like combat."

I sat down in the research bay's secondary chair, the one without monitoring equipment attached to it. "You're telling me the Caleth Corridor will push the integration forward."

"I am telling you that is what the readings suggest. I cannot tell you what forward means. The Thuvari case files from this stage of development are the most complete we have, and they describe capability expansions in the pattern recognition domain that the subjects reported as qualitatively different from what preceded them." Sonn looked at their hands. "I want you to know what the readings show before the briefing. Before you make the decision with Vasht about the deployment timeline."

"I've already made the decision."

They looked up.

"I agreed to go in Chapter 3," I said. "I've been training since Chapter 6. Durrik has a four-element exercise scheduled for three days from now and a sector briefing Friday. The decision was made."

Sonn was quiet for a moment. "You use 'chapter' the way some people use 'stage' or 'phase.'"

"Force of habit."

"It suggests you are thinking of this as a sequential process."

"Isn't it."

They considered this with the precision they brought to every question. "Yes," they said. "That is a reasonable framing." A pause. "The integration readings are good, Derek. The consolidation is clean. Whatever the Caleth Corridor does to the development curve, you are not approaching the parameters that concerned me in Chapter 10."

I noted they'd used the same framing. I didn't comment on it.

"Get some sleep," I said, standing. "You've been here since 0500 by the look of that display stack."

Sonn looked at the stack of data they'd been working through. "0430," they said, with the expression of someone who had not noticed the time until just now. "I will sleep. Eventually." They picked up the stylus again. "Friday. 0800."

"0800," I said, and went back into the corridor.

The station's light cycle was three hours from its night-phase dimming. I had the comm protocol to drill once more in my quarters before sleep, and the four-element exercise to think through in the abstract, and Friday's briefing sitting at the end of the week like a threshold I was walking toward one day at a time.

Greel ran a six-second cycle because the terrain demanded it. The terrain in the Caleth Corridor had been demanding it for four months. In a few weeks it would be demanding it from me too, and the question of whether my instincts and Durrik's doctrine and Sonn's integrated monitoring added up to something useful enough to justify the cost of what had already been spent was a question the Caleth Corridor would answer.

I ran the comm protocol sequence in my head one more time, checking that it sat where I needed it to sit, below the level of conscious attention, automatic.

It did.