Preparing the current spcent route.
The page shell is online. Shared content and route data are still being assembled.
Systems / Combat
Combat Systems
Combat systems model how force is assembled, projected, resisted, and exhausted. The point is not only weapon lists or faction flavor. The point is to explain how distance, supply, coordination, morale, and terrain convert force into outcomes.
Force projectionTempoCounterplayAttrition
Operational lenses currently organizing this topic.
Curated stages that turn this topic into a usable sequence.
Entries currently surfaced as the topic's reading base.
Program And Scale
Browse this topic by program branch and operating scale.
This topic now keeps program branches and scale lanes visible inside the module, so local reading paths can stay aligned with the same branch-and-scale language used elsewhere.
Conflict and Operations
Explain campaigns, sustainment, force projection, defensive depth, and operational windows as structural systems.
Start with sustainment and projection models, identify the theater cycle, validate through an operational case, then run an operations stress test.
Regional Scale · 4
Flow and Logistics
Explain how resources, goods, labor, information, and force circulate, stall, buffer, and break.
Start from the resource-flow loop, trace storage and throughput models, compare one logistics study, then run a flow audit worksheet.
Network Scale · 2Cross-Scale · 1Regional Scale · 1
World Foundations
Explain what the world is materially built from before politics, balance, or style are discussed.
Start in Worlds, read the anchor framework, open one regional model, validate with a complete study, then finish with a world assembly guide pass.
Regional Scale · 2
Show scale lanes
Regional Scale
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Network Scale
Use this scale when routes, relays, buffers, and linked nodes matter more than territorial bulk.
Cross-Scale
Use this scale when the strongest explanation depends on several levels staying visible together.
What It Governs
This topic gives the module a usable operational frame.
Combat becomes structural when it reveals who can fight effectively, where, for how long, and at what systemic cost.
Engagement Logic
Define what starts a fight, what counts as range or contact, and what information actors have when committing force.
Sustainment
Model supply, reserve depth, reinforcement time, and recovery windows rather than treating every battle as self-contained.
Counterplay
A healthy combat model makes strengths legible and also makes their failure conditions legible.
Strategic Cost
Ask what combat consumes from the wider world: transport capacity, treasury, legitimacy, manpower, or corridor security.
Featured Reading
Editorial starting points inside this topic.
Use these entries when you want the strongest current examples before opening the full reading path.
Open featured reading
model
Featured5-stage loop
Resource Flow Loop
A model for how extraction, transport, storage, transformation, and redistribution create stability or fragility in a world system.
SystemsFlow And LogisticsNetworkresourcessystemsevolution
framework
Featured4 leverage classes
Frontier Chokepoint Ledger
A framework for tracking which passes, ports, narrows, and crossings decide political leverage at the edge of a system.
Cross ModuleGovernance And PowerRegionalspatial-structurecivilizationsystems
study
Featured4 reserve pressures
Synthetic Fortress Granary Frontier War
A synthetic study of how fortress belts, granary release, garrison rotation, and corridor choke points turn frontier warfare into a reserve and timing problem.
SystemsConflict And OperationsRegionalsystemscivilizationgeography
Curated Reading
Readings for force, chokepoints, and pressure behavior
These entries help tie confrontation to terrain, throughput, and institutional strain.
01
Reading Stage
Stage 1: Ground force in route and map structure
Start with corridor logic and topology so force projection has a real spatial substrate.
Outcome
Combat choices become map-dependent instead of abstract.
Conflict and Operations currently leads this stage with 1 supporting entries.
Conflict and Operations · 1Spatial Structures · 1
Regional Scale currently anchors this stage with 2 supporting entries.
Regional Scale · 2Cross-Scale · 1
model
4 projection limits
Force Projection Window
A model for how far and how long force can be projected effectively before supply, delay, terrain, and recovery costs collapse performance.
SystemsConflict And OperationsRegionalsystemsgeographyspatial-structure
model
3 corridor layers
Settlement Corridor Stack
A layered model for understanding how roads, rivers, passes, and market towns align into durable spatial corridors.
WorldsWorld FoundationsRegionalgeographyspatial-structurecivilization
model
4 failure scenarios
Topology Stress Test
A model for testing how a spatial layout behaves under congestion, disruption, seasonal shifts, and asymmetric pressure.
SpatialSpatial StructuresCross Scalespatial-structuresystemsgeography
Proof Surface
Validate combat inside complete pressure fields.
Use studies to check whether force projection, sustainment, and counterplay still hold once chokepoints, institutions, and route exposure come online.
Read one case after the loop is clear.
Use the studies below to test whether this topic still explains behavior once full settings, institutions, and route pressure are present.
Move into space when the loop changes leverage on the map.
Open the linked Spatial route when adjacency, chokepoints, reach, or scale are now carrying the real consequence of this system.
Come back to the system with a concrete failure mode.
After one proof read, identify what breaks first: throughput, counterplay, coordination, or territorial reach.
study
Featured2 chokepoint classes
Mountain Basin Civilization
A sample systems study showing how basin agriculture, defensive ridges, and narrow passes produce a dense but brittle civilization pattern.
Cross ModuleWorld FoundationsRegionalgeographycivilizationresources
study
3 logistics theaters
Three Kingdoms Resource Flow Model
A structural study of how river systems, grain logistics, corridor warfare, and administrative concentration shape Three Kingdoms-style strategy worlds.
SystemsFlow And LogisticsRegionalgeographysystemscivilization
Design Checklist
Use these prompts to keep the page actionable.
Open this when you want to pressure-test the topic instead of browsing for orientation.
Open the topic checklist
- What decides initiative: speed, scouting, terrain access, range, or command quality?
- Where does force degrade first: morale, ammunition, food, fatigue, or reinforcement lag?
- Which units or strategies are powerful only because the surrounding map and supply rules support them?
- Check whether a local victory can become an operational advantage or if it dies at the edge of logistics.
- Test how chokepoints, enclosure, or open corridors change viable force composition.
- Make sure strong tactics create exploitable weaknesses instead of dominant no-cost answers.
- Combat that ignores route security, storage, and reinforcement time.
- Every faction fighting effectively under identical terrain and supply conditions.
- Force projection that scales without administrative or logistical penalty.
Cross-model Handoff
Carry combat logic into adjacent systems
Combat is downstream from economy, territory, and frontier topology.
Supply base
Economy Systems
Open economy when force structure needs a stronger production and sustainment base.
Actor structureFactions & Power
Use faction modeling when conflict depends on coordination, coercion, and political alignment.
Map structureTopology
Switch to spatial modeling when engagement logic is really a chokepoint or adjacency problem.
Territorial substrateGeography Model
Return to world geography when military reach is under-explained by the terrain.
Combat systems matter because force only becomes believable when movement, sustainment, and counterplay obey the same constraints as the rest of the world.