The Withdrawal That Cost
The strike force docked at Kresh-Var with four less vessels than it had launched with.
The bay accepted the survivors without ceremony. Docking clamps engaged. Hatches cycled. Atmosphere equalized. The bay systems registered the returning ships, updated the inventory database, and did not note anywhere that four hull numbers would not appear in the next launch cycle. The station was not designed to acknowledge loss.
Mresh-Kan was the last to disembark.
The hatch cycled open. The bay pressure was Skarreth-standard, warm and dense, the familiar weight of the station’s atmosphere pressing against every surface of the body. The air was the same as before the operation. The bay was the same. The lighting was the same. Nothing had changed to mark the fact that four vessels had entered the Vethrak supply depot’s engagement envelope and three of them had not returned.
Mresh-Kan stood at the hatch for a measured interval. The body registered the transition from ship gravity to station gravity. The ocular recesses adjusted to the bay’s illumination level. Body functions completed their recalibration without conscious direction, performing decades of ingrained practice.
Then Mresh-Kan stepped onto the bay deck and began the walk to the after-action chamber.
The after-action chamber was small, enclosed, designed for assessment without distraction. The panel was already seated. Three senior assessors from the command council’s operational review division. They did not greet Mresh-Kan. Greeting was not part of the protocol. They waited until the body registered as settled at the designated position, then they began.
The panel did not ask what happened in narrative form. They asked specific questions about timeline points, sensor readings, and communications logs. Mresh-Kan answered from memory. The record displayed on the chamber’s layered data surfaces. Where the memory and the record agreed, the panel noted it. Where they diverged, the panel asked again.
The first divergence came at the withdrawal phase.
The record showed a course correction of 0.7 degrees at a specific marker. The panel asked for the basis of the correction. Mresh-Kan answered that the correction was calculated to avoid a known sensor gap. The intelligence pre-brief showed no patrol asset within four hours of the withdrawal vector. The correction put the strike force outside the scheduled sweep’s coverage.
The patrol that intercepted was not in the gap.
The panel reviewed the intercept data. A Fang-class destroyer had altered its patrol route approximately thirty minutes before the withdrawal phase began. The course change was not in response to detection. The Fang had not registered the Skarreth force. It had simply changed its vector for reasons the available data could not explain. The reason was not recorded, and the intercepting vessel had transmitted no indicator of why it was where it was. The Fang entered the outer edge of the withdrawal corridor seventeen seconds before Mresh-Kan’s force transited. The intercept was catastrophic timing.
The panel asked what Mresh-Kan had done when the Fang appeared on the tactical display.
Mresh-Kan described the decision sequence. The withdrawal was already in progress. Countermanding it to attempt coordinated evasion would have required breaking emissions silence, ensuring detection. Maintaining the established vectors gave each vessel an independent probability of passing beneath the Fang’s threshold.
Three of the twelve vessels did not pass beneath.
The panel asked for the names of the three vessels. Mresh-Kan provided them. The panel confirmed the names against the casualty manifest. The three vessel types, complement counts, and equipment value were logged as separate data fields. No comment was attached.
The panel asked whether Mresh-Kan would change the withdrawal vector with the same intelligence. Mresh-Kan answered that the vector was correct for the available data. The patrol’s presence could not have been predicted. The panel accepted this without accepting it as exculpation. The assessment noted that three vessels were lost during withdrawal, which was a failure of the Withdrawal discipline regardless of the predictability of the intercepting force.
The assessment concluded. Mresh-Kan left the chamber.
The return to the bay was not direct. Mresh-Kan passed through station passageways without choosing the shortest route, following the familiar pressure differentials and kilometer markers. The three vessels were on the memorial channel. The data field contained their registrations, their complement lists, and the operational circumstances. Skarreth did not build monuments to the dead. They built better doctrine.
At a general-access terminal in an unoccupied alcove, Mresh-Kan opened a personal channel. The channel was biometric-locked. No one else would access it. Mresh-Kan recorded a single cycle of vocal pattern at the frequency that would have been used to transmit a withdrawal correction. The sound was a compressed click, held at operational length, measured and precise. It was the sound that should have preceded the correction signal. The correction that would have put three vessels on a different vector. The correction that had not been transmitted because there was no time, because the Fang appeared at the wrong moment, because three crews had paid for a gap in the intelligence.
The log was never reviewed. It had no function beyond the act of recording it. The act itself was the content.
Mresh-Kan cycled the terminal and returned to duty.
If you enjoyed this story, you can follow the main story arc in The Exodus Rush, the first book in The Vethrak Requiem series.