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 Stack

Shows which corridors are likely to bear the heaviest stress when demand shifts.

Frontier Chokepoint Ledger

Turns 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.