Durrik's Assessment

I woke four hours after I had closed my eyes, which was the pattern now whether I wanted it to be or not. The hub core still hummed. The relay panel still ran its steady handshake with the convoy's position in the corridor. The tone in my right ear had settled at the new baseline during the sleep interval and was running clean, which Sonn had said was an indicator that the system was cycling through a rest state even if the rest state looked different from what rest used to mean.

Denavi was still asleep. Rovan was awake and had moved to the relay panel, monitoring the perimeter feed with the methodical patience of someone who had learned to fill the quiet hours with useful occupation rather than waiting through them.

Hetch was not in the hub.

I checked the perimeter status on the data pad. Four Compact fireteams, two from the convoy's attached force, rotating positions every ninety minutes. No contact. The sector's northeast terrain held its quiet geography. The extension ran its monitoring at the depleted range and returned nothing that was not Compact-positive.

Eshet was out there somewhere beyond that range, and she was not gone. She was thinking.

I picked up the data pad and went looking for Durrik.

He was at the east access, standing at the node's exterior in the early light, which was grey and thin and made the industrial terrain look like it had been assembled from different materials than it actually had. The corrugated casing on the logistics unit to the east. The supply duct routing along the north wall. The damage to the north perimeter's emplacements where the gifted Dominion soldiers had pushed through twelve hours ago. All of it greyish in the pre-full-light, functional and ugly in the way of infrastructure built for use rather than anything else.

He heard me behind him without turning. "Diagnostic."

"Morning." I stood beside him and looked at the same terrain. "The diagnostic is this morning, after I eat something."

"Sonn responded at 0312."

"I know. I saw the message."

He turned his head enough to look at me. "And?"

"He wants to run the full assessment before he gives me a written analysis of the third candidate's profile. He says it's connected to my current state, which means he thinks whatever the third candidate's profile indicates will interact with the extended system in ways he can't model without current baseline data."

Durrik turned back to the terrain. "So the diagnostic is not optional."

"It was not optional before Sonn's message."

The grey light shifted slightly. The sun was somewhere behind the corridor's northeast terrain feature, not visible yet but changing the quality of everything. A supply duct running along the north wall had a section of casing that was not seated correctly, probably from the assault's second hour when two rounds had hit the exterior structure within thirty meters of that position. It would need to be reseated before the node's logistics function could run at full capacity. That was a maintenance item for the incoming Compact technical team, not for me.

I catalogued it anyway. The habit was complete at this point.

"You did something in the gap yesterday," Durrik said.

I waited.

"I have been training people for eleven years," he said. "I have trained Solvari line soldiers and Chethari specialists and two Navari scouts who were the most spatially aware combatants I have ever assessed. I have never trained a human being. I did not know what that would look like and I told Vasht as much when she brought me into this." He put his hands on the exterior casing of the access frame, not gripping it, just resting them there. "What you did in the gap is the kind of decision that saves a unit and gets the person who made it killed in the same motion. You understand that."

"Yes."

"It worked because of the predictive extension. If the extension had not given you a read on the gifted soldier's position through the gap, you would have been in a confined space with a Dominion-gifted combatant at close range with your pattern recognition partially blocked by Eshet's interference, and the outcome of that would have been specific and not in your favor."

"I know."

"I am not telling you it was the wrong call," he said. "The gap needed to close and you were the only person who could close it. I am telling you that the decision was correct by a narrower margin than the outcome suggests."

I considered that. "Three of the four people on the other side of the gap read as Dominion standard infantry. The gifted soldier's position read at the limit of the extension's range through Eshet's interference, which meant partial data, but partial data was enough to route through rather than into. The math was close. I knew the math was close when I went through."

Durrik looked at me then with the full direct attention he used when he was running an assessment. Not evaluating whether I was lying. Evaluating whether I understood the specific thing he was pointing at.

"That is what I am talking about," he said.

We stood there in the grey light for a moment. The corrugated casing on the logistics unit had a hairline fracture along its upper seam that would need to be addressed as well. The technical team was going to have a full morning.

