(Civilisation OS Execution v0.4)
Block 1 — System Boundary
System:
An organisation, city, sector, or nation whose systems still function but are increasingly unreliable due to accumulated maintenance debt.
Included:
- physical infrastructure (buildings, transport, utilities, IT systems)
- operational processes
- maintenance budgets and schedules
- incident handling
- staff capability and morale
- governance incentives around “new projects vs upkeep”
Excluded:
- sudden black swan shocks (war, natural disasters)
- deliberate sabotage
- brand-new systems with no operational history
Goal:
Stop entropy from compounding and restore long-term system reliability before cascading failure begins.
Block 2 — DLR Scores by OS (0–5)
OS-3 Production / Technology OS (Primary)
- D (Depth): 3/5
Systems were once competently designed. - L (Load): 4/5
High utilisation, constant pressure to deliver output. - R (Repairability): 2/5
Repairs are reactive, rushed, and incomplete; root causes persist.
OS-2 Governance OS
- D: 2/5
Leadership prioritises expansion, optics, and short-term KPIs. - L: 3/5
Budget and political pressure. - R: 1/5
Maintenance warnings are ignored or deferred; bad news punished.
OS-1 Education OS
- D: 2/5
Knowledge about legacy systems concentrated in a few individuals. - L: 3/5
Firefighting replaces learning and documentation. - R: 2/5
Lessons are “noted” but not institutionalised.
OS-4 Constraint OS
- D: 3/5
Constraints understood in theory. - L: 3/5
Aging assets increase energy and resource drain. - R: 3/5
Still recoverable if action is taken soon.
Dominant pattern:
Entropy is compounding faster than repair.
Block 3 — Dominant Collapse Signature
CS-12 — Maintenance Debt Spiral
Observable signals:
- incidents become more frequent
- the same failures recur
- “temporary fixes” become permanent
- outages appear random but follow a rising curve
- experienced staff leave due to exhaustion
This is not incompetence.
This is entropy winning.
Block 4 — Recovery Mode (Exactly One)
✅ RM-11 — Maintenance & Renewal Mode
Why this mode:
You cannot innovate or expand your way out of entropy.
The only viable move is to pay down maintenance debt deliberately.
Block 5 — OSME-e/t Plan
O — Outcome (6–12 months)
- Incident frequency decreases.
- Repeat failures drop sharply.
- System uptime and reliability stabilise.
- Staff confidence in systems returns.
S — System Boundary
- Maintenance budgets
- asset lifecycle management
- staffing and training
- decision rules for “new build vs upkeep”
M — Mechanism
Deferred maintenance compounds non-linearly:
- small issues create load
- load reduces repair quality
- poor repairs create more failures
- eventually, the system collapses “suddenly”
E — Execution
- Freeze non-essential expansion
- no new features, projects, or cosmetic upgrades
- Inventory critical assets
- identify systems whose failure cascades
- Fund maintenance first
- maintenance budget protected by rule, not discretion
- Root-cause repair
- no patch without permanent fix
- Knowledge capture
- document systems before key people leave
- Maintenance cadence
- enforce scheduled downtime for repair
e/t — Energy over Time
- Energy: moderate but sustained
- Time: minimum 6 months to reverse the slope; 12–24 months for full renewal
Risk if underfunded:
False recovery → sharper collapse later.
Block 6 — Retest Probes + Thresholds
Probe 1 (Short-horizon — entropy control)
Repeat Incident Rate
- Pass: ≥ 20% reduction within 90 days
- Fail: same incidents recur
Probe 2 (Mid-horizon — resilience)
Maintenance Backlog Trend
- Pass: backlog decreases month-on-month
- Fail: backlog flat or growing
Probe 3 (Long-horizon — recovery integrity)
Mean Time to Recovery (MTTR)
- Pass: MTTR decreases steadily over 6–12 months
- Fail: MTTR unchanged despite spending
Optional confirmation:
Staff Attrition in Critical Roles
- falling attrition = system trust returning
Block 7 — Version + Status
- Version: Civilisation OS v0.4
- Status: Active Repair (RM-11)
- Next Retest:
- 90 days (incident slope)
- 6 months (backlog + MTTR)
Decision rule:
- If incidents drop and backlog shrinks → continue RM-11
- If outages cascade → switch to RM-10 Resilience & Redundancy
- If leadership blocks maintenance → switch to RM-06 Truth Restoration
Suggested Slug
/civilisation-os-case-4-maintenance-debt-spiral/
When ready, say “Case 5” and we’ll proceed to Fragility Cascade.