Eshet Reads the Intelligence Report
By Murdok · 3,340 words · 15 min read
The intelligence brief arrived at 0317 station time, which was not unusual. Blade-Commander Eshet received most of her actionable material in the hours between midnight and dawn, because that was when the Compact's monitoring systems ran their overnight compression cycles and the data that mattered rose to the surface like oil.
She was already awake. She was almost always already awake at 0317.
The brief came through on the tactical display in her command quarters aboard the Vorath's Certainty, a mid-range operations vessel that had been her working address for the last four years. The quarters were small and organized with the precision of someone who had learned to move fast through confined spaces: nothing on any surface that did not belong there, nothing in the drawer configuration that required looking to find. She had lived in rooms like this for eleven years. She knew where everything was without checking.
She read the brief twice.
The first time for content. The second time for what was missing.
A compatible human, recovered from a Class-IV pre-contact world designated TH-2241 in Compact survey records, Earth in the local language of the dominant species. Biological compatibility score of 93.7, which was the number the brief had buried in the technical appendix, probably because the analyst who assembled the document had not recognized what it meant. Eshet recognized it immediately. She had a 91.2, which was the highest active score in the Dominion's operational database.
She did not react to 93.7 the way a novice would react to it. She set the brief down on the tactical display surface, faced the narrow viewport on the opposite wall where the sector's star field showed its unchanging geography, and asked herself three questions.
The first: how long had the Compact had him?
The brief's sensor data trail answered this partially. The scout vessel's integration signature had first appeared in Compact network traffic approximately six weeks ago, which meant six weeks of whatever development protocol the Compact used for new integrations. Six weeks was early stage, still calibration territory, nothing that would register as a serious tactical variable unless the compatibility score was high enough to accelerate the timeline.
At 93.7, it was.
The second question: what had they done with him?
The brief showed the scout vessel's docking record at a staging station in the Seventh Network cluster. A training environment. Six weeks of physical and tactical assessment data, which Compact Intelligence had pulled from the station's monitoring logs through a passive intercept that had been running for three months on that particular installation. The assessment data was incomplete but readable: a human male, young by the species' biological metrics, physical baseline above average for an unmodified specimen, tactical training from a non-military background. The passive intercept had caught two references to a Thuvari liaison attached to the project, which told Eshet that the Compact was at least competent enough to use the only species with meaningful Aeluun experience.
The third question was the one with an unexpected answer.
She had expected the answer to be: what is his current integration stage?
The answer was not the stage. The stage was readable from the sensor data and was consistent with a six-week calibration period. What she had not expected was the sensor data itself, specifically the quality of it. The integration signature the Compact's monitoring had logged was clean and strong and had a specific characteristic she had only seen before in two other operational files: a coherence pattern that indicated the system was not distributing its calibration load across multiple processing channels but consolidating it into a tightly integrated primary structure.
Most integrations, in the early stages, were diffuse. The system tried multiple pathways simultaneously before settling on the architecture that matched the user's neurological profile. The process was messy because people were messy, because human biology and Thuvari biology and Vorath biology and every other compatible species' biology was full of redundant systems and competing circuits, and the Aeluun technology had to negotiate all of it before it could establish a functional architecture.
The human's integration signature was not diffuse. It had gone coherent in under six weeks, which meant the system had found its architecture almost immediately, which meant one of two things: either the compatibility score was doing what high scores theoretically did and producing a clean initial calibration, or the human's neurological profile had something the system recognized as structurally compatible in a deeper way than the compatibility metric captured.
Eshet did not know which. She did not have enough data. This was the answer she had not expected: her third question was not answered, it was replaced by a different and more interesting question, which was what kind of person produced a signature like that.
She returned to the brief's physical profile data. Male, young adult, pre-contact world, non-military background. The training assessment records flagged two anomalies: spatial awareness in confined-space drills that the monitoring had recorded as outlier performance, and fire discipline consistent with a trained hunter rather than an infantry recruit. The analyst had noted this as a quirk. Eshet noted it as the beginning of a profile.
A hunter. Someone who had spent significant time moving through terrain, reading it, waiting for the right moment rather than creating pressure continuously. Someone who had learned precision before they learned volume.
She pulled the tactical display's secondary surface and opened the Caleth Corridor sector map.
The Compact's ground presence in the Caleth Corridor was six months into what had become an attritional stalemate. Her ground forces held the advantage: three gifted-soldier units operating in rotation meant the Compact's opposing units were perpetually facing enhanced opponents, and enhanced opponents in attritional terrain created the kind of sustained pressure that wore through unit cohesion over time. The Compact unit in the primary sector had taken losses in four engagements over four months. They were holding by discipline and familiarity with the terrain, not by any tactical advantage.
The question was whether they would still be holding in another four months if the compatible human was operational.
She considered this for ninety seconds, which was longer than she usually took for decisions at this operational level, but the consideration was worth the time because the decision she made here would shape the next several months of sector activity, and she preferred not to reshape sector activity more often than necessary.
Then she pulled up her force allocation display and made three changes.
The first was routine: she moved a surveillance package from a quiet sector on the network's eastern edge to a position that would give her better coverage of the Seventh Network cluster staging station. The station itself was outside Dominion operational territory, which meant she couldn't act on the surveillance directly, but she could track the human's movement when the Compact shifted him out of the station environment, which they would do, because compatible humans who stayed in training environments were not the problem. Compatible humans in the field were the problem.
The second change was less routine: she reallocated a gifted-soldier unit from a contested corridor in the network's western sectors, where the engagement tempo had been low for six weeks and where the unit was underutilized, to the Caleth Corridor. This would bring her total gifted-soldier presence in the Caleth Corridor to five units, which was more than the sector's strategic value strictly warranted. She wrote the reallocation order in language that framed it as a response to recent Compact ground activity in the sector, which was accurate, and did not mention the intelligence brief, because the intelligence brief was currently classified at a tier that the reallocation order did not need to cite.
The third change was the most significant and she made it without hesitation: she filed a notification with Dominion High Command through the standard intelligence reporting channel, but she filed it in a specific format that placed it in the passive review queue rather than the active alert queue. The difference was procedural: active alerts triggered immediate Command attention and Command response protocols, which would mean this problem became someone else's priority within forty-eight hours. Passive review meant the notification was on record, could not be said to have been withheld, and would be reviewed by Command in the normal cycle, which was seven days.
Seven days was enough time for her to have a clearer picture of what she was actually dealing with before someone at Command decided they needed to manage it.
She was not hiding the information. She was managing the information's timing, which was a different thing, and one she had eleven years of experience doing correctly.
The brief's technical appendix was still open on the primary display. She read through the integration signature data again, more slowly this time, with the specific attention she gave to things she intended to understand thoroughly before she acted on them further.
The coherence pattern held up on the second reading. It was not a sensor anomaly and it was not a calibration artifact. It was a genuine signature characteristic, and it was the most interesting thing she had encountered in the integration data files since her own initial calibration a decade ago, when the system had consolidated around her processing architecture in a way that her then-commanding officer had described as the cleanest first-stage integration the division had logged in three years.
She had been twenty-nine years old. She had been doing this for eleven years since, which meant she understood the development curve in a way that no briefing document could convey and no compatibility score fully predicted.
At six weeks, with a coherent architecture and a 93.7 score, the human was still early stage. Still in the range where the system was mapping rather than amplifying, building its understanding of the user's neurological patterns before it began the actual capability development that the briefing documents called enhancement. He would not, at six weeks, have anything in the field that would make him a material threat to her experienced gifted-soldier units.
At six months, depending on how the development curve ran, he might.
At a year, at that score, with an architecture that coherent, she genuinely did not know what he would be. That was the honest answer, and Eshet preferred honest answers even when they were uncomfortable, because comfortable answers were how you got surprised.
She did not want to be surprised by this particular variable.
The surveillance package she'd reallocated would give her tracking on his movement out of the staging station. The additional gifted-soldier unit in the Caleth Corridor would give her a resource advantage when the Compact moved him into active field deployment, which they would do, because you did not put six weeks of training and Thuvari integration oversight into a resource and then leave it in a training environment. You put it in the field where it could generate the kind of data that justified the investment.
When they moved him to the field, she would know. When she knew, she would have the option of engaging before the development curve made engagement less straightforward.
She had not decided whether to take that option. Not yet. The surveillance data would tell her more, and the field performance data would tell her more, and a Blade-Commander who made irreversible decisions on incomplete information was a Blade-Commander who made the kind of errors that became operational case studies.
She closed the technical appendix and moved the brief to the active file rather than the archive. It would stay there, accessible, alongside the surveillance tracking data when that data started populating.
Her own integration, eleven years built, ran its continuous background inventory in the way it always did: reading the Vorath's Certainty's operational environment through the sensory channels it had permanently restructured, tracking the ship's seventeen crew members by their movement signatures through the hull material without effort, processing the acoustic data from the external sensor array as a secondary stream that she no longer consciously attended to but that produced alerts when something changed. The system had been part of her longer than it had not been part of her, at this point, and the question of where her baseline biology ended and the Aeluun architecture began was one she had stopped trying to answer several years ago.
The human, six weeks in, was still at the stage where that question felt answerable. He would find out, in time, that it stopped being answerable.
She added a note to the active file: monitor staging station transit records for movement order. Flag immediately on departure.
Then she did something that was not standard operational procedure and that she would not have described to anyone in the Dominion's command structure, not because it was improper but because it would have required explaining things about how she thought that she had no particular interest in explaining.
She pulled up the sensor data's integration signature graphic and looked at it.
Not for analysis. She had done the analysis. She looked at it the way she looked at any opponent she was preparing to understand: with the specific attention of someone trying to find the thing that the numbers didn't capture.
The coherence pattern. The consolidated architecture. The clean settling of the system into a primary structure without the diffuse noise of a long calibration period. Behind that pattern was a person whose neurological profile had something in it that the Aeluun system had recognized almost immediately as structurally compatible, in a way that went deeper than the biological metrics.
A hunter, the training assessment had said. Someone who waited. Someone who learned the terrain.
She had been doing this for eleven years. She had read a lot of integration signatures. She had encountered a handful of people whose signatures had the quality this one showed, and every one of them, without exception, had eventually developed capabilities that surprised her in some specific way she had not predicted.
She noted this without alarm. It was data.
The sector map was still open on the secondary display. She looked at the Caleth Corridor's geography, the contested stretch of industrial terrain her ground forces had been working for six months. She knew that terrain in the way she knew all operational terrain she had spent significant time in: thoroughly, specifically, as a physical space with real characteristics that mattered in real engagements.
The human would be in that terrain soon enough. The training timeline suggested four to six weeks before the Compact moved him out of the station environment, and the Caleth Corridor was the obvious destination given the Compact's current operational priorities.
She closed the sector map and the integration signature graphic and the active file, in that order. The brief had told her what she needed to know and the decision she'd made was the right one at this stage, and the rest of the analysis would come from data that did not yet exist.
The viewport showed the same unchanging star field it always showed. Eshet had never been particularly interested in the aesthetics of space, in the way some of her fellow commanders were, the ones who kept records of impressive nebulae and talked about the scale of things. Scale did not interest her. Scale was abstract. What interested her was the specific.
Specifically: a compatibility score she had never seen documented at this level in any operational file, including the Dominion's classified historical records. Including the Vorath's own founding generation. Including her own file.
She had a 91.2. In eleven years. In sustained operational development through eighty-three documented ground engagements and the continuous load of Aeluun-augmented command function.
He had a 93.7. At baseline. Six weeks in.
She added one more note to the active file, in a separate notation field she used for the kind of assessment she did not put in official reports.
This is not a tactical variable. Assess as potential strategic variable. Handle accordingly.
She set the display to standby.
At 0347, she ran through her morning conditioning sequence in the small cleared space beside the command desk, which she had been doing every morning for eleven years at whatever time the ship's cycle made available. The sequence took thirty-two minutes. It was the same sequence every morning, a foundation the integration had built itself around in the early stages and that she had maintained since because consistency in the physical baseline was the clearest way to track changes in what the system was doing.
At 0419, she was done. The Vorath's Certainty's wake cycle would begin in forty-one minutes.
She stood at the viewport and listened to the ship's background systems run their routines, which she processed through the integration's acoustic channel without attending to it consciously, and she thought about a compatibility score she had never seen in an operational file, and she thought about a hunter who waited and learned the terrain, and she filed both of those thoughts in the same category she filed everything she needed to understand before she acted on it.
The surveillance package reallocation order had already propagated through the network. The gifted-soldier unit was already receiving its new sector assignment. The passive-review notification was on record at High Command.
Everything was in motion. The motion was appropriate to the information available. In three to four weeks, she would have tracking data, and after that she would have field-performance data, and after that she would have a clear picture of what this particular variable looked like when it was operational.
She would handle it then, with the information that existed then, the way she handled everything: specifically, without panic, and without the comfort of assumptions she couldn't afford to maintain.
The star field outside did not change. The ship's systems ran their routines. In six weeks or four or eight, a young human male with a compatibility score the historical records had never documented would step into the Caleth Corridor's contested terrain with six weeks of training and an Aeluun integration that had consolidated faster than any case file described.
Eshet began composing her morning operational review in the portion of her attention the integration kept free for administrative work.
She wrote the Caleth Corridor section last and kept it brief: Sector resource allocation adjusted. Current force posture adequate for anticipated Compact activity through six-week projection window. Reassess at window close.
She did not mention the brief. She did not mention the surveillance package. She did not mention the compatibility score, or the coherence pattern, or the notation she had made to herself about strategic variables.
She saved the review, set it to transmit at the standard 0600 distribution cycle, and moved to the next item on the morning's list.
The sector was covered. The asset was being monitored. The decision about how to handle what came next would be made with better information than she had right now, and better information was worth the time it took to gather.
That was the whole of it.
She had been doing this for eleven years. She knew the difference between a problem that needed to be solved immediately and a problem that needed to be understood first, and this was the second kind, and the worst thing she could do with the second kind was treat it like the first.
She pulled up the next brief in the morning's queue, which was a supply logistics report from the western sectors, and she read it with the same attention she gave everything, which was complete and unhurried, because the supply logistics of the western sectors also mattered, and everything that mattered deserved to be read correctly.
The integration ran its inventory. The ship ran its systems. The surveillance package moved into position around a staging station in the Seventh Network cluster, and it would run quietly and continuously until it had something to report, which it would, in time.
She gave the supply logistics report her full attention and made two notes and moved on.
No comments yet. Be the first to share your thoughts!