Preparing the current spcent route.
The page shell is online. Shared content and route data are still being assembled.
Guides / Spatial Design
Spatial Design Guide
This guide is for creators whose map needs to become operational. It focuses on adjacency, layered mobility, chokepoints, gateway districts, and city-scale stress tests so space stops being a backdrop and starts driving movement and leverage.
AdjacencyChokepointsGateway districtsStress testing
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.
Program And Scale
Browse this guide by program branch and operating scale.
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.
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 · 4World Scale · 2
Flow and Logistics
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.
Network Scale · 2Regional Scale · 2
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.
Cross-Scale · 3Network Scale · 1
Show scale lanes
Regional Scale
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Cross-Scale
Use this scale when the strongest explanation depends on several levels staying visible together.
Network Scale
Use this scale when routes, relays, buffers, and linked nodes matter more than territorial bulk.
World Scale
Use this scale when the whole world model or planetary constraint pattern should stay visible at once.
Best For
Use this guide in these situations.
Each scenario describes a common structural problem this guide is meant to solve.
The map looks good but decides nothing
Use this when routes, gateway nodes, and region boundaries are still visually present but strategically vague.
Movement logic is missing
Use this when you cannot explain why one corridor matters more than another or what closure would actually do.
The city still behaves like a map icon
Use this when route leverage is clear at region scale, but gateway districts, throughput limits, and service radius are still implicit or decorative.
You need topology before polish
Use this when the next useful revision is abstraction and stress, not more terrain rendering.
Core Principles
These habits make the guide useful instead of ornamental.
They are the structural assumptions the rest of the workflow is built on.
Open guide principles
Abstract before detailing
Reduce the map into nodes, corridors, gateways, and transfer surfaces before worrying about visual completeness.
Test failure, not only calm conditions
A spatial design is only convincing if closure, delay, border friction, and asymmetric speed produce meaningful rerouting behavior.
Reconnect to the world
Spatial logic should still be grounded in settlement density, resource movement, institutional pressure, and the city-scale surfaces that convert regional flow into usable leverage.
Recommended Workflow
Follow these steps in order.
Each step includes a worksheet output and the canonical entries that support it.
01
Workflow Step
Step 1: Frame the world as regions under constraint
Begin with regional structure and terrain gradients. This is the fastest way to replace vague geography with a legible field of density, movement, and settlement potential.
Outcome
You have a structural map of where density can accumulate and why.
Use this when the setting still feels like named places without clear density logic or terrain-driven structure.
You can point to a core zone, a corridor belt, and at least one hard constraint zone without relying on lore names alone.
- Mark the main terrain barriers, basins, coasts, rivers, or passes that structure movement.
- Place the first settlement-density gradient from core zone to edge zone.
- Write one sentence for why each major region can or cannot sustain dense settlement.
If your regions still read like labels on a map, stay in this step. If they read like constraint fields, move into resource flow.
World Foundations currently leads this step with 4 supporting entries.
World Foundations · 4
Regional Scale currently anchors this step with 2 supporting entries.
Regional Scale · 2World Scale · 2
Region Constraint Worksheet
Core Zone: - Name: - Why density holds here: Corridor Belt: - Main route: - What keeps movement reliable: Edge Zone: - Main constraint: - Why density thins out here: Hard Constraint Zone: - Terrain barrier: - What becomes expensive or impossible here:
framework
5 constraint layers
World Constraint Stack
A framework for reading a world from climate rhythm, terrain friction, habitability, circulation, and settlement thresholds before higher-order institutions are added.
WorldsWorld FoundationsWorldgeographyresourcesevolution
framework
Featured4 structural layers
Regional Systems Matrix
A planning frame for mapping how geography, settlement, resources, and transit form a region's structural identity.
WorldsWorld FoundationsRegionalgeographyresourcessystems
framework
4 density bands
Terrain Settlement Gradient
A framework for reading how terrain friction and access gradients shape where settlement density can sustainably accumulate.
WorldsWorld FoundationsRegionalgeographycivilizationresources
model
4 recurring windows
Climate Rhythm Model
A model for how repeating weather and seasonal windows structure labor, harvest timing, travel reliability, and crisis pacing across a world.
WorldsWorld FoundationsWorldgeographyresourcesevolution
Outputs And Return Paths
Leave this guide with a concrete artifact and a next module.
Each step should produce something usable. Open these return routes once the output is clear enough to pressure-test in the next layer.
worlds/region-constraint-worksheet.md
Take the output back into terrain, settlement, corridor, and regional structure once the workflow exposes a weak world layer.
WorldsCheckpoint
You can point to a core zone, a corridor belt, and at least one hard constraint zone without relying on lore names alone.
Return to Worldsspatial/spatial-stress-worksheet.md
Use the output to test route hierarchy, chokepoints, rerouting, and exposure before polishing representation.
SpatialCheckpoint
You can close one edge on the map and explain what reroutes, what stalls, and which actor gains leverage.
Return to Spatialstudies/applied-review-worksheet.md
Use the output to verify the workflow inside one complete case before you add more detail or open more nodes.
StudiesCheckpoint
You can explain a study world through regions, loops, chokepoints, and pressure rather than through chronology alone.
Return to StudiesFeatured Reading
Editorial starting points for this guide.
Use these entries when you want the shortest path into the strongest current examples behind this workflow.
Open featured reading
framework
Featured4 structural layers
Regional Systems Matrix
A planning frame for mapping how geography, settlement, resources, and transit form a region's structural identity.
WorldsWorld FoundationsRegionalgeographyresourcessystems
study
Featured2 chokepoint classes
Mountain Basin Civilization
A sample systems study showing how basin agriculture, defensive ridges, and narrow passes produce a dense but brittle civilization pattern.
Cross ModuleWorld FoundationsRegionalgeographycivilizationresources
Module Tracks
Open the module tracks this guide leans on.
These are the module surfaces you should enter once the guide reveals the next weak layer.
Cross-layer Handoff
Continue from this guide into the wider graph.
Use Studies when the workflow output is ready for case validation, and Archive when you need broader graph orientation before opening more collections.
Open graph handoff routes
Case layer
Open Studies
Compare full settings when you want to test whether this workflow survives contact with complete worlds.
FrameworksOpen Frameworks
Reusable lenses for thinking about structured worldbuilding.
ModelsOpen Models
Explicit systems and dynamics that can be reused or adapted.
StudiesOpen Studies
Applied analyses that show systems operating in context.
GlossaryOpen Glossary
Canonical terms for discussing spatial and systemic design.
Graph layerOpen Archive
Browse across modules and collections when you want a wider traversal after this guide.
Search layerOpen Search
Search the current knowledge graph directly when you already know the concept you need next.
Spatial design matters because movement, reach, and leverage only become legible when the map is tested as an operational structure.