Preparing the current spcent route.
The page shell is online. Shared content and route data are still being assembled.
The page shell is online. Shared content and route data are still being assembled.
This guide is for creators whose wars, patrol systems, frontier defenses, or relief pushes already have pieces on the board but still lack one disciplined operations audit. It turns the conflict branch into a repeatable stress route across projection, sustainment, tempo, recovery, and holding burden.
Common starting situations this guide is designed to resolve.
Ordered stages currently recommended for this guide.
Canonical entries currently surfaced as the guide's reading base.
This guide now keeps program branches and scale lanes visible inside the workflow surface, so the next step stays aligned with the same branch-and-scale model used across the rest of the site.
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.
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.
Explain how legitimacy, coercion, administrative reach, frontier bargaining, and elite control are structured.
Start with the pressure map, locate legitimacy and capture mechanisms, validate against a frontier or state case, then run a governance stress test.
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Use this scale when the strongest explanation depends on several levels staying visible together.
Use this scale when routes, relays, buffers, and linked nodes matter more than territorial bulk.
Use this scale when city-scale transfer, concentration, or control is doing the main structural work.
Each scenario describes a common structural problem this guide is meant to solve.
Use this when forces can arrive, fight, and take ground in premise, but the design still does not pay repeated operational costs.
Use this when forts, patrols, or corridors exist, but reserve timing, relief routes, and rotation burden are still vague.
Use this when the useful question is not battle flavor, but what closes the operating window or turns success into overextension.
They are the structural assumptions the rest of the workflow is built on.
The audit starts by checking whether projected force can stay supplied, sequenced, and recoverable long enough to matter more than once.
Any line, garrison, or campaign that comes under pressure needs an explicit relief corridor, reserve path, or fallback node instead of generic support language.
End with a case that proves how victory, rotation, reserve release, and holding costs interact under sustained load.
Each step includes a worksheet output and the canonical entries that support it.
Then follow how substrate continuity becomes movement, storage, capture, and political leverage. This is where resources stop being background detail and become the engine of the world.
You can explain prosperity, fragility, and authority through moving surplus and the material base that keeps reproducing it.
Use this when prosperity, scarcity, or authority in the draft world still depend on vague abundance rather than traceable flow.
You can name where surplus is produced, where it concentrates, and which institution benefits when the chain stays open.
If the economy still depends on vague abundance, keep refining this step. If the loop has bottlenecks and capture points, move into spatial stress testing.
Flow and Logistics currently leads this step with 2 supporting entries.
Cross-Scale currently anchors this step with 4 supporting entries.
Critical Resource: - Type: - Origin region: Flow Chain: - Extraction: - Transport: - Storage: - Redistribution: Capture Point: - Institution controlling the flow: - How value is claimed: Failure Mode: - What breaks first: - Who loses leverage:
A framework for reading how food, water, health, and maintenance cycles must keep reproducing beneath settlement, surplus, and political order.
A framework for mapping how flow, capture, legitimacy, coalition strain, and force sustainment combine into one escalating system rather than separate mechanics.
A model for tracing how staples, fuel, fodder, labor conversion, and storage create the recurring intake that makes density and surplus possible.
A model for how extraction, transport, storage, transformation, and redistribution create stability or fragility in a world system.
A model for tracing how raw inputs become processed components, standardized output, and scalable capability through conversion bottlenecks rather than simple extraction.
A model for how raw surplus becomes taxable, storable, and politically controllable through successive layers of capture.
A model for how material capture becomes durable rule only when extraction, justification, and visible order remain coupled strongly enough to be tolerated.
Each step should produce something usable. Open these return routes once the output is clear enough to pressure-test in the next layer.
Use the output to revise flow, capture, escalation, and institutional pressure instead of widening the setting surface.
You can name where surplus is produced, where it concentrates, and which institution benefits when the chain stays open.
Return to SystemsUse the output to test route hierarchy, chokepoints, rerouting, and exposure before polishing representation.
You can close one edge on the map and explain what reroutes, what stalls, and which actor gains leverage.
Return to SpatialUse the output to verify the workflow inside one complete case before you add more detail or open more nodes.
You can explain a study world through regions, loops, chokepoints, and pressure rather than through chronology alone.
Return to StudiesUse these entries when you want the shortest path into the strongest current examples behind this workflow.
A model for how extraction, transport, storage, transformation, and redistribution create stability or fragility in a world system.
A sample systems study showing how basin agriculture, defensive ridges, and narrow passes produce a dense but brittle civilization pattern.
A framework for reading campaigns, patrol regimes, relief pushes, and theater control through projection, sustainment, tempo, recovery, and control burden rather than battle moments alone.
A synthetic study of how fortress belts, granary release, garrison rotation, and corridor choke points turn frontier warfare into a reserve and timing problem.
These are the module surfaces you should enter once the guide reveals the next weak layer.
Use Studies when the workflow output is ready for case validation, and Archive when you need broader graph orientation before opening more collections.
Compare full settings when you want to test whether this workflow survives contact with complete worlds.
FrameworksReusable lenses for thinking about structured worldbuilding.
ModelsExplicit systems and dynamics that can be reused or adapted.
StudiesApplied analyses that show systems operating in context.
GlossaryCanonical terms for discussing spatial and systemic design.
Graph layerBrowse across modules and collections when you want a wider traversal after this guide.
Search layerSearch the current knowledge graph directly when you already know the concept you need next.
Operational stress test matters because conflict becomes structurally convincing only when projection, recovery, and holding burden can all survive repeated pressure.