Preparing the current spcent route.
The page shell is online. Shared content and route data are still being assembled.
model
4 failure scenarios turns a model for testing how a spatial layout behaves under congestion, disruption, seasonal shifts, and asymmetric pressure.
Topology Stress Test
A model for testing how a spatial layout behaves under congestion, disruption, seasonal shifts, and asymmetric pressure.
Models4 failure scenariosSpatialSpatial StructuresCross ScaleCore Models3 related
Maps should survive pressure, not only description
A topology may look coherent in calm conditions yet fail as soon as one corridor closes or demand spikes elsewhere.
The stress test model asks what the map does under disruption rather than what the map looks like at rest.
| Axis | Question | Signal |
|---|---|---|
| Closure | What happens if one critical edge becomes unavailable? | Snowed pass, blockaded port, collapsed bridge, insurgent road |
| Surge | What happens when traffic or demand spikes unexpectedly? | Harvest movement, refugee flight, campaign season, pilgrimage load |
| Delay | What changes when movement stays possible but slower? | Mud season, customs drag, convoy shortages, weather windows |
| Asymmetry | Who gains if one actor can move faster than another? | River fleets, mounted patrols, naval control, privileged relay stations |
Why it matters
This model is useful for checking whether a strategic map really produces choke, reroute, and leverage dynamics, or only claims them in prose.
Relation Map
Stress-test adjacencies
Region Graph
Provides the abstract network needed to simulate edge failure and rerouting.
Settlement Corridor StackShows which corridors are likely to bear the heaviest stress when demand shifts.
Frontier Chokepoint LedgerTurns stress-test outputs into a ledger of strategic holding costs and cascade risks.
Transfer value
The reusable lesson is that maps should be judged by disruption behavior, not just by peaceful appearance. Use the stress test whenever a corridor, border, or gateway is supposed to matter strategically and you need to prove that the wider topology really reacts when it is pressured.
It also helps prioritize what deserves detail. Once a map has been stressed, the routes, nodes, and fallback lines that actually change outcomes become obvious, while decorative connections can be safely treated as background texture.
Continuation Map
Use this node as a deliberate step, not a terminal page.
Read what should come before it, what relation role matters next, and where this page should hand you off after the local graph is clear.
2 prerequisites to read first
Start with Region Graph and then return here once the surrounding concept stack is clear.
3 linked nodes to branch into
Use Region Graph or the linked nodes below when you want to compare this page against neighboring parts of the graph.
Open Frameworks
Return to broader lenses when this model is too specific for the question you are asking.
Continue by shared branch or operating scale.
2 handoff nodes stay inside Spatial Structures. No handoff nodes currently share Cross Scale.
Spatial Structures · 2Cross Scale · 0
Graph Taxonomy
Continue from this node by program branch and operating scale.
Detail pages now expose the branch and scale of their surrounding graph before showing raw prerequisite and relation shelves, so continuation can stay taxonomy-led instead of adjacency-led.
Spatial Structures
Explain how topology, region graphs, corridors, map abstraction, and scale determine movement and leverage.
Start in Spatial, reduce the map into region graph and corridor logic, test topology under disruption, then return through a spatial design guide.
Network Scale · 2
Governance and Power
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.
Regional 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 · 1
Show scale lanes
Network Scale
Use this scale when routes, relays, buffers, and linked nodes matter more than territorial bulk.
Regional Scale
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Read First
Open these prerequisite nodes before going deeper.
Use prerequisites when you want the shortest path into the assumptions this page depends on.
Spatial Structures · 2Network Scale · 2
glossary
Node-edge abstraction
Region Graph
A spatial abstraction that represents regions as connected nodes so adjacency, flow, and chokepoints can be reasoned about systematically.
SpatialSpatial StructuresNetworkspatial-structuresystems
glossary
Gateway-dominant structure
Chokepoint Regime
A structural condition in which a small number of passages or gateways determine the behavior of a much larger region or system.
SpatialSpatial StructuresNetworkspatial-structuresystemscivilization
Relation Map
Generic adjacency is still doing all the work here.
This entry still relies on generic related links. That works as a fallback, but typed relation roles would make continuation clearer.
glossary
Node-edge abstraction
Region Graph
A spatial abstraction that represents regions as connected nodes so adjacency, flow, and chokepoints can be reasoned about systematically.
SpatialSpatial StructuresNetworkspatial-structuresystems
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
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
Collection Context
How to read a model
Models formalize behavior. Use them when you need a concrete chain, loop, stress scenario, or layered mechanism that can be tested and reused.
Open collection context
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.
Reading Prompts
Use these questions while reading this node.
Keep these collapsed until you want to turn the page into an active reading exercise.
Open reading prompts
What mechanism is this model making explicit?
Where does this model break or become most interesting under stress?
Which study would verify whether this model survives in a complete setting?
Cross-layer Handoff
Continue from this node into the next useful surface.
These routes are tuned to the kind of entry you are currently reading, so you can leave this page with one deliberate next move.
Open Frameworks
Return to broader lenses when this model is too specific for the question you are asking.
Open next routes
Cross-layer move
Open Frameworks
Return to broader lenses when this model is too specific for the question you are asking.
Cross-layer moveOpen Systems
Move through the systems module when you want to navigate models by design intent.
Cross-layer moveOpen Studies
Verify the model inside applied cases where multiple structures interact at once.