Loading this page.
Preparing content, navigation, and supporting references for this route.
Preparing content, navigation, and supporting references for this route.
A model for how extraction, transport, storage, transformation, and redistribution create stability or fragility in a world system.
Use this when a concrete mechanism in Flow And Logistics needs to behave coherently instead of only sounding plausible.
IntroductoryRead Surplus first, then return here once the surrounding concept stack is clear.
SurplusResources do not matter only at the point of origin. Their systemic importance comes from how reliably they move and how many institutions depend on that movement.
The loop model tracks extraction, transport, storage, transformation, and redistribution as one chain.
Identify where the system first captures grain, ore, timber, or other strategic material.
Map the roads, ports, and storage nodes that keep output alive long enough to matter elsewhere.
Show how workshops, tax systems, rationing, or markets turn raw material into usable power and political leverage.
| Axis | Question | Signal |
|---|---|---|
| Extraction | Where does material enter the system? | Mines, fields, forests, fisheries |
| Transport | How does it move? | River barges, caravans, roads, ports |
| Storage | Where is surplus buffered? | Granaries, depots, cisterns, vaults |
| Transformation | How is raw material converted into usable power? | Mills, workshops, foundries, tax systems |
| Redistribution | Who receives the output and under what logic? | Markets, tribute, rationing, elite capture |
The model gets more useful once resources stop being treated as a pile of stuff and start being treated as an exposed chain. A fertile basin, rich mine, or magical grove is not yet system-wide power. It becomes system-wide only when output survives extraction, transport, storage, conversion, and release often enough that many actors begin depending on it. That is why shortages often appear far from the source and why political panic can arrive even while production still looks healthy on paper.
This also explains why the loop belongs in worldbuilding rather than in narrow economic simulation. The route between stages determines settlement ranking, fiscal depth, military tempo, and urban stability. The more institutions lean on the same loop, the more every interruption becomes structurally visible.
Power usually enters where material becomes countable, delay-sensitive, or capturable. Storage nodes matter because they concentrate surplus. Transformation matters because it changes raw material into bread, weapons, wages, or taxable output. Redistribution matters because it decides who feels scarcity first and who can stay insulated. Once those gates are explicit, the model can explain why some states govern through granaries, others through toll roads, and others through industrial conversion or rationing systems.
A world becomes more believable when its shortages come from bottlenecks, seasonal breaks, or political disruption rather than arbitrary scarcity.
The most useful diagnostic move is to ask which stage is easiest to interrupt with the least visible effort. In many settings, transport or storage fails long before extraction does, which is why apparent abundance can coexist with local crisis and political panic.
When reviewing a setting, ask three questions in order. Which stage is easiest to interrupt? Which actor gains the most from controlling that stage? Which populations experience the break first? Those answers usually reveal whether the loop is resilient, monopolized, or politically combustible long before a full crisis is narrated on the page.
The reusable lesson is that resources are system-wide only when their loop remains intact. Use the model to explain why abundance can still feel fragile, why shortages can begin far from the source, and why transport and buffering often matter more than raw deposits.
Check the prerequisite, the strongest relation role, and the next route after the reading is complete.
Start with Surplus and then return here once the surrounding concept stack is clear.
These entries clarify the footing underneath the current node before you move outward again. Start with Regional Systems Matrix when you want the clearest next role.
Return to broader lenses when this model is too specific for the question you are asking.
Use this appendix when you want to continue by program branch or operating scale after the page has been read.
Explain how resources, goods, labor, information, and force circulate, stall, buffer, and break.
Start from the flow architecture framework, test circulation fragility and reserve depth, compare one logistics study, then run a flow audit worksheet.
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.
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 prerequisites when you want the shortest path into the assumptions this page depends on.
Output that remains after immediate subsistence and maintenance needs are covered, making storage, exchange, taxation, or concentrated reinvestment possible.
Read firstStorage NodeA location where flow is buffered, accumulated, protected, measured, or redirected strongly enough to change who can control the wider system.
These groups explain why each neighboring entry matters, whether it stabilizes the concept, operationalizes it, proves it, or pushes the lane further.
Use foundation relations when this node depends on a concept, term, or framing layer that should be explicit before you branch further.
Use applied relations when the next useful move is to see the current pattern survive inside a study or assembled world.
A sample systems study showing how basin agriculture, defensive ridges, and narrow passes produce a dense but brittle civilization pattern.
ApplyRiver Port PolityA systems study of how estuaries, port warehousing, and toll control create a state that is wealthy, connective, and strategically exposed.
Use extension relations when the next move is not prerequisite or proof, but a deeper neighboring step in the same graph lane.
Models formalize behavior. Use them when you need a concrete chain, loop, stress scenario, or layered mechanism that can be tested and reused.
| Models | Reading use |
|---|---|
| Read for mechanism | A model should explain how something behaves over time or under pressure, not just identify a broad topic area. |
| Use models to pressure-test a draft | When a setting feels plausible at rest but still behaves vaguely, models provide the explicit structure needed to test it. |
| Models bridge frameworks and studies | A strong workflow often moves from broad lens to formal model to applied case reading. |
Keep these collapsed until you want an active reading exercise.
What mechanism is this model making explicit?
modelWhere does this model break or become most interesting under stress?
modelWhich study would verify whether this model survives in a complete setting?
modelThese routes are tuned to the kind of entry you are currently reading, so you can leave this page with one deliberate next move.
Return to broader lenses when this model is too specific for the question you are asking.
Return to broader lenses when this model is too specific for the question you are asking.
Move through the systems module when you want to navigate models by design intent.
Verify the model inside applied cases where multiple structures interact at once.
Use these links for corrections, missing examples, worksheet requests, or confusing sections. Each link includes the current URL, slug, kind, and Program.
Flag a factual issue, unclear claim, typo, or outdated passage.
EmailFlag a broken route, missing media asset, or relation that leads nowhere.
EmailAsk for a proof case, comparison, glossary term, or missing related entry.
EmailRequest a guide output, checklist, audit pass, or creator-facing worksheet.
EmailPoint to a section that needs a clearer explanation or stronger handoff.
Email