Preparing the current spcent route.
The page shell is online. Shared content and route data are still being assembled.
Spatial / Maps
Maps
Map design is about choosing the right abstractions, layers, and visual priorities for the question being asked. A useful map reveals structure. A decorative map often hides it.
LayersAbstractionReadabilitySemantic emphasis
Operational lenses currently organizing this topic.
Curated stages that turn this topic into a usable sequence.
Entries currently surfaced as the topic's reading base.
Program And Scale
Browse this topic by program branch and operating scale.
This topic now keeps program branches and scale lanes visible inside the module, so local reading paths can stay aligned with the same branch-and-scale language used elsewhere.
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 · 4Network Scale · 1
Urban and Regional Coupling
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.
Urban Scale · 2District 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 · 2
Show scale lanes
Cross-Scale
Use this scale when the strongest explanation depends on several levels staying visible together.
Regional Scale
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Urban Scale
Use this scale when city-scale transfer, concentration, or control is doing the main structural work.
District Scale
Use this scale when internal city geometry or gateway-district filtering is the level that matters most.
What It Governs
This topic gives the module a usable operational frame.
Maps matter when representation makes bottlenecks, density, route hierarchy, and contested space easier to reason about.
Layer Choice
Not every map should show everything. Decide whether terrain, routes, ownership, or throughput is primary.
Abstraction Level
Pick the coarseness that preserves strategic meaning without drowning the viewer in noise.
Symbol Hierarchy
Make important nodes, corridors, and thresholds visually dominant.
View Purpose
A planning map, player map, logistics map, and lore map may need different truths emphasized.
Featured Reading
Editorial starting points inside this topic.
Use these entries when you want the strongest current examples before opening the full reading path.
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
framework
Featured4 urban surfaces
Urban Logistics Surface Framework
A framework for reading cities as transfer surfaces where gateways, districts, depots, servicing radius, and hinterland demand converge into one operational field.
SpatialUrban And Regional CouplingUrbanspatial-structuresystemsgeography
Curated Reading
Readings for converting spatial structure into legible representation
These entries help maps inherit structural meaning instead of only visual detail.
01
Reading Stage
Stage 1: Decide what structure the map must reveal
Start with region, graph, and abstraction models to choose the right spatial layers.
Outcome
You know what the map is for before styling it.
Spatial Structures currently leads this stage with 3 supporting entries.
Spatial Structures · 3World Foundations · 1
Cross-Scale currently anchors this stage with 2 supporting entries.
Cross-Scale · 2Network Scale · 1
model
5 semantic layers
Semantic Map Layering
A model for separating terrain, routes, ownership, throughput, and risk into deliberate visual layers so a map answers one structural question clearly.
SpatialSpatial StructuresCross Scalespatial-structuregeography
model
4 abstraction passes
Map-To-Graph Abstraction Model
A model for reducing a full map into a small graph of meaningful nodes, edges, weights, and transfer surfaces without losing the questions that matter operationally.
SpatialSpatial StructuresCross Scalespatial-structuresystems
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
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
Grounding Route
Ground maps in operational readability.
Use maps when representation needs to carry the structural truth. The next move is to decide what the map must reveal and which spatial terms the legend should support.
Decide which terrain and route layers stay visible.
Return to world structure when the map still lacks a clear hierarchy of cores, corridors, and edge zones.
Make the legend match the model.
Use route and region vocabulary to keep the visual layer aligned with actual movement and throughput logic.
Check whether the view still reveals leverage under pressure.
A useful map should still expose dominant paths and substitutes once disruption enters the scene.
model
5 semantic layers
Semantic Map Layering
A model for separating terrain, routes, ownership, throughput, and risk into deliberate visual layers so a map answers one structural question clearly.
SpatialSpatial StructuresCross Scalespatial-structuregeography
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
Design Checklist
Use these prompts to keep the page actionable.
Open this when you want to pressure-test the topic instead of browsing for orientation.
Open the topic checklist
- What decision should this map help someone make?
- Which relationships need to be seen at a glance?
- Which details are actively harming readability at this scale?
- Test whether the main bottlenecks stand out visually.
- Check if color, symbols, and line weight match actual system importance.
- Make sure overlays do not erase the map's core question.
- Full-detail maps used for questions that need abstraction.
- Important route hierarchy hidden under decorative terrain detail.
- No distinction between regions, nodes, and edges.
Cross-model Handoff
Carry representation choices into related spatial modules
Map views depend on the underlying graph, geometry, and simulation scope.
Underlying structure
Topology
Open topology when the representation is only a surface of deeper connectivity rules.
Regular abstractionHex
Use hex layouts when distance and zone control need regular tactical discretization.
Tile logicGrid
Use grids when orthogonal movement and tile-based simulation are the real design drivers.
Scale viewWorld Slicing
Open slicing when the map must support operational segmentation and scale management.
Maps matter because representation is what determines whether spatial structure is obvious, hidden, or misleading.