A model for how tools, infrastructure, training, maintenance, and standardization determine whether a technology stays elite or rewrites everyday world structure.
4 diffusion gates turns a model for how tools, infrastructure, training, maintenance, and standardization determine whether a technology stays elite or rewrites everyday world structure.
Read when
Use this when a concrete mechanism in Capability Regimes needs to behave coherently instead of only sounding plausible.
IntermediateRead next
Read Resource Flow Loop first, then return here once the surrounding concept stack is clear.
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.
Four gates inside a technology diffusion regime.
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?
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.
Continuation map
Leave this page through one clear next step.
Check the prerequisite, the strongest relation role, and the next route after the reading is complete.
Before this entry
2 prerequisites to read first
Start with Resource Flow Loop and then return here once the surrounding concept stack is clear.
Read firstAdjacent reads
4 linked entrys to branch into
Use Resource Flow Loop or the linked entries below when you want to compare this page against neighboring work.
Model 3 · Framework 1Next move
Open Frameworks
Return to broader lenses when this model is too specific for the question you are asking.
Use this appendix when you want to continue by program branch or operating scale after the page has been read.
Program Branch
Flow and Logistics
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 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.
Send entry feedback with this page already attached.
Use these links for corrections, missing examples, worksheet requests, or confusing sections. Each link includes the current URL, slug, kind, and Program.
Report correction
Flag a factual issue, unclear claim, typo, or outdated passage.
