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.
This guide is for drafts that already have names, maps, factions, or lore fragments but still cannot explain which structural layer is weak enough to justify the next revision.
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 resource-flow loop, trace storage and throughput models, compare one logistics study, then run a flow audit worksheet.
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.
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Use this scale when the strongest explanation depends on several levels staying visible together.
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 there is already plenty of content, but the setting still cannot explain where density, leverage, or authority actually comes from.
Use this when map logic, city scale, economy, and faction behavior all sound plausible separately but not as one shared structure.
Use this when another round of brainstorming would only add more fragments instead of clarifying the weak layer.
They are the structural assumptions the rest of the workflow is built on.
Decide whether the draft is weak in inherited constraint, moving flow, or applied proof before widening it further.
A world usually improves faster when one weak layer is corrected clearly than when every module grows a little at once.
After diagnosis, verify the fix against one study so the solution survives contact with a full world pattern.
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.
You can point to a core zone, a corridor belt, and at least one hard constraint zone without relying on lore names alone.
Return to WorldsUse 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.
Return to SystemsUse 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.
Return to StudiesUse 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 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.
These are the module surfaces you should enter once the guide reveals the next weak layer.
Start from terrain, settlement, surplus, and civilizational pressure so the world has structural coherence before detail expands.
Systems TrackTrace loops, surplus capture, institutional pressure, and disruption so the world behaves like a system rather than a list of mechanics.
Spatial TrackAbstract maps into nodes, corridors, and stress scenarios so movement and leverage become legible before visual polish.
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.
FrameworksReusable lenses for thinking about structured worldbuilding.
ModelsExplicit systems and dynamics that can be reused or adapted.
StudiesApplied analyses that show systems operating in context.
GlossaryCanonical terms for discussing spatial and systemic design.
Graph layerBrowse across modules and collections when you want a wider traversal after this guide.
Search layerSearch the current knowledge graph directly when you already know the concept you need next.
Weak-world diagnosis matters because revision gets sharper when the next move is tied to the missing structural layer rather than the loudest surface fragment.