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 city already matters on the map, but still does not read as a real transfer machine inside a wider region. It turns the urban branch into one audit route across gateway edge, depot ring, port interface, and service reach.
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 how cities work as filters, gateways, relays, conversion surfaces, and regional control machines.
Start with the urban logistics surface, step into gateway and throughput models, compare a port or capital study, then run a city-region worksheet.
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 strongest explanation depends on several levels staying visible together.
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Use this scale when city-scale transfer, concentration, or control is doing the main structural work.
Use this scale when routes, relays, buffers, and linked nodes matter more than territorial bulk.
Each scenario describes a common structural problem this guide is meant to solve.
Use this when a key city drives trade, politics, or logistics in premise, but still behaves like a symbolic node instead of an operating surface.
Use this when arrival edges are clear yet reserve storage, repair, dispatch, and outward service are still implicit.
Use this when you cannot explain how the city actually serves, taxes, relieves, or stabilizes surrounding production zones.
They are the structural assumptions the rest of the workflow is built on.
Do not let the gateway edge do every job. Name the depot ring, repair surfaces, and transfer layers that keep heavy flow from collapsing the entry point.
A city only becomes regional leverage when cleared movement can leave again through canals, roads, feeder towns, or escort corridors at usable tempo.
Close with a flagship case so the audit tests urban coupling in one complete city-region system instead of private notes alone.
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 cities as transfer surfaces where gateways, districts, depots, servicing radius, and hinterland demand converge into one operational field.
A structural study of how harbor clearance, district specialization, and regional servicing tied Hong Kong to a much larger hinterland than the city itself could physically contain.
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.
City region coupling audit matters because cities become believable when gateway edge, buffer belt, and service reach reinforce one another as one regional machine.