"You are not a soldier," Durrik said. "I want to say that with precision, because what I mean by it is not a criticism. You do not move like a soldier, you do not make decisions like a soldier, and the tactical framework you operate from is not a military framework. You have absorbed the fundamentals well enough that you can apply them when the situation demands it, and your natural instincts fill gaps that the fundamentals do not cover. But what you are is something else. I do not have a name for it that fits the categories I was trained in."

"Vasht called it something last night."

"She is not wrong. But her categories are also the wrong categories." He moved back from the access frame and turned to face the hub interior. "What happened in the node's third hour, when you identified Eshet's six-second cycle and passed it to Denavi in two words that she acted on correctly and immediately: that is not a trained behavior. That is a functional relationship built on two weeks of shared operational experience and Denavi's four months of knowing this terrain, and you compressed all of that into a two-word communication that carried everything it needed to carry. A soldier trained in standard doctrine would have given a four-sentence brief and lost the timing."

I had not thought about the exchange in those terms. He was right about it. "Denavi did the execution. I just identified the pattern."

"Yes," Durrik said. "That is the correct division of function. You knew what you had, you knew what she had, and you put them together correctly under full combat load." He paused. "That is not something I can train. That is something I saw in the replay and recognized as the reason the assault broke."

The grey light had shifted another degree. The sun was making progress somewhere beyond the northeast terrain feature.

"Vasht said the same thing differently last night," I said. "She said the Compact does not have a category for what I am operationally and that this is administratively inconvenient and tactically significant."

"Vasht is diplomatic."

"She is when she needs to be."

He almost smiled. Not quite. "What are you going to do about the candidates?"

There it was. The question he had been building toward since I'd walked up behind him.

"I do not know yet," I said.

"That is not an answer."

"I know."

He looked at me for a long moment with the patience that was one of his few modes of expression beyond professional directness, the patience he used when he had said the useful thing and was waiting for the person in front of him to catch up to it or not. "The candidates will need someone who understands what the first seventy-two hours of integration actually feels like, from inside the experience rather than from Sonn's briefing documents. That is one thing. They will also need someone who understands what the operational use of the system looks like in a real engagement, not a controlled testing environment. That is a second thing. The Compact has nobody who can provide both. Vasht can provide neither. Sonn can provide the technical brief but cannot speak to the operational reality." He let that sit. "You can provide both."

"I am aware of the logic."

"I am not asking whether you are aware of the logic. I am asking what you are going to do."

The thing about Durrik was that his questions were always genuine requests for information. He did not ask questions rhetorically. He did not ask questions to make a point he had already decided to make. When he asked what I was going to do, he wanted the actual answer because the actual answer affected his planning, which was concrete and near-term and built on accurate information.

"I am going to go to Earth," I said. "Or wherever the contact needs to happen. I am going to be part of the contact because Vasht is right that a Solvari crew pulling three people off their routines and explaining the galaxy to them through a commander with short sentences and no apologies is going to go worse than it went for me, which is saying something." I stopped. "And because the mill worker is forty miles from Cocke County and the terrain there is ridge country and whoever is going to explain to that man what the integration feels like when it runs wrong is going to need to be someone he does not immediately want to throw out a window."

Durrik was quiet for a moment. "And the other two."

"The other two need the same thing. Different specifics."

"The nineteen-year-old."

"Sonn's analysis first. Then I will know what the nineteen-year-old needs."

He nodded. It was the nod of someone who had received the information he was looking for and was filing it against his operational planning. Not approval, not satisfaction. Assessment completed.

"The extraction protocols for Earth contact are not yours to design," he said. "Vasht has a team. The team has procedures. Your role in the contact will be defined by what you bring to it that the team cannot provide, which is the operational experience and the integration knowledge, and you will stay in that role rather than attempting to run the contact as though it is your operation."

"I know how the Compact works."

"You know how the Compact works when you can negotiate around it. This is a different situation. Three civilians with no context and a contact window measured in weeks and a Dominion investigation team already moving. There is no negotiation room."

