Loading this page.
Preparing content, navigation, and supporting references for this route.
Preparing content, navigation, and supporting references for this route.
This guide is for world leads coordinating several contributors, modules, or iteration passes. It turns Spcent into a review cycle: align the inherited constraints, audit the moving substrate, test the city and corridor surfaces, then decide whether the next revision is baseline repair, governance proof transfer, or advanced transformation work.
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.
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.
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 resources, goods, labor, information, and force circulate, stall, buffer, and break.
Start from the flow architecture framework, test circulation fragility and reserve depth, 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.
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 the whole world model or planetary constraint pattern should stay visible at once.
Each scenario describes a common structural problem this guide is meant to solve.
Use this when geography, systems, and case work are all moving and you need one shared review order instead of parallel private intuition.
Use this when the setting stays plausible locally while the overall program starts losing coherence across scales or eras.
Use this when the next release or revision should only widen after the current graph survives one coordinated structural review.
They are the structural assumptions the rest of the workflow is built on.
Constraints, substrate, city-scale surfaces, and transformation risk should be reviewed in order so upper claims still inherit lower realities.
If capitals, ports, or relay cities keep deciding the world program, they need explicit review as transfer machines and service nodes.
The review cycle should distinguish missing baseline structure from true transformation questions, so advanced analysis is used intentionally.
Each step includes a worksheet output and the canonical entries that support it.
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.
Each step should produce something usable. Open these return routes once the output is clear enough to pressure-test in the next layer.
Take the output back into terrain, settlement, corridor, and regional structure once the workflow exposes a weak world layer.
Use the output to revise flow, capture, escalation, and institutional pressure instead of widening the setting surface.
Use the output to test route hierarchy, chokepoints, rerouting, and exposure before polishing representation.
Take the output back into terrain, settlement, corridor, and regional structure once the workflow exposes a weak world layer.
You can point to a core zone, a corridor belt, and at least one hard constraint zone without relying on lore names alone.
Use the output to revise flow, capture, escalation, and institutional pressure instead of widening the setting surface.
You can name where surplus is produced, where it concentrates, and which institution benefits when the chain stays open.
Use the output to test route hierarchy, chokepoints, rerouting, and exposure before polishing representation.
You can close one edge on the map and explain what reroutes, what stalls, and which actor gains leverage.
Use the output to verify the workflow inside one complete case before you add more detail or open more nodes.
You can explain a study world through regions, loops, chokepoints, and pressure rather than through chronology alone.
Use these entries when you want the shortest path into the strongest current examples behind this workflow.
A planning frame for mapping how geography, settlement, resources, and transit form a region's structural identity.
A framework for mapping how flow, capture, legitimacy, coalition strain, and force sustainment combine into one escalating system rather than separate mechanics.
A model for how extraction, transport, storage, transformation, and redistribution create stability or fragility in a world system.
A sample systems study showing how basin agriculture, defensive ridges, and narrow passes produce a dense but brittle civilization pattern.
A framework for reading intake, transit, storage, conversion, release, and capture as one circulation architecture rather than isolated logistics steps.
An advanced science-fiction study of how infrastructure advantage, communication compression, and selective peripheral integration can stabilize rule at long distance without evenly occupying every region.
A historical study of how alternate attendance, highway discipline, domain expenditure, and status ritual converted a polycentric order into a governable legitimacy regime.
These are the module surfaces you should enter once the guide reveals the next weak layer.
| Module | Why Enter | Path |
|---|---|---|
| Worlds Track | Start from terrain, settlement, surplus, and civilizational pressure so the world has structural coherence before detail expands. | 4 stages |
| Systems Track | Trace loops, surplus capture, institutional pressure, and disruption so the world behaves like a system rather than a list of mechanics. | 4 stages |
| Spatial Track | Abstract maps into nodes, corridors, and stress scenarios so movement and leverage become legible before visual polish. | 5 stages |
Use Studies when the workflow output is ready for case validation, and Archive when you need broader graph orientation before opening more collections.
Compare full settings when you want to test whether this workflow survives contact with complete worlds.
Browse across modules and collections when you want a wider traversal after this guide.
Search the current knowledge graph directly when you already know the concept you need next.
Compare full settings when you want to test whether this workflow survives contact with complete worlds.
Reusable lenses for thinking about structured worldbuilding.
Explicit systems and dynamics that can be reused or adapted.
Applied analyses that show systems operating in context.
Canonical terms for discussing spatial and systemic design.
Browse across modules and collections when you want a wider traversal after this guide.
Search the current knowledge graph directly when you already know the concept you need next.
World lead review cycle matters because large world programs need a repeatable review order, not only more content volume or stronger taste.