(Civilisation OS Reference Page v0)
Collapse signatures are repeatable failure patterns, not unique events.
This page maps each signature directly to real executed cases, proving that collapse follows mechanics — not narratives.
This is the grammar layer of Civilisation OS.
What This Page Does
- Translates abstract failure modes into concrete reality
- Allows fast diagnosis (“this looks like X”)
- Prevents storytelling bias
- Enables early detection and correct recovery mode selection
If you can name the signature, you can intervene early.
The Canonical Collapse Signatures
CS-01 — Capability Stall (Local)
Pattern: Effort increases, progress stagnates.
Primary OS: Education OS
Typical Contexts: students, employees, early-stage organisations
Mapped Case:
→ Case 1 — Student Stalls Despite Tuition/civilisation-os-case-1-student-stalls/
CS-04 — Incentive Inversion (Goodhart Drift)
Pattern: Metrics improve while reality worsens.
Primary OS: Governance OS
Typical Contexts: schools, corporations, governments
Mapped Case:
→ Case 2 — School Improves Scores but Real Capability Drops/civilisation-os-case-2-school-score-illusion/
CS-06 — Institutional Hollowing
Pattern: Output remains high while internal capability erodes.
Primary OS: Governance + Production
Typical Contexts: companies, agencies, mature institutions
Mapped Case:
→ Case 3 — Company Looks Successful but Is Hollowing Out/civilisation-os-case-3-company-hollowing-out/
CS-12 — Maintenance Debt Spiral
Pattern: Deferred upkeep accumulates until failure appears sudden.
Primary OS: Production / Technology
Typical Contexts: infrastructure, IT systems, cities, supply chains
Mapped Case:
→ Case 4 — Maintenance Debt Spiral/civilisation-os-case-4-maintenance-debt-spiral/
CS-11 — Fragility Cascade
Pattern: Small shocks trigger system-wide breakdown.
Primary OS: Production + Governance
Typical Contexts: just-in-time systems, over-optimised economies
Mapped Case:
→ Case 5 — Fragility Cascade/civilisation-os-case-5-fragility-cascade/
CS-14 — Scarcity Bind
Pattern: Chronic scarcity causes volatility, conflict, and instability.
Primary OS: Constraint OS
Typical Contexts: energy, water, food, housing, labor markets
Mapped Case:
→ Case 6 — Scarcity Bind/civilisation-os-case-6-scarcity-bind/
CS-16 — Late Correction / Irreversibility
Pattern: Problems recognised too late; options vanish faster than action.
Primary OS: Constraint OS (Time)
Typical Contexts: wars, climate, fiscal collapse, demographic collapse
Mapped Case:
→ Case 7 — Late Correction / Irreversibility/civilisation-os-case-7-late-correction-irreversibility/
Why This Map Matters
Most failures are misdiagnosed because people argue about events instead of mechanisms.
This map allows:
- fast classification
- correct recovery mode selection
- avoidance of wrong “solutions” that worsen collapse
How to Use This Page
- Identify which signature best matches reality
- Click through to the mapped case
- Observe the DLR pattern and recovery mode
- Run a local Civilisation OS execution