He was not wrong about that either. I had been through the contact window math twice since Vasht's communication and the math did not improve with repetition. Three to four weeks. The Dominion team moving toward Earth was operating with the urgency of an organization that had just watched its sector strategy for the Caleth Corridor fail in part because of what a compatible human could do after six weeks of operational use. They would move faster than they would have moved before yesterday.

"I am not going to try to run the contact," I said. "I am going to be useful in the contact. There's a difference."

"Make sure you remember it when you are there."

"Is that a concern?"

He looked at me with the flat professional assessment that was his version of humor. "Your tendency to reinterpret the scope of your involvement based on your judgment of what the situation requires has been well-documented since approximately day four of your training program. I am noting it as a variable to be managed rather than a character flaw requiring correction."

"You told Vasht that. At the debrief after the first live-fire simulation."

"I tell Vasht most things worth noting. She is the commander. That is her function."

The sun had cleared the northeast terrain feature. The grey light resolved into actual morning, the kind of light that showed the damage to the north perimeter in specific detail: scorch marks on the emplacement casing, a section of outer paneling displaced by the breach entry. Hetch's position from the third hour of the assault was visible from here, the spot where he had covered the interior line before the gifted Dominion soldier had come through the gap. The gap itself was maybe eight meters from where I was standing. The sightlines from the gap to the hub core were exactly as I had read them when I went through.

The math had been close.

"In the gap," I said. "When the extension was running at full load and the interference from Eshet's signal was at its worst, I had about a second and a half of predictive data on the gifted soldier's position. Less than the full two-to-four second window the extension normally provides. The partial data read the gifted soldier moving into the gap's interior at a line that put its position one step behind where I needed to be to cut the angle." I paused. "It was enough. But I want you to know the margin."

Durrik looked at me for a moment. "A second and a half."

"At close range through partial interference. The position read was accurate. The execution margin was narrow."

"How narrow."

"I did not have a second attempt available," I said. "That is the answer."

He was quiet. Not the tactical assessment quiet, something different. The quiet of someone who has received information that fills in a gap in what they understood about an event and is adjusting the adjusted picture.

"The extension's range and accuracy under interference conditions," he said. "Is that something Sonn can address in the diagnostic?"

"I put it in the message last night. He flagged it in his response. It's in the assessment queue."

"Good." He turned toward the hub interior. "Eat something. Run the diagnostic. Whatever Sonn's analysis says about the third candidate, I want a summary before you send a response to Vasht about the contact protocols. I want to know what you are committing to before you commit to it."

I followed him inside. "You are going to be at the diagnostic."

"I am going to be at the diagnostic," he confirmed, without making it a question of whether that was acceptable.

It was acceptable. Durrik at a diagnostic was the same as Durrik at an after-action review or a tactical planning session: he asked the questions that needed to be asked and he did not ask the ones that did not and he received the information without softening it. Sonn was more comfortable in that environment than in an environment where Durrik's directness needed to be translated for someone who processed it as aggression rather than precision.

Inside the hub core, Rovan had a field ration open on the equipment ledge and was working through it with the systematic focus of someone refueling rather than eating. Denavi was awake, sitting with her back to the south wall and her data pad in her hands, running through what I assumed were the perimeter feed logs from the overnight rotation. She glanced up when we came back in.

"Anything from the northeast?"

"Clean to extension range," I said. "Nothing on the convoy perimeter sensors either."

She nodded and went back to the logs. Her forearm had a fresh bandage over the cut, which meant she had redressed it during the night at some point without making anything of it. The laceration was moderate, manageable, and she had managed it.

I found a field ration in the supply section that had survived the assault and sat down on the equipment ledge near Rovan and ate it without examining it too closely. The system had specific nutritional requirements that Sonn had outlined three weeks ago, based on the integration's metabolic load, and field rations met most of them adequately enough that I had stopped thinking about food as anything other than an operational input.

That was one of the small changes I had filed and not examined: the way appetite had shifted from something with preferences to something with requirements. Not a cost. Just a change.

