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.
Guides turns vague world ideas into a usable sequence across Worlds, Systems, Spatial, and Studies.
Frame the region, trace the loop, stress the map, then verify the pattern.
If your focus is clear, pick a track. If not, follow the default workflow below.
8 canonical guide-supporting entries currently sit in the strongest workflow branch.
17 canonical guide-supporting entries currently anchor the dominant operating scale.
Use Guides when you need order and outputs before opening more nodes.
Start here when you need a staged route, worksheet, or clearer revision order.
Use Guides when you need the artifact and next module before you continue.
Use Archive when the workflow is no longer enough but search would still be too early.
Guides now keeps the same program branches and scale lanes visible inside workflow browse, so tracks, audits, and outputs stay aligned with the wider graph.
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.
Explain transition, disturbance, collapse, recovery, and reassembly across eras and stress cycles.
Start with transformation and failure models, trace residue and recovery paths, compare a collapse or successor-order study, then run a failure-mode review.
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.
Use this scale when the strongest explanation depends on several levels staying visible together.
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Use this scale when routes, relays, buffers, and linked nodes matter more than territorial bulk.
Use this scale when city-scale transfer, concentration, or control is doing the main structural work.
Each program path points to the best current route for turning a branch into a creator-facing pass, worksheet, audit, or comparison sequence.
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.
Explain how legitimacy, coercion, administrative reach, frontier bargaining, and elite control are structured.
Start with the pressure map, locate legitimacy and capture mechanisms, validate against a frontier or state case, then run a governance stress test.
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.
Explain how technology, magic, infrastructure, communication, and transformation capacity rewrite baseline constraints.
Start with the operating regime, price the capability through diffusion or monopoly models, compare a regime-rewrite case, then run a capability sanity check.
Explain transition, disturbance, collapse, recovery, and reassembly across eras and stress cycles.
Start with transformation and failure models, trace residue and recovery paths, compare a collapse or successor-order study, then run a failure-mode review.
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.
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.
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.
Turn all major programs into creator-operable workflows rather than leaving them as analysis-only content.
Start in Guides with the workflow framework, choose the role route, open the supporting program branches only as needed, and leave with a worksheet or review artifact.
Guides now also shows what each program still needs next, so workflow design and content production stay aligned.
Start in Worlds, read the anchor framework, open one regional model, validate with a complete study, then finish with a world assembly guide pass.
This branch currently has no planned backlog items in the generated queue.
Start from the resource-flow loop, trace storage and throughput models, compare one logistics study, then run a flow audit worksheet.
This branch currently has no planned backlog items in the generated queue.
Start with the pressure map, locate legitimacy and capture mechanisms, validate against a frontier or state case, then run a governance stress test.
This branch currently has no planned backlog items in the generated queue.
Start in Spatial, reduce the map into region graph and corridor logic, test topology under disruption, then return through a spatial design guide.
This branch currently has no planned backlog items in the generated queue.
Start with sustainment and projection models, identify the theater cycle, validate through an operational case, then run an operations stress test.
This branch currently has no planned backlog items in the generated queue.
Start with the urban logistics surface, step into gateway and throughput models, compare a port or capital study, then run a city-region worksheet.
This branch currently has no planned backlog items in the generated queue.
Start with the operating regime, price the capability through diffusion or monopoly models, compare a regime-rewrite case, then run a capability sanity check.
This branch currently has no planned backlog items in the generated queue.
Start with transformation and failure models, trace residue and recovery paths, compare a collapse or successor-order study, then run a failure-mode review.
This branch currently has no planned backlog items in the generated queue.
Start in Guides with the workflow framework, choose the role route, open the supporting program branches only as needed, and leave with a worksheet or review artifact.
This branch currently has no planned backlog items in the generated queue.
These lanes map directly to real creator roles: author pass, systems audit, world-lead review, or advanced transformation work.
Use this guide when you need a concrete workflow for transformation boundary analysis, cascade propagation, inheritance auditing, and successor-system planning.
Use this guide when the draft has premise and atmosphere, but still needs one reliable structural pass through region, substrate, route, and applied proof.
Use this guide when the question is no longer what systems exist, but whether their loops, chokepoints, and collapse paths are legible enough to design against.
Use this guide when the job is no longer writing one page well, but keeping a larger world program coherent across teams, revisions, and escalating complexity.
Use a guide page when the problem is already clear and you want a tighter route.
Use this guide when you need a first coherent pass through the world and want to avoid building decorative lore on top of weak physical or material structure.
Use this guide when the draft has lots of ingredients but no clear explanation of how they reinforce, balance, or destabilize one another.
Use this guide when you want one flagship operating path across Worlds, Systems, and Spatial before expanding into narrower branches or adding more case detail.
Use this guide when a capital, harbor, or relay city feels important in premise but still lacks visible buffering, dispatch geometry, and hinterland service logic.
Use this guide when force can move and fight in premise, but you still cannot explain whether it can stay effective, reopen pressure after disruption, or hold what it reaches.
Use this guide when a special capability is starting to reshape the setting, but you still cannot tell whether it is decorative, elite-limited, or truly structural.
Use this guide when the problem is no longer whether disruption happens, but how it propagates, when buffers fail, and what narrower order remains afterward.
Use this guide when you need an end-to-end order of operations that ties worlds, substrate continuity, systems, spatial logic, and studies into one repeatable process.
Use this guide when the setting is rich enough to feel convincing in fragments but not yet coherent as a whole.
Use this guide when your map is readable as artwork but not yet readable as structure, especially once decisive cities still feel like abstract points.
Use this guide when the world feels broad on the surface yet still lacks a clear repair target in constraints, flow, node hierarchy, or applied proof.
Use this guide when you need a concrete workflow for transformation boundary analysis, cascade propagation, inheritance auditing, and successor-system planning.
Use this guide when the draft has premise and atmosphere, but still needs one reliable structural pass through region, substrate, route, and applied proof.
Use this guide when the question is no longer what systems exist, but whether their loops, chokepoints, and collapse paths are legible enough to design against.
Use this guide when the job is no longer writing one page well, but keeping a larger world program coherent across teams, revisions, and escalating complexity.
These role guides stay available as dedicated shelves for authors, systems designers, and world leads.
Use this guide when the draft has premise and atmosphere, but still needs one reliable structural pass through region, substrate, route, and applied proof.
Use this guide when the question is no longer what systems exist, but whether their loops, chokepoints, and collapse paths are legible enough to design against.
Use this guide when the job is no longer writing one page well, but keeping a larger world program coherent across teams, revisions, and escalating complexity.
Each lane is already structured as a multi-stage path. Pick the lane before diving deeper.
Start from terrain, settlement, surplus, and civilizational pressure so the world has structural coherence before detail expands.
Primary output: worlds/region-constraint-worksheet.md. Take the output back into terrain, settlement, corridor, and regional structure once the workflow exposes a weak world layer.
Trace loops, surplus capture, institutional pressure, and disruption so the world behaves like a system rather than a list of mechanics.
Primary output: systems/surplus-flow-worksheet.md. Use the output to revise flow, capture, escalation, and institutional pressure instead of widening the setting surface.
Abstract maps into nodes, corridors, and stress scenarios so movement and leverage become legible before visual polish.
Primary output: spatial/spatial-stress-worksheet.md. Use the output to test route hierarchy, chokepoints, rerouting, and exposure before polishing representation.
These clusters keep the main comparison programs visible without widening into the full Archive.
Use this lane when the weak point is substrate, infrastructure, or life-support burden.
A framework for reading how food, water, health, and maintenance cycles must keep reproducing beneath settlement, surplus, and political order.
A model for reading how roads, grids, canals, wards, depots, and maintenance corridors spread capability by enlarging the physical footprint a society must keep repaired.
A historical study of how flood timing, basin irrigation, grain storage, and hydraulic maintenance let a river civilization turn annual renewal into durable state capacity.
A fiction study of how life support, industrial buildout, habitat maintenance, and territorial expansion turn Red Mars into a governance problem before it becomes a mature civilization.
These routes make the output and next module visible before you open the full workflow.
Use this when the setting still feels like named places without clear density logic or terrain-driven structure.
Take the output back into terrain, settlement, corridor, and regional structure once the workflow exposes a weak world layer.
Use this when prosperity, scarcity, or authority in the draft world still depend on vague abundance rather than traceable flow.
Use the output to revise flow, capture, escalation, and institutional pressure instead of widening the setting surface.
Use this when the map looks readable but you still cannot explain which routes matter or how disruption changes behavior.
Use the output to test route hierarchy, chokepoints, rerouting, and exposure before polishing representation.
Use this when the models look coherent in isolation but you need to test whether they survive contact with a complete setting.
Use the output to verify the workflow inside one complete case before you add more detail or open more nodes.
Use this when your world or system question is about era change, systemic break, or successor-order formation rather than baseline coherence.
If the rupture still reads like a vague event list, stay here. If you can name continuity, rupture, and inheritance clearly, move into cascade or rewrite analysis.
Use this when local disruption is visibly changing the wider network and you need to model propagation rather than isolated stress.
If the failure still looks local, return to topology stress. If it now propagates structurally, move into reassembly or rewrite planning.
Use this when collapse or succession has left enough residue that the main question is selective inheritance rather than total destruction.
If inheritance still feels too broad, return to transformation audit. If rewrite needs are clear, move into the reassembly plan.
Use this when the old order has already narrowed enough that the design problem is now coherent reassembly, not complete restoration.
Return to the weakest module in your draft and deepen the successor order there instead of reopening the entire old system at once.
Use this when you want the worksheet first.
Use this when the setting still feels like named places without clear density logic or terrain-driven structure.
Use this when prosperity, scarcity, or authority in the draft world still depend on vague abundance rather than traceable flow.
Use this when the map looks readable but you still cannot explain which routes matter or how disruption changes behavior.
Use this when the models look coherent in isolation but you need to test whether they survive contact with a complete setting.
Use this when your world or system question is about era change, systemic break, or successor-order formation rather than baseline coherence.
Use this when local disruption is visibly changing the wider network and you need to model propagation rather than isolated stress.
Use this when collapse or succession has left enough residue that the main question is selective inheritance rather than total destruction.
Use this when the old order has already narrowed enough that the design problem is now coherent reassembly, not complete restoration.
This is the default path for a new user. Keep the current step in focus instead of reading all four at once.
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.
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.
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.
Regional Scale currently anchors this step with 2 supporting entries.
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:
A framework for reading a world from climate rhythm, terrain friction, habitability, circulation, and settlement thresholds before higher-order institutions are added.
A planning frame for mapping how geography, settlement, resources, and transit form a region's structural identity.
A framework for reading how terrain friction and access gradients shape where settlement density can sustainably accumulate.
A model for how repeating weather and seasonal windows structure labor, harvest timing, travel reliability, and crisis pacing across a world.
Keep two next layers visible: Studies for case validation, Archive for wider graph orientation.