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 potable water, irrigation, flood control, drainage, and navigability bind settlement density to water management burden.
Use this when a concrete mechanism in World Foundations needs to behave coherently instead of only sounding plausible.
IntermediateRead Climate Rhythm Model first, then return here once the surrounding concept stack is clear.
Climate Rhythm ModelSettlements gather around water, but they also become dependent on different water functions that do not always align. Drinking water, crop water, drainage, flood control, and navigation can reinforce one another in one region and conflict sharply in another.
Hydrology settlement coupling turns water from background scenery into a structural bargain. Dense settlement becomes plausible only when a place can manage the water benefits it concentrates and the water risks it amplifies.
| Axis | Question | Signal |
|---|---|---|
| Potable supply | How does ordinary drinking water remain clean and accessible as density rises? | Springs, cisterns, aquifers, upland catchment, filtration, source protection |
| Productive water | How do crops, mills, fisheries, or pasture draw usable water without exhausting the base? | Irrigation timing, flood retreat farming, reservoir release, canal scheduling, wetland use |
| Protective control | What prevents flood, salinity, stagnation, or erosion from turning concentration into fragility? | Dikes, drainage channels, sluices, sediment clearing, embankments, marsh buffers |
| Navigable movement | How does water become a corridor for transport and administration rather than only a local input? | River ports, tow paths, lock chains, ferry crossings, canal depots, seasonal draft depth |
Which water function fails first when the region scales up or suffers disruption: drinking safety, irrigation timing, drainage, flood control, or navigation? That first failure usually tells you whether the setting is really a river civilization, a floodplain gamble, or an aquifer society pretending to be more stable than it is.
In River Port Polity, river access is not enough on its own; port hierarchy depends on storage, dredging, and flood behavior staying aligned. In Rift Aquifer Theocracy, hidden water security changes both legitimacy and settlement pattern because the aquifer is more politically decisive than surface geography alone. Ming Canal Logistics System is the other useful comparison when hydraulic maintenance and administrative coordination scale together.
The reusable lesson is that settlement around water should be modeled as a coupling between benefits and maintenance, not as free fertility. Once the water functions are separated, deltas, canal belts, oasis systems, and marsh cities become structurally distinct rather than cosmetically different.
Check the prerequisite, the strongest relation role, and the next route after the reading is complete.
Start with Climate Rhythm Model 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 Material Continuity Framework 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.
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 routes, relays, buffers, and linked nodes matter more than territorial bulk.
Use this scale when the strongest explanation depends on several levels staying visible together.
Use this scale when the whole world model or planetary constraint pattern should stay visible at once.
Use prerequisites when you want the shortest path into the assumptions this page depends on.
A model for how repeating weather and seasonal windows structure labor, harvest timing, travel reliability, and crisis pacing across a world.
Read firstRegional Systems MatrixA planning frame for mapping how geography, settlement, resources, and transit form a region's structural identity.
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.
Use extension relations when the next move is not prerequisite or proof, but a deeper neighboring step in the same graph lane.
These entries still matter, but they currently rely on generic adjacency instead of typed continuation semantics.
An assembled example world showing how deep water access, ritual infrastructure, and magical monopoly can produce a theocratic basin state that is rich in control but brittle at its hidden sources.
AdjacentMing Canal Logistics SystemA historical study of how canal transport, grain reserves, courier timing, and administrative corridors helped hold a large imperial system together unevenly.
AdjacentStorage NodeA location where flow is buffered, accumulated, protected, measured, or redirected strongly enough to change who can control the wider system.
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