Durrik sat across the hub with a data pad and worked through what I assumed was his observational notes from the engagement, the kind of documentation he maintained as a matter of professional habit regardless of whether anyone had asked for it. He had been filing observational records on my development since the first day on the training deck, most of which he had shared with Vasht and some of which I suspected he had shared with no one.

After the ration, I pulled up the diagnostic interface on the data pad and opened the Sonn link.

Sonn responded within seconds, which meant they were already at their station on the research vessel, wherever it was in the corridor's operational zone. The link quality was good. Better than the secure relay Vasht used, which ran through the convoy's comm infrastructure.

"The system has settled," Sonn said, without preamble. Their voice was the same as it always was: precise, measured, pausing in the places that carried weight. "The sustained load from the engagement has resolved into an integration state that I am still compiling notation on, but the preliminary readings suggest that the predictive extension is not in a destabilizing configuration. The nosebleed response that occurred during the engagement was a pressure-release mechanism rather than a cascade indicator. That is the good news."

"What is the other news."

"The new baseline is higher than the pre-engagement baseline. The system ran at maximum load for approximately three hours and when it settled it did not settle back to the previous operating level. It settled higher. This is consistent with the Thuvari theoretical model for integration under sustained extreme stress, which suggests that the system uses high-load periods to permanently integrate new structural pathways. You are more capable than you were forty-eight hours ago." A pause. "The cost accounting for that capability increase includes the tonal shift in your right ear, which I expect has moved to a slightly higher frequency than before the engagement."

"Yes."

"That will be the permanent baseline now. I want to confirm it in the diagnostic."

Durrik, from across the hub, had set the data pad down and was listening. He did not comment.

"The third candidate," I said.

"Yes. The profile indicates a stress-response architecture that is significantly more reactive than yours was at initial contact. The Thuvari assessor's flag was correct, and I understand why they used careful language. This candidate's integration, under operational stress conditions within the first six weeks, will develop at a rate I estimate at approximately twice the rate yours did." Sonn paused. "This is not inherently a problem. It becomes a problem if the first six weeks include sustained extreme stress without someone present who can read the integration state in real time and identify the early indicators of cascade approach before the candidate experiences them."

"Someone who can read the integration signal."

"Yes."

I knew what the system signal sounded like. I had been hearing it for weeks in my right ear, and before that I had learned to read it through Sonn's diagnostic readouts and my own sensory reporting. The specific frequency and pattern of a system running clean versus a system running hot versus a system approaching a ceiling were distinctions I had developed the way you develop any working knowledge: through repeated exposure until the distinction was automatic.

"I can do that," I said.

"I know," Sonn said. "I have been thinking about this since I read the file. I want you to understand the specific responsibility: this candidate's profile suggests that without someone present who understands what they are experiencing from the inside, the first six weeks of operational development will be the highest-risk period in the entire integration arc. The Compact's standard medical monitoring does not have the granularity to catch early cascade indicators in a profile this reactive. I can monitor remotely, but there is a response-time gap between what I observe in the readings and what you can observe in person."

"How big a gap."

"Under optimistic conditions: six minutes. Under real conditions, with communication relay latency through the sector infrastructure: twelve to fifteen."

Twelve to fifteen minutes was a gap that mattered. The cascade failure that Sonn had described in Chapter 10, the one that had taken the first Thuvari subject and left the second in a condition the records talked carefully around: both of those had moved fast when they moved. Fast enough that twelve to fifteen minutes was a resolution that arrived after the problem had already become a different kind of problem.

I put the data pad on the ledge and looked at the hub core's relay panel. The handshake with the convoy ran its steady frequency. Outside, the technical team that had arrived with the convoy's second element was already working on the supply duct, which I could hear if I filtered for it through the hub's ambient sound.

"The full diagnostic," I said. "Let's run it."

Sonn walked me through the diagnostic protocol while Durrik sat across the hub and watched the readouts on his own data pad, which I had given him access to two weeks ago after he had asked a series of technically specific questions about the integration that I had answered verbally and then recognized that verbal answers were less efficient than direct readout access. He reviewed the data the way he reviewed any operational information: without editorializing it in real time, building his assessment through the full picture rather than responding to individual data points.

