A model for tracing whether disruption pushes a system toward repair, brittle stagnation, or self-amplifying collapse after reserves, coordination, and repair capacity are tested.
What matters after shock is not only how hard the hit was, but whether repair returns faster than exposure compounds.
Read when
Use this when a concrete mechanism in Evolution And Breakdown 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.
Disruption does not create only two outcomes. Systems often pass through a loop where reserves are released, repairs begin, coordination degrades or stabilizes, and the same shock either gets absorbed or amplified.
The recovery-collapse loop makes that sequence explicit. It is useful when you need to explain why one system rebounds from a blockade, harvest failure, or raid while another enters prolonged brittleness from a shock that looked similar on day one.
Read the post-shock loop
State 1Absorb the shock
Measure what reserves, slack, or local substitution can keep operating immediately after disruption.
State 2Restore the damaged links
Track whether repair crews, reserve release, and coordination arrive fast enough to reopen critical flow.
State 3Watch the second-order burden
Ask whether the repair effort itself creates debt, exhaustion, or governance drift that makes the next disruption worse.
Three post-shock states in a recovery-collapse loop.
Axis
Question
Signal
Recovery
Does repair restore key flow before reserve depletion becomes decisive?
Use the model for economies, campaigns, city infrastructure, frontier rule, or ecological systems whenever the interesting question is what happens after the first failure, not whether the first failure happens.
It is also a useful antidote to binary writing. Systems often look stable right before they enter drawn-out stagnation, and they often look doomed right before a reserve release or repair corridor gives them enough space to recover.
The reusable lesson is that resilience should be modeled as a loop of response, repair, and renewed exposure. That keeps recovery believable and prevents collapse from appearing as an arbitrary plot switch.
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 firstRelation map
3 typed paths across 2 continuation roles
These entries clarify the footing underneath the current node before you move outward again. Start with Strategic Reserve Network when you want the clearest next role.
Foundation 2 · Contrast 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.
Turn all major programs into creator-operable workflows rather than leaving them as analysis-only content.
Start in Guides with the workflow framework, choose the role route, open the supporting program branches only as needed, and leave with a worksheet or review artifact.
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.
