Infrastructure
by Charlie Foxtrot
Copyright© 2026 by Charlie Foxtrot
Science Fiction Story: Naleth is fourteen months into a military research contract studying why civilians stall in the Integration system. She's found the answer. Sixty-nine percent of civilian designations are combat roles. All six attributes optimize for warfare. The progression track exists for soldiers alone. She was hired to find a gap in the design. She found the design. The system, it turns out, found her first.
Tags: GameLit Military Science Fiction
A short story set in the Integration era, approximately fifteen years after Signal Zero.
The designation distribution chart had been running for six minutes, which was four minutes longer than it should have taken, because the dataset was large. Naleth had requested a sample of 140,847 individuals: civilian-registry confirmed, non-military employment on record, residing in settlement zones Four through Seven. The Integration Assessment Office had given her access to the anonymized cohort eighteen months ago when she’d signed her contract. She had been looking at these numbers, in various configurations, ever since.
The chart resolved.
She looked at it for a while without writing anything down.
Outside the research module’s single porthole, the station’s running lights swept a slow arc across the dark. Night cycle aboard a military platform had a specific quality of silence: not quiet, exactly, but all the sounds were the wrong register for human voices, which gave the illusion of solitude without providing it. The research staff went home at 1800. The security rotation had a checkpoint every forty minutes. Naleth had been here since 0900 and had eaten something at some point and couldn’t now remember what.
The chart said what it always said, regardless of how she sliced the cohort.
She pulled her working notes and began to add to them, because she was fourteen months from the end of her contract and a report was owed, and she had always written better when she was bothered by something.
The project brief had used the phrase civilian utility index, which was a policy-friendly way of asking a simpler question: what fraction of the Integration’s infrastructure was actually useful to people who didn’t carry weapons for a living? Fourteen months ago, Naleth had expected to find a number somewhere in the comfortable range. She had expected the system to be dual-use in the ways that most infrastructure was dual-use: military in origin, civilian in application, beneficial across the board in ways that justified the word gift.
She was no longer expecting that.
She opened the designation distribution across her full cohort. The eight Foundation Designations, spread across 140,847 civilian-registered, non-military individuals.
Vanguard: 8.4%
Sentinel: 11.2%
Operative: 12.7%
Specialist: 14.9%
Commander: 22.1%
Technician: 11.6%
Medic: 9.3%
Scout: 9.8%
She had run this breakdown forty-seven times since she first pulled it. The numbers shifted slightly depending on how she defined the cohort. Tighter age bands, different sector registries, employment categories with varying precision, but the shape never changed. Roughly 69% of her civilian cohort held designations whose primary function, per the system’s own documentation, was combat.
Vanguard: assault and breakthrough. Sentinel: defense and area denial. Operative: infiltration and precision strikes. Specialist: ranged combat and fire support. Commander: tactical coordination. Five designations, one and a half pages of the system document, and every one of them described a warfighting role first.
She had read the documentation carefully. She had looked for civilian applications listed in the primary descriptions and found them in the footnotes and the edge cases: a Commander’s leadership abilities translated to corporate management, technically; a Sentinel’s protective instincts applied to personal security work, in principle. The system document noted these possibilities with the specific courtesy of a manual that included a safety warning you were expected to ignore.
She wrote in her notes: The system has categorized 69% of a civilian cohort into warfighting roles. This is not noise. At N=140,847, the distribution is too consistent across demographic subgroups to be explained by measurement artifact. The system is not assigning these designations by accident.
Her own designation was Technician, which sat in the 11.6% she thought of as the plausibly civilian bucket. She noted this without feeling particularly reassured by it.
The attribute analysis was the section of her notes she had been putting off for three weeks, because she knew what it said and wanted to be wrong before she wrote it down.
She wasn’t wrong.
The six attributes were: Signal, Frame, Drive, Lattice, Echo, Flux. Each had a system description, a governing domain, and a set of documented applications. She had gone through them attribute by attribute and attempted to separate the combat-utility applications from the civilian-utility applications, on the assumption that a system with genuine dual-use intent would show some weighting toward the latter.
Signal governed perception, reaction time, targeting accuracy, and electronic warfare capability. Its narrative-level description in the system document described, at high values, something resembling battlefield omniscience.
Frame governed health, melee damage, carrying capacity, and physical resistance to harm. At extreme values, the document noted that the system reinforced bone structure and skin to a degree that was, the document used the word visibly, inhuman.
Drive governed stamina, movement speed, recovery rate, and resistance to morale effects, which was a phrase that meant resistance to fear in combat conditions.
Lattice governed skill slots and designation merge paths. A higher Lattice meant more tools. The system’s primary vehicle for filling those tools was content that required killing things.
Echo governed ability potency, system resonance, and, at sufficient depth, the system’s investment in keeping you alive. The death-protection mechanics were among the most clinically detailed sections of the system document. At Echo ranges above 31, the system could reconstruct an individual from near-total physical destruction. At Echo above 76, the system would not allow death at all. The document described this as the system refusing to release its most valuable assets.
Flux governed critical hit chance, ability mutation probability, and resistance to system anomalies.
Naleth had highlighted the combat-utility applications in one color and the civilian-utility applications in another. The document was mostly the first color. She had found genuine civilian applications for Lattice (crafting, analytical work), partial civilian applications for Echo (social influence, consciousness depth), and arguable civilian applications for Signal (general perception enhancement). The other three she had been unable to color anything but the first color without being dishonest about what the words said.
A friend who had been through a medical program had called the Frame attribute “the system’s way of turning you into something you can’t unbecome.” She had been describing the physical changes at high values. Naleth had filed the quote and returned to it often.
She wrote: All six core attributes have primary or substantial secondary combat utility. None are named for capabilities that don’t translate directly into warfighting advantage. The system did not name a Creativity attribute, or a Knowledge attribute, or a Diplomacy attribute. It named six attributes, and all six of them make you better at surviving violence.
She underlined that last sentence, which she rarely did.
She had been putting off the skill category analysis because it was the part of the project where she had expected to find her counterargument. Skills were specific. Skills could be genuinely civilian. Field Medicine, Field Engineering, System Architecture: these sounded like the vocabulary of people who built things and healed people and maintained infrastructure.
She ran the count anyway.
Five skill categories: Combat, Movement, Technical, Support, System. Seventy-four documented skills in the public registry, which was the set the IAO had cleared her to access. She went through them one by one and asked the same question she had been asking since she pulled the first designation chart: how many of these would be primarily useful to a person who was never in combat?
The Combat category: twenty-three skills. Precision Firearms, Close Quarters Combat, Heavy Weapons, Ballistic Prediction, and nineteen variants she had catalogued by application. Primary civilian utility: zero.
The Movement category: twelve skills. Covert Movement, Spatial Compression, Zero-G Maneuvering, and nine others. Primary civilian utility: perhaps three, if she was generous about what Zero-G Maneuvering served beyond combat operations in space.
The Technical category: eighteen skills. This was where she had expected to find her counterargument in bulk. She found eight skills with genuinely broad civilian application: Field Engineering, System Architecture, and several crafting-adjacent abilities. The remaining ten were electronic warfare, drone command, and systems she had to read twice before she could articulate why they were in the Technical category rather than the Combat one.
The Support category: fourteen skills. Field Medicine was here, and Threat Assessment, and Tactical Command. She noted that the category was named Support, not Medical or Care or Community. The naming was the system’s own.
The System category: seven skills, all rare, all requiring conditions she had been unable to document adequately from the civilian registry data. Architect Reading was here. She noted that the one skill explicitly concerned with understanding the system’s own origins was rare enough to be academically invisible.
Final count: seventeen skills, out of seventy-four, with primary civilian utility. Twenty-three percent.
She looked at that number for a long time.
Then she looked at the Rift mechanics section, which she had been circling for weeks without landing on it directly.
Rifts were the system’s primary experience delivery mechanism. The document described them as common, hours to days in duration, populated with system-generated entities, and timer-based: complete objectives before the Rift collapses or be forcibly ejected, with injury. Solo Rift access required Integration Level 25 or higher. Fireteam access required IL 10, with the registering member needing IL 10 and no minimum for the others.
The four documented Rift types were: Assault, Survival, Extraction, and Anomaly.
She had been trying to explain the civilian progression gap in her cohort for three months. Why did civilian-registered individuals plateau around IL 8-12 when military-registered individuals in equivalent demographic windows continued to advance? She had proposed twelve hypotheses. She had discarded eleven of them for failing to account for the full magnitude of the gap.
The twelfth hypothesis was: the system’s progression infrastructure was designed for a population that would use it.
The direct level-up events were documented in an addendum she had received late in the project, after she’d submitted a formal request for supplementary mechanical data. She read the confirmed triggers again.
Solo Rift completion. Surviving a system event that incapacitates everyone else present. First-contact encounter with a previously unclassified threat category. Completing an action the system has no prior record of any individual completing.
She read the list three times, looking for the entry she had assumed would be there.
It was not there.
To read the complete story you need to be logged in:
Log In or
Register for a Free account
(Why register?)
* Allows you 3 stories to read in 24 hours.