Loading this page.
Preparing content, navigation, and supporting references for this route.
Preparing content, navigation, and supporting references for this route.
Capability modeling defines what kinds of transformation, communication, movement, extraction, or coercion a world can actually sustain. Whether the mechanism is magical, technological, biological, or ritual, the key question is the same: what new leverage does it create, for whom, at what cost, and under what ceiling?
Operational lenses currently organizing this world layer.
Curated stages that turn this world layer into a usable sequence.
Entries currently surfaced as the reading base for this layer.
This world layer now exposes program branches and scale lanes directly, so layer-level browse stays compatible with the same taxonomy used across the wider graph.
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 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.
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 region is the main leverage unit for settlement, extraction, governance, or conflict.
Use this scale when city-scale transfer, concentration, or control is doing the main structural work.
Define the upper bound of what actors can sense, move, store, heal, destroy, calculate, or coordinate across distance.
Every powerful system should have fuel, maintenance, skill bottlenecks, ritual windows, infrastructure load, or institutional dependence that limits scaling.
Ask whether the capability is elite-only, infrastructural, civilianized, frontier-adapted, or monopolized by a few organizations.
The real question is not what the capability can do in isolation, but which existing constraints it softens and which new constraints it introduces.
Use these entries when you want the clearest current examples before following the full reading path.
A planning frame for mapping how geography, settlement, resources, and transit form a region's structural identity.
A framework for reading intake, transit, storage, conversion, release, and capture as one circulation architecture rather than isolated logistics steps.
A framework for reading how technology, magic, infrastructure, communication, and maintenance reorganize what a world can coordinate, govern, and reproduce at scale.
A model for identifying when reduced coordination delay becomes strong enough to change territorial control, reserve release, and operating scale rather than merely making an old system slightly faster.
A framework for mapping how flow, capture, legitimacy, coalition strain, and force sustainment combine into one escalating system rather than separate mechanics.
A historical study of how telegraph lines, rail corridors, operator discipline, and maintenance standards compressed command time and rewrote territorial governance.
This path now combines substrate, capability-regime framing, command compression, infrastructure burden, and proof cases with the world and system entries capability layers tend to rewrite most aggressively.
Start with substrate and resource structure so you know what problems the new capability is actually changing.
You can compare the world before and after the capability layer instead of free-floating speculation.
World Foundations currently leads this stage with 2 supporting entries.
Cross-Scale currently anchors this stage with 2 supporting entries.
A framework for reading how food, water, health, and maintenance cycles must keep reproducing beneath settlement, surplus, and political order.
A planning frame for mapping how geography, settlement, resources, and transit form a region's structural identity.
A framework for reading intake, transit, storage, conversion, release, and capture as one circulation architecture rather than isolated logistics steps.
Open this only when you are actively revising a world layer instead of browsing for orientation.
Magic and technology should rewrite existing layers, not replace them. Use these handoffs to keep the model integrated.
Open the guide when the capability is interesting in premise but still needs one disciplined pass through access, command compression, upkeep, and hierarchy rewrite.
Return to substrate and climate when the capability seems to ignore hard environmental cost.
Check fuel, materials, maintenance, and throughput once power depends on supply chains.
See how capability changes governance, coercion, communication, and hierarchy.
Move into dynamic loops when you want escalation, balancing effects, and incentives.
Capability modeling matters because technology or magic only feels consequential when it visibly rewrites the same constraints the rest of the world is already obeying.