The diagnostic took forty minutes. It was less physically demanding than the first calibration had been, or than the integration sessions in the early weeks. The system had a stable enough architecture now that the diagnostic read against a known structure rather than mapping an unknown one. Sonn's commentary ran throughout: the tonal frequency confirmation, the new baseline capabilities registered against the pre-engagement baseline, the predictive extension's range and accuracy parameters under standard conditions, and the specific note about Eshet's signal interference that I had flagged in my overnight message.

That last item took Sonn longer to assess. The interference from a dense integration signature was not well-documented in the Thuvari records because no Thuvari had ever tried to predictively model a Vorath-line Aeluun user in a combat context. Sonn's analysis was built from first principles and the data the diagnostic pulled from the engagement's recorded integration readings, which the system had logged while it was running.

"The interference ceiling is fixed at the current level of your predictive extension's sensitivity," Sonn said. "An eleven-year Vorath-line integration will produce sufficient signal density to reduce your accuracy window from two to four seconds to one to two seconds at close range. Beyond fifty meters, the interference reduces further. Within twenty meters, the window is less than a second." A pause. "I want to be honest with you: this is a structural limitation. Eshet's integration will continue to develop. Your integration will continue to develop. Whether the gap between your current sensitivity and her signal density widens or narrows over time is not something I can model without knowing the development trajectories, and I do not know enough about her trajectory to estimate."

"What I know is that she knows I can read her now," I said. "She pulled the assault when she recognized her coordination had been identified. She will adjust."

"Yes," Sonn said. "She will adjust."

I thought about the model the predictive extension had built of Eshet's signal over the seventeen hours of the engagement, the background process that was still running against the stored data. Building detail from the recorded readings even now, when the engagement was over and the tactical usefulness of the model was downstream. The system was thorough in ways that went past my conscious direction.

"The model the extension built of her signal during the engagement," I said. "Is it usable in a future engagement as a baseline, or does it degrade against real-time variation?"

Sonn was quiet for a moment. This was one of the questions that landed in territory the Thuvari records did not cover. "I do not know," they said. "I will add it to the assessment queue and review the engagement data. It is a good question."

"It is a necessary question," I said.

After the diagnostic, Durrik put the data pad down and looked at the hub's east wall for a moment before he spoke.

"The candidates," he said. "Vasht's contact protocols put a Compact team on the ground for initial extraction. Where do you want to be in that sequence?"

"Not the extraction," I said. "The extraction is a Compact operation with Compact protocols and the team is trained for it. Where I want to be is in the first forty-eight hours after extraction, before the integration decision is made, because the decision to touch the device needs to be made by someone who has actual information about what that decision entails, and that briefing is not something a Compact officer can give."

Durrik considered that. "Vasht will have thoughts about the forty-eight hour window."

"Vasht's thoughts about the forty-eight hour window are going to have to accommodate the fact that I am the only person in the Compact who can tell those three people what the integration actually does to you, from inside the experience rather than from a technical file."

"I know," Durrik said. "I am telling you Vasht will have thoughts so that you are not surprised when she does and so that you do not respond to her thoughts as though they are obstructions rather than coordination requirements."

I took that for what it was. "I will coordinate."

"Good." He stood up from the equipment ledge and stretched his shoulders in the careful way of someone whose back was not entirely right after a night of field conditions. "When Sonn's written analysis is ready, brief me before you send the response to Vasht. I want to know what you are agreeing to."

"You already know what I am agreeing to."

"I want to know the specifics." He moved toward the east access. "Greel's recovery debrief is at 0900 via the medical team's relay. I want you on that link."

"I will be on it."

He stopped at the east access frame. This was the position he had used when he had a final thing to say that he had not worked through yet and needed the frame there while he found it. I had seen him use the same position four times since the assault began.

"The farm," he said. "Forty miles from Cocke County."

I waited.

"You said it is not a personal connection."

