VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Case 3 — Company Looks Successful but Is Hollowing Out (Civilisation OS Execution v0.4)

Block 1 — System Boundary

System: A company (or institution) with strong outward indicators—revenue, growth, awards, market share—but internally is losing capability: high attrition, decaying quality, rising incidents, knowledge loss, cultural fear, and increasing dependence on short-term extraction.

Included: leadership incentives, internal metrics, hiring/training, knowledge transfer, product/service quality, incident handling, budgeting, maintenance, customer trust.
Excluded: competitor sabotage claims without evidence; illegal tactics; personal targeting.

Goal: Restore long-horizon capability and repairability without killing near-term survival.


Block 2 — DLR Scores by OS (0–5)

OS-1 Education OS (capability formation inside the company)

  • D (Depth): 2/5 — shallow bench; expertise concentrated; weak training pathways
  • L (Load): 4/5 — chronic urgency; burnout; context switching
  • R (Repairability): 2/5 — postmortems exist but don’t change incentives; knowledge not retained

OS-2 Governance OS (truth/incentives/legitimacy inside the org)

  • D: 2/5 — success defined by short-term numbers
  • L: 3/5 — investor/board pressure; competitive intensity
  • R: 1/5 — truth is punished; bad news delayed; gaming widespread

OS-3 Production/Technology OS (delivery engine)

  • D: 3/5 — still producing output, but with rising defects
  • L: 4/5 — over-optimized for speed; maintenance debt growing
  • R: 2/5 — recovery slow; incidents repeat; brittle systems

OS-4 Constraint OS (market + time + resource limits)

  • D: 3/5 — constraints understood in theory
  • L: 3/5 — resources not yet exhausted, but runway narrowing
  • R: 3/5 — options still exist if repair begins early

Dominant issue: Governance repairability collapse + extraction logic driving capability loss.


Block 3 — Dominant Collapse Signature(s)

Primary signature: CS-10 Extraction Lock-in (Hollowing of the System)
Common co-signatures:

  • CS-09 Feedback Collapse (review theatre; no real correction)
  • CS-12 Maintenance Debt Spiral (entropy win)
  • CS-06 Truth Decay (reality hidden)
  • CS-07 Incentive Inversion (metrics gamed)

But we select one primary.


Block 4 — Recovery Mode (Exactly One)

✅ RM-08 — Legitimacy Rebuild Mode

Why this mapping (important): Extraction lock-in survives because the internal social contract breaks:

  • staff stop trusting leadership
  • customers stop trusting quality
  • truth becomes dangerous
  • correction stops being safe

Without legitimacy, you cannot restore truth or incentives sustainably.

Legitimacy rebuild is the first keystone that allows other repairs to stick.


Block 5 — OSME-e/t Plan

O — Outcome (90 days)

  • Trust and truth channels reopen (measurable).
  • Attrition and incident recurrence stabilise.
  • Execution shifts from extraction-only to capability-preserving output.

S — System Boundary

Leadership incentives + performance system + incident/correction culture + maintenance investment + staff/customer trust.

M — Mechanism

Extraction behavior increases short-term numbers but destroys:

  • talent retention
  • knowledge integrity
  • product quality
  • repairability
    which eventually collapses the company.

E — Execution (what changes now)

Step 1 — Declare the “truth protection rule”

  • no punishment for surfacing defects, risks, or bad news
  • public commitment from leadership with enforcement

Step 2 — Repair fairness + accountability

  • transparent criteria for promotions and rewards
  • visible consequences for metric gaming and blame shifting

Step 3 — Rebalance time horizons

  • redefine success to include:
  • defect recurrence rate
  • training throughput
  • maintenance backlog trend
  • customer trust indicators
  • reduce prestige for “hero sprinting” and increase prestige for “system repair”

Step 4 — Make one visible repair investment

  • pick one high-pain system (maintenance debt hotspot)
  • fix it end-to-end to prove seriousness

e/t — Energy over Time Budget

  • Energy: moderate–high (leadership courage required; short-term discomfort inevitable)
  • Time: 90 days to stabilise trust signals; 2–4 quarters to rebuild depth

Block 6 — Retest Probes + Thresholds (Minimum 3)

Probe 1 (Short-horizon — legitimacy / truth channel)

Bad News Flow Rate (G-G2)

  • Pass: reported issues increase in first 2–4 weeks (truth returns), then stabilize
  • Fail: reports stay near zero while incidents still occur (suppression persists)

Probe 2 (Mid-horizon — repairability)

Repeat Incident Rate (R indicator)

  • Pass: repeat incidents drop by ≥ 20% within 60–90 days
  • Fail: repeats unchanged (feedback still fake)

Probe 3 (Long-horizon — capability retention)

Attrition + Knowledge Concentration

  • Pass: attrition stabilises; key-person dependency decreases (more trained backups)
  • Fail: attrition accelerates; expertise concentrates further

Optional production probe:
Maintenance Backlog Trend (P-R3)

  • Pass: backlog shrinks steadily
  • Fail: backlog grows while output claims remain high

Block 7 — Version + Status

Version: Civilisation OS v0.4
Status: Active Repair (RM-08)
Retest schedule: Week 2 (truth), Week 6 (incident recurrence), Day 90 (retention + backlog)

Decision rule at Day 90:

  • If truth channels reopen and repeats fall → next run shifts to RM-07 Incentive Realignment (to lock it in).
  • If audits show truth still suppressed → next run must switch to RM-06 Truth Restoration.
  • If fragility dominates outages → next run shifts to RM-10 Resilience & Redundancy.