This page lists the canonical ways the full stack breaks.
Planet OS is designed to prevent drift, but failure still happens when:
- sensors are ignored
- dependencies are skipped
- repair is cosmetic
- narratives replace measurement
Failure modes are important because they explain why systems look like they run while silently degrading.
Failure Mode 1 — Boot Skipping (Top-Down Fantasy)
What happens:
People try to run Civilisation OS conclusions without stabilising Mind/Vocabulary/Education.
Symptoms:
- confident narratives
- weak causal accuracy
- contradictions across layers
- “solutions” that don’t stick
Repair:
Return to boot sequence:
https://edukatesg.com/planet-os-boot-sequence/
Failure Mode 2 — Sensorless Operation (Story Mode)
What happens:
People discuss stability without measurement.
Symptoms:
- opinions replace variables
- debates never resolve
- outcomes don’t improve
- no repeatable execution
Repair:
Turn on the panels:
https://edukatesg.com/planet-os-sensors/
Failure Mode 3 — Drift Dominance (Truth Failure)
What happens:
Narratives outrun reality.
Symptoms:
- metrics look good, reality worsens
- bad news cannot travel
- policy is performance, not repair
- trust collapses suddenly
Repair:
Repair truth flow:
https://edukatesg.com/civilisation-sensor-drift/
Failure Mode 4 — Coordination Cost Explosion (Execution Failure)
What happens:
Even correct diagnosis cannot execute.
Symptoms:
- paralysis
- endless committees
- delays become normal
- enforcement costs rise
- agency conflict
Repair:
Reduce coordination friction:
https://edukatesg.com/civilisation-sensor-coordination/
Failure Mode 5 — Repair Rate Collapse (Recurrence)
What happens:
The system responds but does not repair.
Symptoms:
- the same failures return
- crisis response becomes permanent
- decay compounds
- buffers shrink
Repair:
Target recurrence:
https://edukatesg.com/civilisation-sensor-repair/
Failure Mode 6 — Constraint Lock (Ceilings Bind)
What happens:
Constraints tighten until repair cannot scale.
Symptoms:
- maintenance backlog becomes impossible
- debt servicing dominates
- energy shocks cascade
- demographic burden overwhelms
- resilience disappears
Repair:
Restore buffers early:
https://edukatesg.com/civilisation-sensor-constraint/
Failure Mode 7 — CDI Runaway (Decay Compounds)
What happens:
Decay grows faster than repair.
Symptoms:
- multiple systems fail simultaneously
- cascades occur
- trust collapses
- instability becomes normal
Repair:
Stop recurrence + scale repair throughput:
https://edukatesg.com/civilisation-sensor-cdi/
Failure Mode 8 — Local Optimisation (Kills the Whole)
What happens:
One part improves at the cost of the whole.
Examples:
- test drilling boosts scores temporarily but kills transfer
- impressive metrics hide maintenance decay
- productivity grows while truth flow collapses
Repair:
Use the dashboard and check cross-sensor agreement:
https://edukatesg.com/planet-os-dashboard/
Failure Mode 9 — Plug-in Pollution (Uncontrolled Add-ons)
What happens:
New modules are added without boundaries or sensors.
Symptoms:
- concept sprawl
- terminology drift
- conflicting hierarchies
- project fragmentation
Repair:
Force add-on standard:
https://edukatesg.com/planet-os-addons/
Canonical Statement
Planet OS Failure Modes lists the predictable ways the stack breaks — boot skipping, sensorless story mode, drift dominance, coordination friction, repair collapse, constraint lock, CDI runaway, local optimisation, and plug-in pollution — so repairs can be targeted before brittleness compounds.
Next Page to Publish
Planet OS Add-on Template (How to write a new OS module correctly)
https://edukatesg.com/planet-os-addon-template/