Core idea

Hex space works well when the lattice preserves the world's real corridor logic instead of flattening it into uniform adjacency.

The point of discretization is not to erase geography. It is to compress geography into a playable or legible unit system while keeping the decisive differences between river corridors, open plains, defended crossings, and hard edges intact.

That means a hex lattice should inherit the world first and simplify it second. If the lattice is designed before the corridor system, settlement rhythm, and movement costs are understood, the grid may become tidy while the world itself becomes strategically empty.

Build the lattice from world logic, not empty geometry

Rule 1Set the unit of action

Tie one hex to a real movement or administration budget such as a march day, patrol ring, convoy hop, or district workload.

Rule 2Preserve the route spine

Make rivers, roads, and pass chains legible inside the lattice so major corridors remain more than just a string of equivalent neighbors.

Rule 3Keep frontier asymmetry alive

Encode terrain drag, crossings, and seasonal shifts so some directions are still cheaper, safer, or more durable than others.

Rule 4Show reach clearly

Use the lattice to reveal how influence, escort depth, and border pressure expand outward rather than merely counting distance.

Axis	Question	Signal
Scale fit	What real distance or time does one hex represent?	Campaign turn, march day, patrol radius, supply hop
Corridor retention	How is the main route spine kept visible inside the lattice?	Weighted movement lanes, terrain bands, road-linked hex chains
Reach clarity	How does the lattice make influence readable?	Ring distance, zone overlap, border tension, forward depth
Friction encoding	How are asymmetries kept alive?	Terrain penalties, river crossings, chokepoint hexes, seasonal cost shifts

When the lattice works

The lattice becomes useful when it helps the reader compare territory without hiding why territory differs. A basin core should still look easier to traverse and supply than a march of thin roads, scattered depots, and costly river crossings.

This is also why lattice quality is not measured by symmetry alone. A good lattice lets players or readers quickly understand where movement bunches, where defense compounds, and where expansion stops being cheap. If those judgments disappear, the model has failed even if the map still looks orderly.

Relation Map

Hex-lattice adjacencies

Corridor

Explains the movement spine the lattice must preserve if it is to remain strategically meaningful.

Route Hierarchy

Helps distinguish primary lanes from feeder and fallback movement paths inside the hex field.

Regional Systems Matrix

Provides the regional substrate whose density and infrastructure the lattice is simplifying.

Transfer value

The reusable lesson is that discretization should clarify strategic structure rather than replace it. Hexes work when they make corridor pressure, frontier depth, and movement friction easier to read.

Use this model whenever a world needs spatial compression for gameplay, simulation, or planning, but still has to preserve the deeper differences between core zones, relay chains, and hard territorial edges.