"It is not a personal connection. I do not know the man. I know the geography."

"Yes," Durrik said. "And you know what it is to be pulled out of that geography without a framework for understanding what comes next, and you know what having a framework would have changed in the first seventy-two hours, and you know that the gap between the briefing you received and the reality you encountered was significant in specific ways that had operational consequences."

He was not wrong.

"That is the useful thing," I said. "Not the geography."

"I know," he said. "I am noting that you know the useful thing and what the useful thing is and why it matters. That is not the same as a personal connection and it is not nothing."

He went out through the east access.

The hub core hummed. Rovan was back at the relay panel. Denavi had moved to the equipment ledge and was working through a section of her after-action notes with the focused quiet of someone who processed events by documenting them with precision. The diagnostic readings were still open on my data pad, the new baseline numbers sitting in the interface fields in the plain numeric language of the system's self-reporting.

Higher than the pre-engagement baseline. The system had used the seventeen hours of sustained extreme load to build new permanent structure and it had settled at that structure and it was not going to step back from it.

The tone in my right ear ran at the new frequency.

I thought about the three candidates and the contact window and Sonn's assessment of the third profile's development rate under operational stress and the twelve-to-fifteen minute response gap between Sonn's remote monitoring and my ability to read the integration state in person. I thought about the mill worker with the ridge country behind his residential coordinates and forty miles of Tennessee geography between him and a county where I knew which tree stands were mine and which were the neighbor's.

I did not think about what came after the contact, because that was downstream and there were enough immediate problems in the near term to fill the operational space completely.

What I had was this: a diagnostic that confirmed my integration was stable and developed and running at a permanent new baseline. A Sonn analysis incoming that would give me specifics on what the third candidate needed from the first seventy-two hours that no Compact briefing document covered. A debrief with Greel's medical team at 0900. A secure link to Vasht that was waiting for my response on the contact protocol question.

And an Aeluun integration running in the background of everything, the predictive extension processing the stored engagement data with the patient thoroughness of a system that did not stop working when I did.

Denavi looked up from her notes. "The third candidate."

I looked at her.

"Sonn flagged the profile in your message," she said. "I was on the relay when you sent it. I did not read the content, but I read the flag." She held the data pad at a slight angle, the habit she had when she was deciding how far to go with a line of inquiry. "The nineteen-year-old."

"Yes."

"Fast development," she said. It was not a question.

"Sonn thinks twice my rate under operational stress."

She was quiet for a moment. "You're going there. To Earth."

"Yes."

She nodded once, the small decisive nod that she used when she had received the information she was looking for and was updating her operational picture accordingly. "Then you need Sonn's analysis and a clear framework for what the contact window looks like on your end before you talk to Vasht about the protocol. Because if you go in without a clear ask, Vasht will fill the gap with what the Compact's standard contact procedure allows for, and the standard procedure does not account for someone who can read the integration signal in real time."

"I know."

"I am not telling you something you do not know," she said. "I am telling you to have the ask ready before the conversation. So it is a specific request rather than a general position, because Vasht responds better to specific requests than general positions."

Four months of working inside the Compact's operational structure while the Compact made decisions about a unit that had been losing engagements had given Denavi a practical education in how to get what you needed from the people above you without making the ask into a confrontation. It was a different skill from my tendency to find the leverage point and apply it directly, and it was frequently more effective.

"The specific ask," I said.

"First forty-eight hours, in person, with direct integration monitoring authority. Specific to the third candidate's profile. Give Sonn's analysis as the technical basis. Make it narrow enough that it's not a general claim on the contact operation and broad enough that it covers what actually needs covering."

I looked at her for a moment. "When did you read Sonn's message?"

"I did not read Sonn's message. I read the flag and I know how Sonn thinks from three weeks of watching you two work through the integration diagnostics on the relay. And I know how Vasht thinks from four months of receiving directives from the Compact structure she represents." She went back to her notes. "Have the ask ready."

The hub core hummed. The tone in my right ear ran at the new baseline.

I pulled up the message interface and started drafting the specific ask.