Preparing the current spcent route.
The page shell is online. Shared content and route data are still being assembled.
The page shell is online. Shared content and route data are still being assembled.
A model for encoding local movement, blocking, cover, and exact control inside orthogonal space without losing connection to wider route logic.
Grid space is strongest when local occupancy rules stay connected to the wider network the grid sits inside. Otherwise the grid becomes a self-contained puzzle instead of a spatial system.
The grid is a local precision tool. It can show exact blocking, cover, door control, and firing geometry far better than a regional map, but it should still inherit the logic of the district, corridor, or building network around it.
That inheritance matters because local control only becomes strategically meaningful when it changes something larger: whether a gate remains open, whether a bridge can be crossed, whether a depot entrance can be held, or whether movement through a district slows enough to matter upstream.
Tie each cell to a real action scale so occupancy reflects room, street, lane, or work-space logic.
Show where occupation closes movement entirely and where it only taxes movement or attention.
Use local geometry to explain why some positions sustain control while others only delay entry.
Identify which local cells correspond to gates, bridges, depots, or junctions that matter beyond the immediate scene.
| Axis | Question | Signal |
|---|---|---|
| Tile meaning | What real space or action budget does one cell represent? | Room width, street span, firing lane, work parcel |
| Blocking | How does occupation change available movement? | Closed lanes, stack limits, chokepoint tiles, door control |
| Cover | How is protection distributed locally? | Walls, angles, elevation, hard corners, shielded lanes |
| Network connection | How does local occupancy affect the larger route system? | Bridge tiles, gate rooms, street junctions, depot entrances |
The most important grid cells are rarely generic interior tiles. They are the cells that sit on a wider relation: stair cores, gate rooms, choke corners, street mouths, dock edges, and depot entrances. These are the points where local occupancy starts changing regional throughput and route choice.
This is why grids should not be authored as detached tactical minigames unless detachment is the actual design goal. If a local battle cannot affect corridor continuity, storage access, or territorial reach, the grid may be visually precise while strategically irrelevant.
Shows whether local blocking only inconveniences movement or actually collapses substitute paths.
Force Projection WindowExplains how local occupancy can shorten or sustain operational reach in combat space.
Region GraphKeeps the local grid tied to the larger node-edge structure it belongs to.
The reusable lesson is that orthogonal precision works best when it remains plugged into the wider movement system. A good grid clarifies local leverage instead of isolating local play from the rest of the world.
Use this model for tactical maps, facility layouts, district combat spaces, or work simulations where exact occupation matters but broader route logic still decides the stakes.
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.
Start with Region Graph and then return here once the surrounding concept stack is clear.
Use Route Hierarchy or the linked nodes below when you want to compare this page against neighboring parts of the graph.
Return to broader lenses when this model is too specific for the question you are asking.
3 handoff nodes stay inside Spatial Structures. No handoff nodes currently share Local.
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.
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.
Explain campaigns, sustainment, force projection, defensive depth, and operational windows as structural systems.
Start with sustainment and projection models, identify the theater cycle, validate through an operational case, then run an operations stress test.
Use this scale when routes, relays, buffers, and linked nodes matter more than territorial bulk.
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Use prerequisites when you want the shortest path into the assumptions this page depends on.
A spatial abstraction that represents regions as connected nodes so adjacency, flow, and chokepoints can be reasoned about systematically.
The ranked structure by which some routes function as primary spines while others act as feeder, secondary, seasonal, or fallback paths.
This entry still relies on generic related links. That works as a fallback, but typed relation roles would make continuation clearer.
The ranked structure by which some routes function as primary spines while others act as feeder, secondary, seasonal, or fallback paths.
A model for comparing how many viable substitutes exist between important nodes and how quickly a topology collapses when one edge is lost.
A model for how far and how long force can be projected effectively before supply, delay, terrain, and recovery costs collapse performance.
A spatial abstraction that represents regions as connected nodes so adjacency, flow, and chokepoints can be reasoned about systematically.
Models formalize behavior. Use them when you need a concrete chain, loop, stress scenario, or layered mechanism that can be tested and reused.
A model should explain how something behaves over time or under pressure, not just identify a broad topic area.
When a setting feels plausible at rest but still behaves vaguely, models provide the explicit structure needed to test it.
A strong workflow often moves from broad lens to formal model to applied case reading.
Keep these collapsed until you want to turn the page into an active reading exercise.
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?
These routes are tuned to the kind of entry you are currently reading, so you can leave this page with one deliberate next move.
Return to broader lenses when this model is too specific for the question you are asking.
Return to broader lenses when this model is too specific for the question you are asking.
Cross-layer moveMove through the systems module when you want to navigate models by design intent.
Cross-layer moveVerify the model inside applied cases where multiple structures interact at once.