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 how tools, infrastructure, training, maintenance, and standardization determine whether a technology stays elite or rewrites everyday world structure.
Technology changes a world only when it can move beyond isolated invention and become reproducible across labor, supply, and institutions.
The real question is not whether a device is possible. The question is whether the world can train operators, source inputs, repair failures, standardize parts, and route output widely enough for the device to alter everyday constraints.
| Axis | Question | Signal |
|---|---|---|
| Input base | What materials, fuels, and components make the technology possible? | Extractive chains, workshop inputs, energy density, import dependence |
| Operator base | Who can build, maintain, and use it reliably? | Guilds, schools, drill time, literacy, calibration skill, repair discipline |
| Infrastructure base | What larger systems must exist before this scales? | Roads, ports, relay systems, warehouses, foundries, regulated standards |
| Diffusion ceiling | Why does adoption stop at a certain layer of society? | Cost, monopoly, state secrecy, maintenance burden, frontier unreliability |
Shows why every scalable technology is attached to extraction, transport, storage, and replacement chains.
Surplus Capture LadderExplains how technological gains become taxable power, military advantage, or concentrated institutional leverage.
Magic Operating RegimeProvides the parallel lens for worlds where capability spreads through ritual and monopoly rather than industrial replication.
Most technologies do not fail at invention. They fail at replication. Input chains break, operator training stays narrow, maintenance becomes too expensive, or the frontier lacks the infrastructure needed to keep the technology reliable. The diffusion regime is therefore a model of practical spread, not of abstract capability.
The reusable lesson is that capability diffusion decides whether a world stays craft-bound, becomes infrastructural, or fragments into uneven technological islands.
Technology feels believable when it changes communication speed, storage practice, labor organization, military timing, and frontier reach all at once instead of appearing as a decorative prop.
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 Resource Flow Loop and then return here once the surrounding concept stack is clear.
Use Resource Flow Loop 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.
1 handoff nodes stay inside Capability Regimes. 1 handoff nodes share Network.
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 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.
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 routes, relays, buffers, and linked nodes matter more than territorial bulk.
Use prerequisites when you want the shortest path into the assumptions this page depends on.
A model for how extraction, transport, storage, transformation, and redistribution create stability or fragility in a world system.
A model for how raw surplus becomes taxable, storable, and politically controllable through successive layers of capture.
This entry still relies on generic related links. That works as a fallback, but typed relation roles would make continuation clearer.
A model for how extraction, transport, storage, transformation, and redistribution create stability or fragility in a world system.
A model for how raw surplus becomes taxable, storable, and politically controllable through successive layers of capture.
A framework for tracking expansion, consolidation, frontier friction, and institutional fatigue across a civilizational space.
A model for how magical capability is sourced, gated, trained, costed, and monopolized so it behaves like a real operating layer instead of selective plot permission.
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.