Lore:HCAF Ranks

ORGANIZATION

Heliostatic Coalition Armed Forces

Other Names: HCAF
Related Lore: Lore:Heliostatic_Coalition, Expeditionary Police Force (of HC)
Languages: PanslavicThe primary language of the Heliostatic Coalition, Pan-Slavic evolved organically from the Eastern and Central European linguistic roots of the founding colonists who settled Vistula and its surrounding systems during the First Great Interstellar Migration. Isolated from Sol for centuries during the 'Quiet Century', the scattered colonies saw their inherited languages drift, merge, and simplify under the pressures of survival and limited communication between settlements. When the colonies re-established contact in the late 2390s and formalized the Heliostatic Compact in 2405, the engineered Pan-Slavic emerged as the natural standard.
Linguistically, Pan-Slavic retains the Slavic verbal aspect system and much of its foundational vocabulary: body parts, family, nature, and basic actions. However, centuries of separation and the mixing of settlers from different regional backgrounds simplified its noun morphology dramatically. Today, Pan-Slavic is spoken natively by the human majority of the CZD and as a second language by most other Coalition citizens.
While Sol Common remains the language of interstellar communication, Pan-Slavic is the language of home, of the Chamber, and of the Long Arm. To an outsider, it sounds simultaneously familiar and alien - recognizably Slavic in its rhythm and structure, but punctuated by loanwords from the Turkic and Persian linguistic strata that survived the Quiet Century., Sol CommonAnd when contact was established, the Admiral waved at the screen and said, "Mi parolas la lingvon de la Homines!" - I speak the language of Mankind. A simplified mix of Esperanto and Modern Latin, and the only recognized official language of the Sol Federation. This peculiar constructed language became popular during SolFed's earliest days, and was almost entirely overtaken by other popular tongues - it became widespread through heavy-handed political maneuvering with the help of corporate bureaucrats and other undesirables. Nowadays, it's a near-universal tongue and a must-know for any sentient being that plans to leap forward into space.
Contributors: Stalkeros Token Panslavic representative, author of the entire HC, too many PRs to count (like the Random Ship Event framework, and an incredible writer all around. Truly a god among men, and a gift among women. If there are two people left alive on Earth, they're both him, somehow. This wiki and community are eternally grateful for their contributions, and beyond that, their simple presence. They are incredible for reasons beyond what they do, and deserve far better than what words can write.
May be contacted on Discord in regards to HC content. In their words:
"Hi I Make HC Stuff If You Also Wanna Make HC Stuff Please Reach Out Or I Might Veto Your Shit KTHX XOXO", XeroX_Office Galactic Hero. High, ranking, official.
May contact on Discord about HC Larp, SolFed Larp stuff.

The Heliostatic Coalition Armed Forces (HCAF) is the military organization of the Heliostatic Coalition. It operates on a doctrine of network-centric warfare, distributed authority, and mission-specific orchestration.

The HCAF does not use a traditional rank system. Instead, it uses Authority Codes (AUTH), specializations, qualifications, and temporary operational roles such as Actual and Orchestrator. All personnel are Vertexes — nodes in the Integrated Tactical Network.

Part One: Foundations

1. Note on Rank Equivalents

The HCAF does not use a rank system fully comparable to regular militaries. There is no enlisted/officer divide, permanent commanders, or chain of command in the traditional sense.

What the HCAF has instead:

AUTH Codes: Scope-specific certifications that describe what you're certified to do, not who you are.
The Actual Designation: A temporary, mission-specific role assigned by the ITN. The Actual has ultimate decision-making authority for the duration of a mission.
Orchestrators: Temporary, mission-specific roles responsible for assembling and coordinating a unit. An Orchestrator is not a commander. They orchestrate.
Intent Authority: The body or individual responsible for setting strategic goals. They do not command. They set intent.

If you are coming from a conventional military background: Forget everything you know about rank. An HCAF "AUTH-4" is not a Lieutenant. They are a Vertex who is certified to orchestrate a platoon-sized element. They may never exercise that certification. They may exercise it once and never again. They are not "in charge" of anyone outside of a mission context. They are, however, responsible for whether the mission succeeds and whether the people under their orchestration come home.

2. Note on the ITN

The Integrated Tactical Network is the foundation of the HCAF. It is a quantum-encrypted, mesh-network data fabric that links every asset, from an individual Vertex's helmet to a Sovereign-class battle carrier, into a single, real-time tactical picture.

The ITN works. This is a foundational assumption of HCAF doctrine. It does not fail in major ways. It has never suffered a theater-wide failure. It is not a technology that is "mostly reliable" or "usually available." It is the environment in which the HCAF operates, as fundamental as air or gravity.

This does not mean the HCAF is complacent. The Analog Layer exists because the HCAF was founded by survivors of isolation. The Coalition's foundational trauma is the slow decay of systems that everyone assumed would keep working. The HCAF does not assume anything will always work. It trains for network failure the way it trains for casualties: not because it expects them, but because it refuses to be surprised by them.

The ITN's failure modes are human, not technical.

Cognitive Overload: A Vertex cannot process the data. The network works. The human doesn't. This is the most common failure. The ITN can be overwhelming. It provides perfect information, and perfect information is useless if the human receiving it cannot act on it. HCAF training emphasizes data discipline and cognitive resilience for this reason.
Compromise: An infiltrator feeds false data into the network. The network works. The data doesn't. The ITN is encrypted and authenticated, and no system is perfectly secure. A compromised node can poison the tactical picture. HCAF counter-intelligence is constantly vigilant for this.
Over-Reliance: A Vertex trusts the network more than their own judgment. The network works. The human has stopped thinking. This is the most insidious failure mode. A Vertex who cannot function without the network is not a Vertex. They are a liability. HCAF culture actively discourages over-reliance on the ITN. The network is an advantage, not a crutch.

The HCAF's enemies plan around the network, not for its absence. This is the strategic reality of fighting the HCAF. SolFed regulars report "fighting ghosts." The HCAF doesn't just have better technology. It has perfect information. Its enemies cannot surprise it, cannot outmaneuver it, cannot exploit gaps in communication. The HCAF sees everything, knows everything, and responds instantly. This means the HCAF's enemies do not plan for network failure. They plan for network presence. They plan to be seen, to be predicted, to be outmaneuvered. And they plan accordingly.

The ITN is a strategic assumption, not a tactical advantage. The HCAF assumes the network will work. Its enemies must assume the same. This is the environment in which the HCAF fights. It is the water in which it swims.

3. Note on the "Actual"

The term "Actual" is not a rank. It is a designation automatically applied to the individual with ultimate decision-making authority for a given tactical unit.

How It Works

Automatic Assignment: When a unit is assembled for a mission, the ITN automatically designates the most appropriate member as "Actual" based on a combination of factors: AUTH certification, mission-relevant experience, specialization relevance, and demonstrated network proficiency. This is not a formal promotion. It is a temporary operational designation.
Callsign Suffix: The designated "Actual" appends the suffix to their callsign. For example, a Vertex with callsign "Hammer Seven" becomes "Hammer Seven Actual." This signals to everyone in the network who holds ultimate authority for that mission.
Dynamic Transfer: If the designated "Actual" is killed, incapacitated, or otherwise unable to command, the ITN automatically reassigns the "Actual" designation to the next most appropriate member of the unit. The network always has an Actual. If the network is down, the Analog Actual takes over. If the Analog Actual is dead, the next Vertex in the pre-designated sequence assumes authority. The chain does not break.
Functional Authority over Certification: An AUTH-2 Vertex who is designated "Actual" for a mission has operational authority over an AUTH-5 Vertex assigned to the same unit for the duration of that mission. Certification is secondary. The "Actual" designation is primary. The person responsible for the mission is the person who makes the call.

Pre-Mission Transparency

Before a mission begins, the ITN's selection logic is visible and contestable.

Selection Criteria: Every Vertex in the unit sees what factors were weighted: AUTH certification, mission-relevant experience, specialization relevance, network proficiency, recent performance.
Candidate Summary: The designated Actual's relevant scores are summarized in a clear "why this person" format. Not raw data. A readable justification.
Challenge Mechanism: Any Vertex can formally contest the designation before the mission begins. The challenge is reviewed by a panel of three randomly selected peers with relevant certification. If the challenge succeeds, a new Actual is designated. If it fails, the challenger accepts the decision and moves on.
In Combat: There is no challenge mechanism once the mission is underway. The Actual's authority is absolute. The pre-mission transparency builds trust and legitimacy. The system is not a black box.

Degraded-Mode Protocols

Failure Mode	Protocol
ITN goes down	Pre-mission briefing includes a designated "Analog Actual," a Vertex who will assume command if the network fails. Chosen before the mission, not by the network.
Actual is incapacitated	The ITN reassigns the designation. If the ITN is also down, the Analog Actual takes over.
ITN designates someone incompetent	Peer challenge process. Three randomly selected peers review the designation. If upheld, the ITN reassigns.
Two Vertexes both claim Actual	The ITN resolves it. If the ITN is down, the pre-mission Analog Actual resolves it.
A Vertex refuses to follow the Actual's orders	The Actual flags the refusal in the network. A peer review panel determines if the refusal was justified. If not, the refusing Vertex faces administrative consequences. If the refusal occurs in combat and results in casualties, the consequences are severe.

Implication: The HCAF does not have a permanent chain of command. It has a temporary, mission-specific chain of command that dissolves when the mission ends. Authority flows to the most capable individual for the specific situation, as determined by the network, confirmed by peers, and accountable to review.

4. The Vertex

"Every combatant is a Vertex."

All HCAF personnel, regardless of specialization, share the following core competencies:

Network Proficiency: Flawless use of the Integrated Tactical Network (ITN).
Data Discipline: Accurate, timely reporting of status, position, and observations. Your data-stream is your primary weapon. In combat, a delayed report can mean a dead comrade. A false report can mean a dead battalion.
Adaptive Execution: Ability to operate within Commander's Intent without micromanagement. You are trusted to execute.
Cognitive Resilience: Capable of processing high-volume network data without overload. The network amplifies you. It does not break you.
Orchestration over Execution: Your job is not to do everything yourself. Your job is to orchestrate the resources of the network to achieve the objective.

A Vertex is not a rank. It is a standard. Every HCAF soldier is expected to meet it. Those who cannot are not discharged. They are trained until they can, or they are reassigned to roles where their limitations are not a liability.

5. Plug-and-Play Vertexes

The HCAF does not maintain rigid, permanent squads. Units are assembled dynamically based on mission requirements, personnel availability, and the specific tactical needs of the operation. This is made possible by the ITN and the standing universal personnel doctrine.

Key Principles

No Permanent Squads: A soldier does not belong to a fixed fireteam or squad. They are a node that can be slotted into any formation as needed.
Mission-Based Assembly: An Orchestrator assesses the mission, reviews available personnel, and assembles the optimal mix of specializations. One day, that might be a standard 4-person fireteam: Skirmisher, Heavy Skirmisher, Drone Operator, Orchestrator. The next, it might be an 11-person section of Heavy Skirmishers with crew-served automortars. The network ensures seamless integration.
Role Fluidity: A soldier's specialization does not lock them into a single role. A Drone Operator (CBT-03) can be assigned as a standard Skirmisher if the mission doesn't require drones. A Heavy Skirmisher (CBT-02) can operate as a standard Skirmisher when not carrying heavy weapons. The only constant is that they are a Vertex.
Network-Enabled Coordination: Because everyone is proficient with the ITN, there is no friction from working with unfamiliar personnel. The network provides real-time data on each soldier's capabilities, status, and position. This allows instant coordination regardless of prior experience working together. When the shooting starts, you don't have time to learn your teammate's name. The network already knows it. It knows their blood type. It knows their ammunition count. It knows whether they're still breathing.

Implication: An HCAF soldier is never "just" a rifleman or "just" a technician. They are a Vertex who happens to have a specialization.

Persistent Clusters and unit cohesion are addressed in Section 15. The HCAF acknowledges that plug-and-play units do not build the deep bonds that sustain soldiers through combat. Persistent Clusters are the solution.

Part Two: Personnel Systems

6. Authority Codes

The HCAF does not use ranks. It uses Authority Codes, scope-specific certifications that describe what you are certified to do.

How AUTH Codes Work

Scope-Specific: Each AUTH code describes a scope of orchestration authority. AUTH-4 means you are certified to orchestrate a platoon-sized element. It does not mean you are "senior" to an AUTH-3.
Earned Through Certification: You qualify for an AUTH code by demonstrating you can do the job, not by waiting a certain amount of time.
Expirable: AUTH codes expire if not exercised. A Vertex who hasn't orchestrated a squad in two years may need to requalify.
Not Hierarchical: There is no "seniority" between AUTH codes. An AUTH-5 (Company Lead) does not outrank an AUTH-3 (Squad Lead) in any general sense. They have different scopes of certification.
Independent of Specialization: Your specialization (CBT, ENG, etc.) describes what you're trained to do. Your AUTH code describes what scope you are certified to orchestrate. These are independent.

AUTH Code Table

Code	Scope	What You're Certified to Orchestrate	Monthly Stipend	Monthly MWC
AUTH-1	Individual	Yourself. You can operate independently within Commander's Intent.	5 Ɱ	6 Ɱ
AUTH-2	Fireteam	2 to 4 Vertexes. You can lead a fireteam-sized element.	8 Ɱ	10 Ɱ
AUTH-3	Squad	2 to 4 fireteams (8 to 16 Vertexes).	12 Ɱ	15 Ɱ
AUTH-4	Platoon	2 to 4 squads (20 to 40 Vertexes).	18 Ɱ	22 Ɱ
AUTH-5	Company	2 to 4 platoons (80 to 160 Vertexes).	28 Ɱ	35 Ɱ
AUTH-6	Battalion	4 to 6 companies (400 to 800 Vertexes).	45 Ɱ	55 Ɱ
AUTH-7	Regiment	3 to 5 battalions (1,500 to 4,000 Vertexes).	75 Ɱ	80 Ɱ
AUTH-8	Brigade	3 to 5 regiments (5,000 to 20,000 Vertexes).	120 Ɱ	80 Ɱ
AUTH-9	Division	3 to 5 brigades (20,000 to 100,000 Vertexes).	190 Ɱ	80 Ɱ
AUTH-10	Corps	2 or more divisions (50,000 to 200,000 Vertexes).	300 Ɱ	80 Ɱ
AUTH-11	Theater	Multiple corps. Supreme strategic authority for a theater of operations.	480 Ɱ	80 Ɱ

Note on Stipend: The stipend is real currency. It can be saved, withdrawn, transferred, sent home, invested. It is paid monthly in Soft Marks. It is in addition to the base stipend, specialization supplement, qualification supplement, and QI supplement.

Note on MWC: The Morale & Welfare Credit is a monthly allowance of non-transferable, non-drawable credit. Use it or lose it. It resets on the first of the month. It is in addition to the stipend and other MWC supplements.

Note on AUTH-7+ MWC: The MWC caps at 80 Ɱ for AUTH-7 and above. Higher AUTH codes receive additional stipend instead. The reasoning is simple: a senior Intent Authority has less need for subsidized entertainment than a junior Vertex. They can afford to pay for their own recreation. The MWC is a morale tool, not a wealth tool.

Certification Requirements

Demonstrate proficiency in all responsibilities of the previous AUTH code.
Complete a live-fire or simulation exercise where you orchestrate a unit of the appropriate size through a complex scenario. Live fire is preferred.
Receive peer evaluation from at least three Vertexes who have served under you.
Pass a network proficiency assessment. Can you process high-volume data without overload?
Receive certification from a Certification Board. Three randomly selected Vertexes who hold the AUTH code being assessed or higher.

Certification is not time-based. If you're ready in 6 months, you're certified in 6 months. If it takes 5 years, it takes 5 years.

Certification is revocable. If you demonstrate poor judgment or fail to maintain proficiency, your certification can be suspended pending review. If your poor judgment results in casualties, your certification will be suspended. The review will determine whether you retain it.

7. Specialization Groups

Your specialization describes what you're trained to do. It is independent of your AUTH code. You can be a CBT-01 (Skirmisher) with AUTH-3 (Squad Lead) certification. You can be an ENG-01 (Engineer) with AUTH-1 (no orchestration certification).

The General Principle

Specializations describe a domain of competence. AUTH codes describe scope of orchestration authority. Orchestrator, Actual, Intent Authority, and all "commander/leader/officer" titles are temporary roles, not specializations. If a job title describes who someone commands, it's not a specialization. It's an AUTH code wearing a costume.

Specializations are broad domains, not narrow job titles. An Engineer can handle power, structure, life support, damage control, construction, and survey because the systems are standardized and the nanoforges do the heavy lifting. A Logistician can handle supply, convoys, inventory, and distribution because the ITN tracks everything and the human role is to manage exceptions. A Medic can handle trauma, surgery, mental health, and xenobiology because the human body is a system and the medic is trained to fix it.

What specializations do NOT include: permanent command roles. There is no "Engineering Platoon Leader" specialization. There is an Engineer with AUTH-4 who happens to be orchestrating a platoon this mission. There is no "Chief Medical Officer" specialization. There is a Medic with AUTH-5 who happens to be orchestrating a medical company this campaign. Command is a temporary role, not a specialization.

Group 1: Combat (CBT) — "The Teeth"

Philosophy: Every soldier fights. Specialization is about what scale of weapon they employ, not what kind of rifle. The network makes each soldier a versatile, adaptive combatant.

Special Note on the "Actual" Designation in CBT:

Within any assembled combat unit, the ITN automatically designates the most appropriate member as "Actual," the individual with ultimate tactical authority for that specific mission. This designation is not a rank. It is a temporary operational role. The Actual may be an AUTH-4, an AUTH-2, or even an AUTH-1 if the network determines they are the most capable for the specific situation.

Callsign Example: A squad assigned the callsign "Dagger" will have one most capable member (i.e. "Dagger Three") designated "Dagger Three Actual." All other members are regular "Dagger One," "Dagger Two," etc. If Dagger Three Actual is incapacitated, the ITN automatically reassigns the designation to the next most appropriate member.

Code	Job Title	Description	Monthly Stipend	Monthly MWC
CBT-01	Skirmisher	Standard infantry. Proficient with all personal-scale HCAF small arms: Zaibas assault rifle, Zaibas-Astrus DMR, Zaibas-Sprogis shotgun, and sidearms. Can fill any light infantry role, whether rifleman, marksman, breacher, or pointman, as mission dictates. The baseline combat Vertex.	+0 Ɱ	+0 Ɱ
CBT-02	Heavy Skirmisher	Operates support-scale and crew-served weapons: GPMGs/HMGs (e.g., Zaibas-Nuolatinis variable-output LMG/GPMG), recoilless rifles, rocket launchers, missile launchers (M/A-97 "Comet"), and man-portable energy cannons (M/ER-11 "Quasar"). Provides heavy firepower and area suppression. Can also operate as a standard Skirmisher when not employing heavy weapons.	+1.5 Ɱ	+1.5 Ɱ
CBT-03	Drone Operator	Controls tactical UAVs, UCAVs, UGVs, UCGVs, and synthetic assets for reconnaissance, surveillance, and light strike missions. The squad's "eyes in the sky" and organic precision strike capability.	+2.5 Ɱ	+2.5 Ɱ
CBT-04	Vehicle Crew	Operates HCAF ground vehicles: M/MBT-9 "Aegis", M/IFV-7 "Centurion", and other armored platforms. Trained in driving, gunnery, and vehicle command.	+2 Ɱ	+2 Ɱ
CBT-05	Orchestrator	Manages the local tactical picture. Coordinates artillery, air support, and electronic warfare. Acts as a secondary squad leader. The "conductor" of the mini-theatre. Often designated "Actual" for fireteam-sized operations.	+3 Ɱ	+3 Ɱ

Note: CBT-05 is a specialization in orchestration as a skill, not a permanent command role. A CBT-05 may be designated Actual for a mission, or may serve as a secondary orchestrator under another Actual. The specialization describes what they're trained to do. The AUTH code describes what scope they're certified to orchestrate.

Group 2: Engineering (ENG) — "Build It, Break It, Power It"

Philosophy: Standardized systems, automated diagnostics, and nanoforges mean one engineer can handle what once required a dozen specialists. An Engineer is a generalist who can handle power systems, structural integrity, life support, damage control, construction, and survey because the systems are standardized and the nanoforges do the heavy lifting. Specialization is about what kind of engineering problem you're best at, not what system you're chained to.

Code	Job Title	Description	Monthly Stipend	Monthly MWC
ENG-01	Engineer	Generalist. Power systems, structural integrity, life support, damage control, construction, survey. Proficient with all standard HCAF engineering systems and nanoforges. The baseline engineering Vertex.	+2 Ɱ	+2 Ɱ
ENG-02	Senior Engineer	Deep expertise in one or more engineering domains. Diagnoses complex, multi-system failures. Mentors junior engineers.	+4 Ɱ	+4 Ɱ
ENG-03	Fabrication Specialist	Operates and programs heavy-duty nanoforges. Can produce custom components and prototype parts. The engineer's engineer.	+5 Ɱ	+5 Ɱ

What about engineering command? An Engineer with AUTH-4 orchestrates an engineering platoon. An Engineer with AUTH-5 orchestrates an engineering company. An Engineer with AUTH-6 orchestrates an engineering battalion. There is no "Engineering Platoon Leader" specialization. There is an Engineer with the appropriate AUTH code who happens to be filling an orchestration role this mission.

Group 3: Logistics (LOG) — "Move It, Store It, Track It"

Philosophy: The ITN tracks everything. The human role is to manage exceptions, command convoys, and make strategic decisions. A Logistician is a generalist who can handle supply chain monitoring, convoy operations, inventory management, and distribution because the ITN tracks everything and the human role is to manage exceptions. Specialization is about what kind of logistics problem you're best at, not what echelon you're permanently assigned to.

Code	Job Title	Description	Monthly Stipend	Monthly MWC
LOG-01	Logistics Technician	Monitors the automated supply chain. Handles exceptions, reroutes shipments, tracks inventory. Proficient with all standard HCAF logistics systems. The baseline logistics Vertex.	+1 Ɱ	+1 Ɱ
LOG-02	Convoy Commander	Leads a convoy of MUV-12 "Mule" vehicles through contested territory. Manages human drivers and defensive teams. A specialization in convoy operations, not a permanent rank.	+3 Ɱ	+3 Ɱ
LOG-03	Senior Logistics Technician	Deep expertise in supply chain management. Plans large-scale supply operations. Mentors junior logisticians.	+4.5 Ɱ	+4.5 Ɱ

What about logistics command? A Logistician with AUTH-4 orchestrates a logistics platoon. A Logistician with AUTH-5 orchestrates a logistics company. A Logistician with AUTH-6+ handles theater-level supply chains. "Quartermaster" is not a specialization. It's a LOG-03 with AUTH-6 doing their job. "Ship Operations Coordinator" is a LOG-01 or LOG-03 assigned to a ship. "Fleet Logistics Coordinator" is a LOG-03 with AUTH-8+.

Group 4: Maintenance (MAI) — "Keep It Running"

Philosophy: Modular design and nanoforges make the "generalist mechanic" the standard. A single technician can fix almost anything. Specialization is about what kind of maintenance problem you're best at, not what system you're chained to.

Code	Job Title	Description	Monthly Stipend	Monthly MWC
MAI-01	Modular Systems Technician	Repairs and maintains all standardized HCAF equipment (weapons, armor, vehicles) using modular components and fabricators. The baseline maintenance Vertex.	+1.5 Ɱ	+1.5 Ɱ
MAI-02	Fabrication Specialist	Operates and programs heavy-duty nanoforges. Can produce custom components and prototype parts.	+4.5 Ɱ	+4.5 Ɱ

What about maintenance command? A Modular Systems Technician with AUTH-4 orchestrates a maintenance platoon. A Modular Systems Technician with AUTH-5 orchestrates a maintenance company. There is no "Maintenance Officer" specialization.

Group 5: Service (SVC) — "Support the Fighters"

Philosophy: Replicators handle nutrition. The human role is about morale, biology, and welfare. Service specializations are genuinely different domains (nutrition, morale, administration, culture), so they remain separate.

Code	Job Title	Description	Monthly Stipend	Monthly MWC
SVC-01	Nutritional Technician	Operates and maintains food replicators/nanoforges. Ensures nutrient balance for all species. Manages raw feedstock inventory.	+0.5 Ɱ	+0.5 Ɱ
SVC-02	Senior Nutritional Technician	Oversees a ship's entire food production system. Manages dietary requirements for specialized units.	+1 Ɱ	+1 Ɱ
SVC-03	Combat Nutritionist	A medical/logistics hybrid role. Designs specialized meal plans for combat stress, long-duration missions, and post-injury recovery.	+2 Ɱ	+2 Ɱ
SVC-04	Morale & Welfare Specialist	The actual "cook" or entertainer. A rare, highly specialized role focused on psychological well-being, special occasions, and diplomatic events.	+2.5 Ɱ	+2.5 Ɱ
SVC-05	Welfare Officer	Manages shore leave, recreation, and counseling services. Ensures the mental health of the crew.	+2 Ɱ	+2 Ɱ
SVC-06	Recreation Coordinator	Organizes off-duty activities, sports, and entertainment.	+1.5 Ɱ	+1.5 Ɱ
SVC-07	Cultural Liaison	Manages cross-species cultural events and diplomacy.	+2.5 Ɱ	+2.5 Ɱ

What about station administration? A Service specialist with AUTH-4+ can be assigned as a Station Administrator. This is an orchestration role, not a specialization. The ITN designates the most appropriate Service specialist for the role, and they fill it for the duration of the assignment.

Group 6: Organizational/Bureaucratic (ORG) — "The Paperwork Warriors"

Philosophy: The AI handles data. Humans handle people, law, policy, and exceptions. ORG roles never hold operational authority. They are staff, not command. A Legal Officer adjudicates. They don't command. A Staff Facilitator administrates. They don't command.

Code	Job Title	Description	Monthly Stipend	Monthly MWC
ORG-01	Administrative Technician	Manages the human-facing side of the ITN's decisions. Handles exceptions, appeals, and personal interactions with personnel.	+1 Ɱ	+1 Ɱ
ORG-02	Senior Administrative Technician	Oversees the administrative team for a unit. Liaises with the ITN's AI to ensure personnel data is correct and policies are followed.	+2 Ɱ	+2 Ɱ
ORG-03	Legal Officer	Handles Coalition law, Courts-Martial, and legal disputes. The human element of justice. Does not command. Adjudicates.	+6 Ɱ	+6 Ɱ
ORG-04	Staff Facilitator	A senior administrative officer. Advises on personnel, legal, and bureaucratic matters. Coordinates multiple units. Does not command. Administrates.	+3 Ɱ	+3 Ɱ
ORG-05	Adjutant	Orchestrator's personal assistant. Manages schedules, communications, and paperwork.	+2 Ɱ	+2 Ɱ
ORG-06	Senior Facilitator	Manages the administrative and planning side of operations. The Orchestrator's administrative counterpart.	+4 Ɱ	+4 Ɱ
ORG-07	Policy Analyst	Reviews and recommends changes to Coalition policy.	+4.5 Ɱ	+4.5 Ɱ
ORG-08	Personnel Data Manager	Ensures ITN personnel data is accurate. Tracks certifications, qualifications, and availability.	+5 Ɱ	+5 Ɱ

Critical Note: ORG roles are the one place where "officer" titles are justified, because these are legal and administrative roles, not operational command roles. An ORG-04 Staff Facilitator does not command troops. They administrate. The distinction is enforced by the Authority Tracks system.

Group 7: Medical (MED) — "Heal the Fighters"

Philosophy: Some specialization is still needed. Brain surgery is not bone setting. Human biology is not Unathi biology. But many roles are merged where practical. A Medic is a generalist who can handle trauma, surgery, mental health, and xenobiology because the human body is a system and the medic is trained to fix it. Specialization is about what kind of medical problem you're best at, not what organ you're chained to.

Code	Job Title	Description	Monthly Stipend	Monthly MWC
MED-01	Combat Medic	Field trauma. Stabilizes casualties on the frontline. The first responder.	+3 Ɱ	+3 Ɱ
MED-02	Medical Technician	Shipboard and field hospital care. Operates the sickbay. Manages medical equipment, supplies, and pharmaceuticals. The logistics of healing.	+2.5 Ɱ	+2.5 Ɱ
MED-03	Surgeon	Advanced surgical care. Handles combat injuries, organ damage, and critical cases. Includes trauma surgery, neurosurgery, and other surgical specialties. A surgeon is a surgeon. The specific organ is a detail.	+8 Ɱ	+8 Ɱ
MED-04	Mental Health Specialist	Counseling, trauma, stress, psychological conditions. Includes psychiatrists, psychologists, and mental health technicians.	+5 Ɱ	+5 Ɱ
MED-05	Xenobiologist	Non-Human biology. Essential for a multi-species force. Includes epidemiology and cross-species pathology.	+6 Ɱ	+6 Ɱ

What about medical command? A Surgeon with AUTH-5 orchestrates a medical company. A Surgeon with AUTH-6 orchestrates a medical battalion. There is no "Chief Medical Officer" specialization. There is a MED-03 Surgeon with the appropriate AUTH code who happens to be filling a medical orchestration role this campaign.

Group 8: Aviation (AV) — "The Skyriders"

Philosophy: Standardized flight systems, modular aircraft design, and ITN-assisted control mean one pilot can fly any airframe. One operator can run any sensor or EWAR suite. Specialization is about what kind of aviation problem you're best at, not what airframe you're chained to.

Code	Job Title	Description	Monthly Stipend	Monthly MWC
AV-01	Aircraft Systems Technician	Maintains and repairs all HCAF aircraft. Modular systems, nanoforge repairs.	+2.5 Ɱ	+2.5 Ɱ
AV-02	Flight Systems Operator	Operates sensors, EWAR, and mission systems on all HCAF aircraft. The "back seat" role.	+3.5 Ɱ	+3.5 Ɱ
AV-03	Pilot	Flies all HCAF aircraft. Single certification for all airframes.	+5 Ɱ	+5 Ɱ
AV-04	Loadmaster	Manages cargo, troop handling, and aircraft loading.	+2 Ɱ	+2 Ɱ

What about flight lead and aviation coordination? A Pilot with AUTH-2+ can be designated Flight Lead for a section of 2 to 4 aircraft. This is a temporary, mission-specific role. A Pilot with AUTH-4+ can be assigned as an Aviation Coordinator for a squadron, wing, or fleet. This is an orchestration role, not a specialization.

Universal Pilot Certification:

Complete basic Vertex training.
Complete flight school (simulation-based).
Demonstrate proficiency in atmospheric flight, zero-G/space flight, VTOL operations, emergency procedures, ITN-assisted navigation, and weapons employment (all types).
Pass a live-flight evaluation in at least three different airframes.
Receive peer evaluation from certified pilots.

Universal Flight Systems Operator Certification:

Complete basic Vertex training.
Complete flight systems school (simulation-based).
Demonstrate proficiency in sensor operation, EWAR operation, flight systems monitoring, ITN data interpretation, and target identification and tracking.
Pass a live-flight evaluation in at least two different airframes.
Receive peer evaluation from certified operators.

Group 9: Special Operations (SOF) — "The Shadows"

Philosophy: SOF are the best Vertexes. Every Operator is a complete soldier first. Specialization is about mission type, not job title. An Operator is expected to be a marksman, a medic, a demolitions expert, a linguist, and a network master all in one. The title is irrelevant. The capability is everything.

Code	Job Title	Description	Monthly Stipend	Monthly MWC
SOF-01	Operator	The baseline SOF soldier. Capable of all aspects of unconventional warfare. The "Swiss Army Knife" of the HCAF.	+7 Ɱ	+7 Ɱ
SOF-02	Senior Operator	An experienced Operator. Mentors junior Operators. Serves as a specialist advisor on complex missions.	+10 Ɱ	+10 Ɱ
SOF-03	Team Leader	Leads a 4 to 6 Operator team. The tactical orchestrator for SOF operations. A temporary, mission-specific role, not a permanent rank.	+13 Ɱ	+13 Ɱ

What about SOF command? An Operator with AUTH-4 orchestrates a detachment. An Operator with AUTH-5 orchestrates a squadron. An Operator with AUTH-6 orchestrates a group. An Operator with AUTH-9+ directs SOF command. There is no "Command Director" specialization. There is a Senior Operator with AUTH-9+ who happens to be directing SOF command this campaign.

SOF Entry Requirements:

Minimum 3 years service in any specialization.
Physical fitness test (95th percentile).
Psychological evaluation.
Selection course (6 months).
Qualification training (12 to 18 months).
Must already be a certified Vertex.

Group 10: Command/Orchestration (CMD) — "The Decision Makers"

Philosophy: The ITN eliminates the need for traditional command hierarchies. An Orchestrator's job is to interpret intent and orchestrate the network, not to micromanage subordinates. Orchestrators issue goals. The network and its Vertexes execute the path.

Command is not a career. It is a temporary responsibility.

Critical Note: This group is NOT a specialization. It describes temporary, mission-specific roles that any Vertex with the appropriate AUTH code can fill. It is included here for reference, but it should not be treated as a career track.

Code	Job Title	Description	Minimum AUTH	Duration
CMD-01	Orchestrator	Temporary, mission-specific orchestration of any-sized element. Assembles the team, issues intent, monitors the network, takes responsibility for outcomes, dissolves when the mission ends.	AUTH-3 to AUTH-10	Mission duration
CMD-02	Intent Authority	Sets strategic goals for a theater, campaign, or operation. Does NOT command. Does NOT micromanage.	AUTH-8 to AUTH-11	Campaign duration
CMD-03	Intent Council	Council of senior Vertexes who set Coalition-wide strategic goals. Elected by peers.	AUTH-9+	Fixed term (2 years)

Note: Orchestration roles do not carry additional stipend or MWC. The compensation is already reflected in the AUTH code and specialization. An Orchestrator is paid for their AUTH code and specialization, not for the temporary role they fill.

What an Orchestrator Does:

Receives Commander's Intent from higher authority.
Queries the ITN for available Vertexes with relevant specializations and qualifications.
Assembles the optimal team.
Issues intent, not orders.
Monitors the network and adjusts as needed.
Takes responsibility for outcomes.
Dissolves the role when the mission ends.

What an Orchestrator Does NOT Do:

Does not have permanent authority over anyone.
Does not have a rank.
Does not have a career track.
Does not have subordinates. They have collaborators.
Does not command. They orchestrate.

8. Qualifications

Qualifications in the HCAF do not represent competency. Every Vertex is already competent in the full range of standard Coalition military operations: network integration, small arms proficiency, basic field medicine, environmental adaptation, and cross-species communication. These are not qualifications. They are expectations.

A qualification, therefore, represents something outside the standard doctrinal envelope. It is a skill that is:

Highly Specialized: Beyond the scope of normal Vertex training.
Often Absurd: The kind of thing that makes other soldiers say "...why do you even know how to do that?"
Situationally Useful: The military won't train everyone in it, but it's valuable to have someone who can do it.
Self-Earned: Usually acquired through personal interest, prior civilian life, or serendipitous experience, not formal military schooling.

The only formal qualifications the HCAF officially recognizes are those that require certification for safety or legal reasons. These are rare and include, among others:

Qualification	Monthly Stipend	Monthly MWC	Why It's Formal
Reactor Certification	+2 Ɱ	+2 Ɱ	Safety-critical. Required to operate or maintain fusion reactors.
Instructor Certification	+1.5 Ɱ	+1.5 Ɱ	Quality-control. Required to train other personnel.
Command Override Authorization	+3 Ɱ	+3 Ɱ	Operational-critical. Required to issue orders that contradict standard doctrine.

Non-standard qualifications do not carry a direct stipend or MWC supplement. Instead, they feed into the Qualification Index (QI), which provides its own stipend and MWC supplement (see Section 9). A Vertex with a rating-5 in an anomalous qualification earns more through their QI than they would through a flat per-qualification supplement.

Examples of Legitimate (Non-Standard) Qualifications

Qualification	What It Actually Means	Why It's a Qualification
Anti-Matter Confectionery	Can bake a cake using anti-matter ingredients without causing a catastrophic explosion.	Because no one is trained in this. This soldier learned it in a past life as a civilian chef on a research station. The military finds it useful for diplomatic functions and morale events.
Zero-G Parkour Specialist	Can navigate complex zero-gravity environments with acrobatic efficiency.	Every Vertex can move in zero-G. This soldier can do it fast, silently, and without thrusters. Useful for boarding actions, salvage, and EVA sabotage.
Xenopsychology (insert species)	Deep understanding of non-Human concepts. Can interpret subtle social cues and avoid diplomatic incidents.	Every Vertex gets cultural sensitivity training. This soldier has lived with the species and can navigate their social structures with native-like fluency.
Improvised Ordnance Engineering	Can build functional explosives, traps, or weapons from scavenged materials.	Standard doctrine relies on standardized munitions. This soldier can build a bomb from a microwave, a plasma cell, and a roll of duct tape. Useful behind enemy lines.
Pathological Liar	Can maintain a false identity under interrogation, polygraph, and even neural scan.	Standard training includes resistance to interrogation. This soldier is naturally gifted at deception and has honed the skill to supernatural levels. Useful for deep-cover operations.
Gastronomic Alchemist	Can synthesize edible, nutritious meals from any organic matter, regardless of origin or toxicity.	Every Vertex knows how to operate a food replicator. This soldier can turn alien fungus, recycled protein slurry, and... other things... into a gourmet meal. Useful in logistics failures or long-term survival scenarios.
Chaos Theory Practitioner	Can predict the behavior of anomalous phenomena with better than-random accuracy.	Standard training covers anomaly identification and reporting. This soldier has an intuitive grasp of the patterns within chaos and can anticipate anomaly behavior. Useful for research station security.
Improvised Medical Prosthetics	Can create functional, if crude, prosthetics from scrap materials.	Standard medical training covers stabilization and evacuation. This soldier can build a working replacement limb from a MUV's suspension strut and a damaged HUD visor. Useful for long-term deployment far from proper medical facilities.
Hive Mind Immunity	Can resist psychic or memetic influence that would overwhelm normal soldiers.	Standard training covers memetic resistance. This soldier has an unusually strong will or a neurochemical quirk that makes them immune to certain types of mental manipulation. Useful against enemies like the Void Imperium or certain psychic aliens.
Synthetic Empathy	Can communicate with and gain the trust of synthetic sapiens (AIs, cyborgs, KMIF avatars) more effectively than baseline soldiers.	Standard training covers interaction with synthetics. This soldier has an intuitive understanding of synthetic psychology and can build rapport where others create distrust. Useful for joint operations with KMIF assets or negotiating with rogue AIs.
Plasma Pulse Tuning	Can adjust plasma weaponry to perform optimally in non-standard atmospheric or gravitational conditions.	Standard training covers weapon maintenance. This soldier can hear the plasma's frequency and tune it on the fly. Useful for operations in unusual environments.

How Qualifications Are Used

Personnel File: A soldier's qualifications are listed in their personnel file, accessible via the ITN.
Mission Assembly: When a mission is assembled, the Orchestrator or the ITN's AI can review available personnel and select those with relevant qualifications.
Self-Reported: Qualifications are typically self-reported and then peer-verified. A soldier claiming "Improvised Medical Prosthetics" would be expected to demonstrate the skill to their squad leader.
Not Required: No soldier needs a qualification. The baseline Vertex is sufficient for 95% of operations. Qualifications are the spice, not the meal.
Subject to the Actual's Discretion: The designated Actual for a mission has the final say on whether a claimed qualification is valid and relevant. If the Actual says "we don't need a pathological liar for this routine patrol," the qualification is irrelevant.

In short: The HCAF doesn't issue qualifications. It recognizes them. And the strangest, most niche, most absurd qualifications are often the most valuable, because they represent skills that cannot be trained, only discovered.

9. The Qualification Index

The Qualification Index (QI) is a single number, calculated monthly by the ITN, that represents the total value of a Vertex's qualifications. It is not a rank. It is not a certification. It is a measure of a Vertex's versatility and specialization. It feeds into compensation, mission assignment, and recognition.

The Two Dimensions

The QI is calculated from two independent scores:

Breadth: How many qualifications a Vertex holds, and how diverse they are.
Depth: How developed each qualification is, based on peer assessment and demonstrated use.

The final QI is weighted so that depth matters more than breadth. The HCAF values mastery. A Vertex with one deeply developed qualification is more valuable than a Vertex with five shallow ones. But breadth matters too. A Vertex who can do many things is more flexible, and flexibility is the HCAF's core doctrine.

Breadth

Breadth measures how many qualifications a Vertex holds, adjusted for diversity. The formula uses a square root to prevent hoarding. The first qualification is the most valuable. The tenth is marginal.

Qualifications are grouped into categories. A Vertex with qualifications spread across many categories is more versatile than a Vertex with all their qualifications in one category. The diversity multiplier reflects this.

Depth

Each qualification is rated on a scale of 1 to 5, from Novice to Master. Ratings are assigned through a combination of self-reporting, peer verification, ITN-logged usage, and Certification Board review for higher ratings.

Each qualification is also weighted by its category. A rating-5 in anti-matter confectionery is impressive, but it is not the same as a rating-5 in xenopsychology or plasma pulse tuning. The weighting reflects the strategic value of the skill to the HCAF.

The Qualification Categories

For the purpose of breadth and depth, qualifications are grouped into five categories:

Mundane: Hobbies, crafts, cooking, sports, arts, entertainment. Morale-positive and socially valuable, but not mission-critical.
Professional: Engineering, logistics, administration, law, medicine, education. The backbone of the HCAF's support structure.
Combat: Weapons, tactics, survival, demolitions, sniping, hand-to-hand. The core of the HCAF's warfighting capability.
Xenological: Alien species, cultures, languages, biology, psychology. Essential for a multi-species force operating across the galaxy.
Anomalous: Bluespace, plasma, resonance, memetics, chaos theory. Rare, dangerous, and strategically vital.

How QI Affects Compensation

The QI feeds into both the stipend and the MWC. A higher QI means a higher monthly supplement to both. The exact formulas are not published. The ITN calculates them. Vertexes know their QI, know their supplement, and know that improving their qualifications improves their compensation. That is enough.

The QI supplement is higher for the MWC than for the stipend. Qualifications are often tied to hobbies and personal development. A Vertex who has mastered anti-matter confectionery is likely to spend their MWC on high-quality ingredients and equipment. The MWC supplement supports that.

How QI Is Used

The QI is used for compensation, mission assignment, and recognition. It is not a competition. Vertexes talk about their QI the way civilians talk about their education. It is a point of pride, but not a defining characteristic. The HCAF encourages Vertexes to develop their qualifications. It provides time, resources, and training for any Vertex who wants to deepen their skills or learn new ones.

The ideal Vertex is both broad and deep. They have several qualifications across multiple categories, and at least one qualification at rating 4 or higher. They are the universal soldier. Capable of anything, master of something.

10. Branch Designations

Branch Code	Branch Name	Liaison Title
ITF	Integrated Tactical Forces	ITF Liaison
HCSF	Heliostatic Coalition Starfleet	HCSF Liaison
HAC	Heliostatic Aerospace Corps	HAC Liaison
HSOD	Heliostatic Special Operations Division	HSOD Liaison
HLSC	Heliostatic Logistics & Sustainment Corps	HLSC Liaison

Note: Liaisons represent their branch to Unified High Command and don't command.

11. The Certification Authority

The HCAF uses certification, not promotion. To maintain consistent standards across the Coalition, the HCAF uses a Certification Authority.

How It Works

The Certification Authority is a standing body responsible for maintaining certification standards across the Coalition.
It is composed of senior Vertexes (AUTH-8+) from each specialization group.
It sets certification criteria for each AUTH code and specialization.
It audits Certification Boards to ensure consistency.
It can revoke certifications if a Vertex fails to maintain proficiency.
It is accountable to the Strategic Council.

Key Principles

The Certification Authority ensures consistency. An AUTH-4 in one branch meets the same standards as an AUTH-4 in another.
The Certification Authority is a bottleneck. It is slower than decentralized certification. It ensures consistency.
The Certification Authority is accountable. It reports to the Strategic Council.

12. Compensation & Incentives

The HCAF has no ranks, no promotions, and no career progression in the traditional sense. To motivate Vertexes, the HCAF uses a Compensation and Incentive System.

The Core Principle: The HCAF Provides

The HCAF is not a job. It is a total institution. A Vertex does not need to buy anything essential. They need to request it, and the request is granted if it serves the mission, the network, or the Vertex's ability to function.

The rule of thumb: If it helps you do your job, it's issued. If it helps you live your life, it's provided. If it's purely personal, you buy it with your stipend.

What the HCAF Provides

The HCAF provides everything a Vertex needs to function, and most of what they need to live. This includes food (replicators and mess halls, with species-specific and medical diets on request), housing (barracks, ship berths, or subsidized apartments, with family housing for dependents), clothing (uniforms, specialized gear, and dress uniforms as needed), healthcare (universal, comprehensive, including mental health, prosthetics, genetic care, and resurrection for all species and ages), education (full tuition for Vertexes and their dependents at any Coalition institution), transportation (a depot-nanoforge-printed air car for AUTH-2+, specialized vehicles as duty kit, free public transit, and arranged long-distance travel for personal reasons), communication (ITN access and personal comms), childcare (free or subsidized), legal services (the ORG-03 Legal Officer handles Coalition law and personal legal matters at no cost), and financial services (the Morozov Matrix administers the Soft Mark ledger with no fees or minimums).

What the HCAF does not provide: personal weapons, luxury vehicles, real estate, investments, or anything the ITN determines is not morale-positive. These are purchased with the stipend.

The Stipend

The stipend is real currency. It can be saved, withdrawn, transferred, sent home, invested. It is paid monthly in Soft Marks. It is calculated as:

Stipend = Base Stipend + AUTH Supplement + Specialization Supplement + Formal Qualification Supplement + QI Supplement

Base Stipend: 5 Ɱ/month for all certified Vertexes. 2 Ɱ/month for Candidates in training.
AUTH Supplement: See Section 6. Ranges from +0 Ɱ (AUTH-1) to +475 Ɱ (AUTH-11).
Specialization Supplement: See Section 7. Ranges from +0 Ɱ (CBT-01) to +13 Ɱ (SOF-03).
Formal Qualification Supplement: See Section 8. Reactor Certification (+2 Ɱ), Instructor Certification (+1.5 Ɱ), Command Override Authorization (+3 Ɱ).
QI Supplement: Calculated by the ITN. Not published.

The Morale & Welfare Credit

The MWC is a monthly allowance of non-transferable, non-drawable credit. Use it or lose it. It resets on the first of the month. It is calculated as:

MWC = Base MWC + AUTH MWC + Specialization MWC + Formal Qualification MWC + QI MWC Supplement

Base MWC: 6 Ɱ/month for all certified Vertexes. 3 Ɱ/month for Candidates in training.
AUTH MWC: See Section 6. Ranges from +0 Ɱ (AUTH-1) to +80 Ɱ (AUTH-7+, capped).
Specialization MWC: See Section 7. Matches the stipend supplement for each specialization.
Formal Qualification MWC: See Section 8. Matches the stipend supplement for each formal qualification.
QI MWC Supplement: Calculated by the ITN. Not published.

The Deployment Supplement

For Vertexes deployed outside Coalition space for more than 90 consecutive days:

Deployment Supplement: +5 Ɱ/month to Stipend.

This is not combat pay. It is a cost-of-living adjustment. It applies to everyone in the theater, from the newest AUTH-1 to the senior-most Intent Authority.

Additional Benefits

Housing Stipend Option: A Vertex can opt to receive a housing stipend instead of provided housing. 10 Ɱ/month for AUTH-1 to AUTH-3, 20 Ɱ/month for AUTH-4 to AUTH-6, 40 Ɱ/month for AUTH-7+.

Retirement: After 20 years of certified service, a pension equal to 40% of the Vertex's highest AUTH supplement. After 30 years, 60%. After 40 years, 80%. Paid for life.

Survivor Benefits: If a Vertex is killed in action, their designated dependents receive a lump-sum payment of 1,000 Ɱ plus a monthly stipend equal to 50% of the Vertex's total compensation for 20 years. If the Vertex was AUTH-5 or higher, the stipend is paid for 30 years.

Postmortem Care: If a Vertex's template survives but their body is destroyed, the HCAF pays for resurrection. If the Vertex elects not to return, their estate receives survivor benefits.

13. The Morale & Welfare Credit

The Morale and Welfare Credit (MWC) is a monthly allowance of non-transferable, non-drawable credit. Use it or lose it. It resets on the first of the month. This is wellbeing, not wealth.

What It Is

Every Vertex receives a monthly MWC deposit into a separate ledger account. The MWC cannot be:

Withdrawn as cash
Transferred to another person
Converted to Marks
Saved beyond the current month
Used for anything the ITN determines is not morale-positive

How Much?

The MWC is calculated as:

MWC = Base MWC + AUTH MWC + Specialization MWC + Formal Qualification MWC + QI MWC Supplement

See Section 12 for the full breakdown. The base MWC is 6 Ɱ/month for all certified Vertexes. AUTH and specialization supplements are listed in their respective tables. The QI supplement is calculated by the ITN and not published.

Note: The MWC caps at 80 Ɱ for AUTH-7 and above. Higher AUTH codes receive additional stipend instead. The reasoning is simple: a senior Intent Authority has less need for subsidized entertainment than a junior Vertex. They can afford to pay for their own recreation. The MWC is a morale tool, not a wealth tool.

Where Can It Be Spent?

On-site establishments: Bars, cafes, restaurants, recreation facilities, entertainment venues, hobby shops, libraries, and media centers.

Off-site approved vendors: Restaurants, bars, cafes, streaming and media subscriptions, concert and sports and event tickets, hobby and craft stores, bookstores, art galleries, personal care services, travel and tourism (within Coalition space).

Digital services: Streaming platforms, game subscriptions, VR environments, music and audiobook services, online courses (hobbies, not career).

What it cannot be spent on: Weapons (personal, non-issue), vehicles, real estate, investments, anything the ITN flags as not morale-positive.

The AI and the "No" Factor

The ITN's morale subsystem is not a separate AI. It's a function of the same network that tracks everything else. It has been running for centuries. It has been debugged, tweaked, and refined across millions of Vertexes and billions of transactions.

What it does:

Tracks spending patterns across the entire HCAF
Identifies purchases that correlate with improved morale, productivity, and network performance
Identifies purchases that correlate with declining morale, isolation, or self-destructive behavior
Flags anomalous spending for review
Provides vendors with a simple approve/deny signal for MWC transactions

What it doesn't do:

It doesn't read your mind
It doesn't know why you want something
It doesn't judge your character
It doesn't punish you for wanting things

The vendor's role: Vendors who accept MWC are not passive. They can see the ITN's signal. If the ITN flags a transaction as "not morale-positive," the vendor can refuse.

Example: A Vertex wants to buy a bottle of expensive whiskey with their MWC. The ITN approves. Whiskey is a legitimate morale purchase. Moderate consumption correlates with relaxation and social bonding. The same Vertex next week wants to buy twelve bottles. The ITN flags it. The vendor sees the flag. The vendor can refuse. Not because the Vertex is forbidden from buying whiskey, but because the pattern suggests a problem. The vendor might say, "I'll sell you one bottle. Come back next month." Or they might say, "I'm not comfortable with this sale. Let's talk." The Vertex can still buy the whiskey with their stipend. The stipend has no morale restrictions. The MWC is a subsidized system, and subsidized systems have rules.

The cultural norm: Most Vertexes accept the system. It's been part of the HCAF for centuries. The ITN's morale subsystem is not seen as a surveillance tool. It's seen as a care tool. The Coalition provides for its Vertexes. The MWC is part of that provision. The rules exist to ensure the provision actually helps.

A Vertex who games the system, by buying MWC-eligible items and reselling them or by exploiting vendor relationships, is caught quickly. The ITN tracks patterns. Vendors report anomalies. The consequences are administrative, not criminal, but they're real.

Why This Works

It Removes the "Should I Spend This?" Anxiety: A Vertex doesn't have to decide whether a night out is "worth it." The MWC is there. It resets next month. If they don't spend it, they lose it.
It Subsidizes the Things That Actually Help: Bars, restaurants, hobbies, streaming services, gyms, social events. These are the things that keep people sane. The HCAF doesn't want Vertexes sitting in their barracks, staring at the wall, saving their Marks for a rainy day that may never come.
It Separates Wealth from Wellbeing: A Vertex's stipend is their wealth. The MWC is their wellbeing. It can't be hoarded. It's a monthly reminder that the HCAF cares about whether they're actually living, not just surviving.
It Gives Vendors a Role: Vendors aren't just passive recipients of MWC. They're gatekeepers. They can refuse a sale. They can suggest alternatives. They can talk to a Vertex who seems to be struggling. This creates a human layer on top of the AI's pattern matching.
It Creates a Culture of Care: The MWC is not charity. It's not a bonus. It's a structural part of HCAF service. Every Vertex gets it. Every Vertex knows it's there. It's not something you have to ask for.

There's a cultural expectation in the HCAF that Vertexes use their MWC. A Vertex who hoards their MWC is seen as slightly odd. Not wrong, but odd. The MWC is there to be used. Using it is part of being a Vertex.

Vendors who refuse MWC sales are respected. They're seen as doing their job. A vendor who sells twelve bottles of whiskey to a Vertex who's clearly struggling is not respected. If a Vertex is flagged repeatedly, the system doesn't punish them. It talks to them. A welfare officer (SVC-05) will check in. A mental health specialist (MED-04) might schedule a conversation. The goal is not to catch the Vertex doing something wrong. The goal is to figure out what's actually going on. A Vertex who repeatedly tries to buy large quantities of alcohol is flagged. The welfare officer talks to them. It turns out their partner just left them. They're not an alcoholic - they're heartbroken. The welfare officer connects them with a counselor. The problem is addressed.

The MWC and the Guild Mark

The MWC is denominated in Soft Marks, but it's not real Marks. It's a separate ledger. When a Vertex spends MWC at an approved vendor, the vendor receives real Marks from the HCAF. The MWC is simply a mechanism for allocating the HCAF's morale and welfare budget.

This means:

The MWC doesn't affect the Mark's value. It's not "money in circulation."
The MWC doesn't affect the labor ledger. It's not compensation. It's a provision.
The MWC is a line item in the HCAF's budget. It's the cost of keeping Vertexes sane.

The HCAF's morale and welfare budget is enormous. Billions of Vertexes, each receiving a monthly MWC, adds up. But the HCAF considers it essential. A Vertex who is miserable, isolated, or self-destructive is a liability. A Vertex who is engaged, social, and happy is an asset. The MWC is an investment in the latter.

Part Three: Operational Doctrine

14. Nested Intent Hierarchies

The HCAF's flat structure is excellent for small-unit operations. For large-scale conventional warfare, the HCAF uses Nested Intent Hierarchies. These are layers of intent-setting that translate theater-level goals into tactical action without creating a chain of command.

How It Works

Theater Intent Authority sets theater-level goals. "Secure the transit corridor."
Corps Intent Authority interprets that goal and sets corps-level intent. "Secure the three jump points along the corridor."
Division Intent Authority interprets that and sets division-level intent. "Take Node Alpha, hold Node Bravo, recon Node Echo."
Brigade Intent Authority interprets that and sets brigade-level intent. "1st Regiment takes Alpha, 2nd holds Bravo, 3rd recons Echo."
Orchestrators assemble teams and execute.

Key Principles

Intent Authorities are not commanders. They don't issue orders. They set goals. The Orchestrators below them decide how to achieve those goals.
Intent Authorities are temporary. They're assigned for a campaign or operation, not permanently. When the operation ends, they dissolve.
Intent Authorities are selected by the ITN and confirmed by the Strategic Council. The network identifies who is best suited to interpret intent at each level based on certification, experience, and demonstrated judgment. The Strategic Council, or a sub-panel thereof, confirms the selection.
Intent Authorities can be challenged. If an Intent Authority is making poor decisions, subordinate Orchestrators can flag a challenge. A peer review panel composed of other Intent Authorities and senior Orchestrators resolves it.

Standing Intent: The ITN pre-loads standing intent for common scenarios. If the enemy does X, the standing intent is Y. This allows for faster responses without centralized decision-making.

15. Persistent Clusters

Plug-and-play units don't build the deep bonds that sustain soldiers through combat. The HCAF uses Persistent Clusters. These are semi-permanent groupings of Vertexes who train and deploy together for extended periods.

How It Works

Persistent Clusters are semi-permanent groupings of Vertexes who train and deploy together for extended periods. Six to twelve months. They train together, deploy together, and build cohesion over time.
When a mission requires a different composition, the ITN can draw from multiple Persistent Clusters. The Persistent Cluster remains as a home base. They return to it after the mission.
The ITN tracks shared experience. If two Vertexes have served together before, the network knows it.
The ITN prioritizes keeping Persistent Clusters together for high-risk missions. Splitting them up is a last resort, not the default. When a mission is routine or low-risk, the ITN may draw from multiple clusters to fill specialized roles. When a mission is high-risk or requires maximum cohesion, the ITN deploys a Persistent Cluster intact.

Key Principles

Persistent Clusters build cohesion. They provide the stability and shared experience that combat requires.
Persistent Clusters are not permanent. They exist for 6 to 12 months, then dissolve. Vertexes can request reassignment.
Persistent Clusters are flexible. The ITN can break them up for specific missions.
Persistent Clusters are voluntary. Vertexes can request assignment. The ITN matches requests to needs.

16. Standing Defensive Clusters

Holding ground requires discipline, cohesion, and the willingness to stay in place under fire. The HCAF uses Standing Defensive Clusters. These are semi-permanent groupings of Vertexes assigned to hold a specific position for a specific duration.

How It Works

Defensive Clusters are semi-permanent groupings of Vertexes assigned to hold a specific position for a specific duration. They stay together for weeks or months.
The ITN still manages the network, but the Cluster's composition is stable. The Cluster's Actual is designated by the ITN at the start of the deployment and remains the Actual for the duration, unless incapacitated.
When the deployment ends, the Cluster dissolves. Vertexes return to the general pool.

Key Principles

Defensive Clusters are temporary. They exist for a deployment, not a career.
Defensive Clusters are mission-specific. They're formed to hold a position, not to be a permanent unit.
Defensive Clusters are still plug-and-play. If a Vertex is killed or injured, the ITN can slot in a replacement.
Defensive Clusters build cohesion through shared experience. Even if they dissolve afterward, the bonds formed during deployment are real.

17. Reserve Pool & Rotational Deployment

Attrition warfare requires units to absorb casualties and continue fighting. The HCAF uses a Reserve Pool and Rotational Deployment to sustain combat operations over time.

How It Works

The Reserve Pool is a standing body of Vertexes who are not currently assigned to a mission. They train, maintain proficiency, and wait for assignment.
Rotational Deployment means that units in combat are rotated out after a set period, typically 30 days, and replaced by fresh units from the Reserve Pool.
The ITN tracks everything. It knows who is available, what their certifications are, and when they last deployed. It can assemble replacement units in hours, not days.
The Actual designation transfers automatically. If a unit's Actual is killed, the ITN reassigns the designation. If the unit is so depleted that it can't function, it's rotated out entirely and replaced.

Key Principles

Rotation breaks cohesion. The ITN compensates, but there's a cost. The cost is measured in lives. The HCAF accepts this cost because the alternative, keeping units in combat until they break, is worse.
Defensive Clusters can be maintained for longer durations. Rotational Deployment is for offensive operations where adaptability matters more than cohesion.
The Reserve Pool is deep. The HCAF maintains enough trained Vertexes to replace losses without compromising the network.
The Reserve Pool exists because the HCAF expects to take casualties. It is not a question of if. It is a question of how many and how fast.

18. The Analog Layer

The HCAF assumes the ITN always works. This does not mean it is complacent. If the network goes down, the Analog Layer activates. This is a redundant, non-network command structure that allows the HCAF to function without the ITN.

How It Works

Every unit has a pre-designated Analog Actual. This is a Vertex who is trained to lead without the network. They're chosen before the mission, not by the network.
Every Vertex carries an Analog Protocol Card. This is a physical card or implanted chip that contains:
- The unit's chain of command, who to follow if the network is down.
- The unit's standing intent, what to do if the network is down.
- The unit's rally points and fallback positions.
- The unit's authentication codes, how to verify orders without the network.
The Analog Layer is trained regularly. Units practice operating without the network. This is not a stopgap. It's a core competency.
The Analog Layer has its own command structure. It's a pre-designated sequence of who takes over if the person above them is incapacitated.

Key Principles

The Analog Layer is not a practical necessity. It is a cultural one. In the history of the HCAF, there has never been a theater-wide ITN failure. Local failures occur, and the Analog Layer handles them. But the HCAF trains for total network loss anyway, because the Coalition was founded by people who learned the hard way that the systems you depend on can fail.
The Analog Layer is independent. It doesn't rely on technology. It relies on training and pre-designation.
The Analog Layer is simple. It can't adapt to changing circumstances in real-time. It's a fallback, not a replacement.
The Analog Layer is always active. Even when the ITN is working, the Analog Layer is maintained.

19. Distributed Architecture

The HCAF assumes the ITN always works. To prevent the network from becoming a single point of failure, the HCAF uses a Distributed Network Architecture.

How It Works

The ITN is a mesh network, not a centralized system. Every Vertex is a node. If one node goes down, the network routes around it.
Every Vertex carries a local cache of critical data. This includes standing intent, rally points, authentication codes, and the unit's chain of command.
The network can operate in dark mode. If the network is compromised, it can switch to low-emission, line-of-sight, or courier-based communication.
The Analog Layer is always active. Even when the ITN is working, the Analog Layer is maintained.

Key Principles

A mesh network is more resilient than a centralized system. A single point of failure becomes a distributed system.
A mesh network is more complex. It requires more power, more bandwidth, and more maintenance. But for a military that depends on the network, that's a worthwhile investment.
The Analog Layer is the ultimate fallback. If the mesh network fails, the Analog Layer takes over.

20. Orchestration Roles

The HCAF separates specialization (what you're trained to do) from orchestration (what scope you're certified to lead). Orchestration roles are temporary, mission-specific, and assigned by the ITN. They are not specializations. They are not career tracks.

The Orchestration Roles

Role	What It Is	Minimum AUTH	Duration
Actual	Ultimate decision-making authority for a tactical unit. Assigned by the ITN based on mission needs.	Any (ITN designated)	Mission duration
Orchestrator	Assembles and coordinates a unit. Issues intent, monitors the network, takes responsibility for outcomes.	AUTH-3 to AUTH-10	Mission duration
Intent Authority	Sets strategic goals for a theater, campaign, or operation. Does not command. Sets intent.	AUTH-8 to AUTH-11	Campaign duration
Intent Council	Sets Coalition-wide strategic goals. Elected by peers.	AUTH-9+	Fixed term (2 years)

How Orchestration Roles Differ from Command

Orchestrators do not have permanent authority. When the mission ends, the role dissolves.
Orchestrators do not have subordinates. They have collaborators. Every Vertex in the unit is a peer who has agreed to follow the Orchestrator's intent for the duration of the mission.
Orchestrators do not have a career track. There is no "promotion" to Orchestrator. There is only the temporary assignment of the role when the mission requires it.
Orchestrators are accountable to peer review. If an Orchestrator abuses their authority, any Vertex can flag it. A peer review panel determines whether the Orchestrator's actions were justified.
Orchestrators have assignment authority, not administrative authority. They decide who goes on this mission. They do not decide pay, discipline, or permanent assignment.

What an Orchestrator Does:

Receives Commander's Intent from higher authority.
Queries the ITN for available Vertexes with relevant specializations and qualifications.
Assembles the optimal team.
Issues intent, not orders.
Monitors the network and adjusts as needed.
Takes responsibility for outcomes.
Dissolves the role when the mission ends.

What an Orchestrator Does NOT Do:

Does not have permanent authority over anyone.
Does not have a rank.
Does not have a career track.
Does not have subordinates. They have collaborators.
Does not command. They orchestrate.

Part Four: Governance & Justice

21. The Strategic Council

The HCAF has an Intent Council (CMD-03) that sets Coalition-wide strategic goals. To ensure accountability and transparency, the HCAF uses a Strategic Council.

How It Works

The Strategic Council is composed of senior Intent Authorities from each branch. ITF, HCSF, HAC, HSOD, HLSC. Plus elected representatives from the Vertex pool.
The Council sets Coalition-wide strategic goals. It doesn't command. It sets intent.
The Council is elected by peers. Senior Vertexes (AUTH-9+) elect the Council members. The Council serves for a fixed term, typically 2 years, and can be recalled by a vote of no confidence.
The Council has no operational authority. It sets goals. Orchestrators and Intent Authorities execute them.
The Council is transparent. All deliberations are logged in the ITN. Any Vertex can review them.

Key Principles

The Council provides collective leadership. No single person has ultimate authority.
The Council is accountable to peers. Members can be recalled by a vote of no confidence.
The Council is transparent. All deliberations are logged in the ITN.
The Council can delegate crisis authority. In a crisis, the Council can delegate authority to a single Intent Authority. This is a temporary measure.

22. Authority Tracks

The HCAF separates authority into three tracks, each with its own structure. This prevents any single track from becoming a chain of command.

Track	Authority	Who Holds It	What It Covers
Operational	The Actual	Designated by ITN for each mission	Tactical decisions during a mission
Administrative	The Facilitator	ORG-06 or equivalent	Pay, personnel, assignments, disputes
Legal	The Legal Officer	ORG-03	Courts-Martial, legal disputes, Coalition law

How It Works

Operational authority is temporary and mission-specific. The Actual is in charge during a mission. When the mission ends, the Actual designation dissolves.
Administrative authority is permanent but limited. The Facilitator handles paperwork, personnel data, and assignments. They don't command. They administrate.
Legal authority is permanent and independent. The Legal Officer handles legal matters. They don't command. They adjudicate.

23. Peer Review

The HCAF does not have a permanent chain of command. Disputes are resolved through Peer Review.

Peer Review Panel

Composition: Three Vertexes selected randomly from the pool of available personnel.
Qualifications: Must hold relevant certification. For example, AUTH-3 or higher for disputes involving squad-level operations.
Duration: Serves for the duration of the dispute, then dissolves.
Conflict of Interest: No one can serve on a panel that reviews a dispute involving someone they've served with in the last 6 months.

What the Panel Does

Reviews challenges to Actual designations.
Reviews challenges to Orchestrator designations.
Reviews disputes between Vertexes.
Reviews refusals to follow orders.
Determines whether a refusal was justified.
Has the authority to reassign Actual and Orchestrator designations.
Has the authority to recommend administrative consequences, not operational ones.

Administrative Consequences

Infraction	Consequence
Refusing a lawful order	Peer review determines if refusal was justified. If not, administrative consequence such as loss of certification or reassignment. If the refusal occurred in combat and resulted in casualties, the consequences are severe.
Insubordination	Peer review. If upheld, administrative consequence.
Dereliction of duty	After-action review flags it. Certification board reviews. Certification may be suspended. Dereliction of duty in combat is treated as a potentially criminal matter.
Cowardice	After-action review flags it. Peer review determines context. Administrative consequence.
Treason	Legal Officer handles it. Courts-Martial still exist for Coalition law.

24. Legal Authority

Military law still exists. It is handled by a separate track.

Role	What It Does
Legal Officer (ORG-03)	Handles Coalition law, Courts-Martial, legal disputes.
Administrative Technician (ORG-01)	Handles paperwork, appeals, personnel data.
Peer Review Panel	Handles operational disputes.
Certification Board	Handles certification decisions.

Legal authority is separate from operational authority. A Legal Officer does not command. They adjudicate. A Peer Review Panel does not punish. They determine facts. The system handles consequences separately.

Courts-Martial exist for Coalition law. The HCAF is not above the law. Vertexes who commit crimes, whether murder, assault, theft, treason, or dereliction of duty under fire, are subject to legal consequences. The Legal Officer handles these cases. The fact that the HCAF is a military does not exempt it from justice. It subjects it to a higher standard.

Part Five: Reference

25. Commonly Achieved Timeframes

Disclaimer: The following is an immensely averaged "Soldier Joe" for reference only. This is not a career path. It is a statistical snapshot of a hypothetical Vertex who joins the HCAF, serves competently, takes the opportunities presented to them, and achieves certifications at a "typical" pace. Actual Vertexes may progress faster or slower depending on talent, drive, luck, and the needs of the service. Some Vertexes achieve AUTH-5 in five years. Some never seek certification above AUTH-1. Both are valid paths. This section exists purely to give players and writers a sense of scale and pacing.

The Soldier Joe Profile

Who They Are Before Joining

Soldier Joe is a citizen of the Heliostatic Coalition. They grew up on a Core world, a Mid-world, or a Rim-world. They attended Coalition-standard schooling, which included basic ITN literacy and physical education. They are not a super-soldier. They are not a genius. They are a reasonably fit, reasonably intelligent, reasonably motivated person who decided to serve. They have probably never killed anyone. They have probably never seen anyone die.

Why They Joined

Civic Duty: The Coalition's culture of collective survival and Unificationism makes military service a respected and meaningful career.
Economic Opportunity: The HCAF offers stable pay, housing, education, and a clear path to advancement via certification.
Personal Ambition: Some want to travel, see the galaxy, learn a trade, or test themselves.
Family Tradition: Many Coalition families have a history of service.

What Basic Training Was Like

Not a Meat Grinder: HCAF basic training is not designed to break recruits down and rebuild them. It is designed to assess, teach, and integrate.
Network Integration is the First Test: Recruits are immediately introduced to the ITN. Recruits who cannot handle the cognitive load are flagged for additional training or reassigned to non-network-intensive roles.
Physical Fitness is Expected, Not Exceptional: The standard is "fit enough to do the job," not "special forces fit." Soldiers who struggle are given additional training, not discharged.
Specialization is Chosen, Not Assigned: At the end of basic training, recruits choose their specialization based on aptitude, interest, and the needs of the service.
The "Vertex" Identity: The most important lesson of basic training is that you are not an individual. You are a node in a network. Your value is not just what you can do. It is what you can enable others to do.
The Reality of Combat: Basic training includes simulated combat. Recruits are taught what it looks like when a person dies. Some recruits wash out at this stage. Not because they can't handle the physical demands. Because they can't handle the reality of what they're being trained to do.

The Average Timeline

Year 0–1: Basic Training and AUTH-1

Completes basic Vertex training.
Achieves AUTH-1, certified to operate independently within Commander's Intent.
Chooses a specialization, such as CBT-01 Skirmisher.
Completes advanced individual training in specialization.

What They Can Do: Operate as a basic infantryman, technician, or support specialist. Follow orders. Report data. Be a reliable node. Kill the enemy when ordered to.

What They Still Struggle With: Complex tactical decision-making. Leading others. Handling high-stress, high-data environments without support. The first time they kill someone. The first time they see someone die.

Year 1–3: AUTH-2 and Early Experience

Assigned to a Persistent Cluster.
Deploys on 3 to 5 missions. Patrols, security details, minor engagements.
Achieves AUTH-2, certified to orchestrate a fireteam of 2 to 4 Vertexes.

What They Can Do: Lead a small team in a limited scope. Make tactical decisions within a clear intent. Handle moderate data loads. Make decisions that result in people dying.

What They Still Struggle With: Larger-scale coordination. Anticipating enemy actions. Managing complex logistics. Interacting with other branches. Dealing with the aftermath of a firefight.

Common Mistakes: Over-reliance on the ITN. Micromanaging subordinates. Failing to adapt when the plan goes wrong. Freezing under fire.

Year 3–6: AUTH-3 and Specialization Growth

Achieves AUTH-3, certified to orchestrate a squad of 8 to 16 Vertexes.
May have qualified for a second specialization.
Has likely served in a Defensive Cluster for a 6-month deployment.
Has probably experienced at least one major engagement or crisis.

What They Can Do: Lead a squad effectively. Coordinate with other squads. Manage a small unit's logistics and personnel. Mentor junior Vertexes. Make decisions that determine whether the mission succeeds and whether the people under their command come home alive.

What They Still Struggle With: Company-level operations. Strategic planning. The political dimensions of coalition warfare. The weight of responsibility. The memories of the people who didn't come home.

Common Mistakes: Becoming too attached to "their" squad. Resisting mission-based reassignment. Over-identifying with their specialization. Letting the pressure get to them.

Year 6–12: AUTH-4 and Professionalization

Achieves AUTH-4, certified to orchestrate a platoon of 20 to 40 Vertexes.
Has likely served in multiple Persistent Clusters and Defensive Clusters.
May have completed a secondment to another branch.
Is considered a senior Vertex. Is trusted to operate with minimal supervision.

What They Can Do: Orchestrate a platoon in complex operations. Coordinate with company-level assets. Train junior Vertexes. Serve as an Intent Authority for small operations.

What They Still Struggle With: Battalion and higher operations. Strategic vision. High-level coalition politics. The cumulative weight of command.

Common Mistakes: Believing their own hype. Becoming inflexible. Failing to recognize when a situation requires a different approach. Becoming callous.

Year 12–20: AUTH-5 and Senior Leadership

Achieves AUTH-5, certified to orchestrate a company of 80 to 160 Vertexes.
Has likely served in multiple theaters.
Has a broad network of peers.
May be selected for a role as an Intent Authority (CMD-02) for a campaign or operation.
Is a mentor and role model for junior Vertexes.

What They Can Do: Orchestrate a company in sustained operations. Manage large-scale logistics. Coordinate with other branches. Set intent for subordinate Orchestrators. Serve as a liaison to Unified High Command.

What They Still Struggle With: Theater-level strategy. Fleet operations. The complexities of Coalition politics. The loneliness of command.

Common Mistakes: Becoming too distant from the "on-the-ground" reality. Over-delegating. Losing touch with the Vertex culture. Forgetting that war is not a game. It is a tragedy.

Year 20–30: AUTH-6+ and Strategic Influence

Achieves AUTH-6, certified to orchestrate a battalion of 400 to 800 Vertexes.
Continues to advance through AUTH-7 (Regiment), AUTH-8 (Brigade), and beyond.
Serves as a senior Intent Authority, a member of the Strategic Council, or a Certification Authority board member.

What They Can Do: Set strategic goals for entire theaters. Shape the future of the HCAF. Mentor the next generation of leaders. Navigate the complexities of Coalition governance.

What They Still Struggle With: Nothing is beyond their scope of certification. What they struggle with is the same thing every leader struggles with: the limits of their own judgment, the unpredictability of chaos, and the weight of responsibility.

A Note on "Common Mistakes"

Even the best Vertexes make mistakes. The HCAF does not expect perfection. It expects adaptive correction. A Vertex who makes a mistake, reports it honestly, and adjusts is infinitely more valuable than a Vertex who hides their mistakes to protect their certification.

The ITN logs everything. There is no hiding. The culture of the HCAF is built on the principle that data discipline, including honest self-reporting, is the most important quality a Vertex can possess. A mistake that is reported immediately can be corrected. A mistake that is hidden can get people killed.

A Soldier Joe who fails to report a mistake will face peer review and administrative consequences. A Soldier Joe who reports a mistake immediately and takes corrective action will be respected for their integrity and will likely be promoted, certified for higher AUTH, faster than one who is "perfect" but dishonest.

Ст. 30 из 30 22.09.2026, 15:08

Work in Progress: Footer subject to change at a moment's notice. Do not take a red link's presence, struck-through or otherwise, as confirmation (or denial) of their canonicity.

Nova Sector Lore
	Common Species	Humans, Tiziran, Unathi, Moths, Azulae (Ceruleans), Slime Hybrids, Vox (Primalis et al), Tajaran, Synthetic Humanoids (and assorted robots), Pod Persons (Colonial Seed Vaults), Hemophages, Xenomorphic Hybrid
	Other Species	Genemodders (Felinids, Ice Walkers), Ashwalkers, Ethereals, Snailpersons, Teshari, Dwarf, Ordoht (Formerly Skrell), Plasmamen, Flypeople, Vulpkanin, Rouges (Abductorkin), Kobolds, Miscellaneous Species, Dullahans, Employee Golems, Ghouls, Changelings, Shadekin, Proteans, Ghouls
	Nanotrasen	Nanotrasen, Central Command, Emergency Response Corps
	SolFed	SolFed, Sol in 2566, The SolFed Armed Forces Notable Member States: Libraen Federation, Nanotrasen Government: Voting Cliques (Plasma Clique), Voting in SolFed
	External Groups	Heliostatic Coalition (HC CompactThe HC Constitution, the document formally defining the HC., HCAFHeliostatic Coalition Armed Forces (Ranks), CZDCommonwealth of Zvirdnyn Dominions, KMIFKemppainen-Morozov Industrial Fabrication, Expeditionary Police ForceHC's Cops (InspectorsThe Expeditionary Force. They inspect more than stations. (Quick Reference, SOPStandard Operating Procedure, LexiconLingo, chatter guide, manner of speaking.))), Interdyne Pharmaceutics, Cargo, MECU, Colonial Seed Vaults
	Hostiles	The Syndicate (Gorlex, Tiger Cooperative, DS-2, Syndicate Manifestos), The Void Imperium, The Spider Clan, Changelings
	Nova	The Nova Sector, IndecipheresLavaland, volcanic mining place., FreyjaIcebox and Snowglobe station frozen moon., BoletusSerenity Mushroomoon.
	Concepts	Bluespace, Plasma, Faster Than Light Travel, Resonance ("Souls"), Death, Timeline of Events in the Lore

Lore:HCAF Ranks

Table of Contents

Part One: Foundations

Part Two: Personnel Systems

Part Three: Operational Doctrine

Part Four: Governance & Justice

Part Five: Reference

Part One: Foundations

1. Note on Rank Equivalents

2. Note on the ITN

3. Note on the "Actual"

How It Works

Pre-Mission Transparency

Degraded-Mode Protocols

4. The Vertex

5. Plug-and-Play Vertexes

Key Principles

Part Two: Personnel Systems

6. Authority Codes

How AUTH Codes Work

AUTH Code Table

Certification Requirements

7. Specialization Groups

The General Principle

Group 1: Combat (CBT) — "The Teeth"

Group 2: Engineering (ENG) — "Build It, Break It, Power It"

Group 3: Logistics (LOG) — "Move It, Store It, Track It"

Group 4: Maintenance (MAI) — "Keep It Running"

Group 5: Service (SVC) — "Support the Fighters"

Group 6: Organizational/Bureaucratic (ORG) — "The Paperwork Warriors"

Group 7: Medical (MED) — "Heal the Fighters"

Group 8: Aviation (AV) — "The Skyriders"

Group 9: Special Operations (SOF) — "The Shadows"

Group 10: Command/Orchestration (CMD) — "The Decision Makers"

8. Qualifications

Examples of Legitimate (Non-Standard) Qualifications

How Qualifications Are Used

9. The Qualification Index

The Two Dimensions

Breadth

Depth

The Qualification Categories

How QI Affects Compensation

How QI Is Used

10. Branch Designations

11. The Certification Authority

How It Works

Key Principles

12. Compensation & Incentives

The Core Principle: The HCAF Provides

What the HCAF Provides

The Stipend

The Morale & Welfare Credit

The Deployment Supplement

Additional Benefits

13. The Morale & Welfare Credit

What It Is

How Much?

Where Can It Be Spent?

The AI and the "No" Factor

Why This Works

The MWC and the Guild Mark

Part Three: Operational Doctrine

14. Nested Intent Hierarchies

How It Works

Key Principles

15. Persistent Clusters

How It Works

Key Principles

16. Standing Defensive Clusters

How It Works

Key Principles

17. Reserve Pool & Rotational Deployment

How It Works

Key Principles

18. The Analog Layer

How It Works

Key Principles

19. Distributed Architecture

How It Works