eduKate Singapore

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.

Next useful routeCanonical hubHELP

Planet OS Sensors Directory (Canonical)

Planet OS Sensors are the master instrument panel for the full stack.

This page exists so Planet OS can execute without drifting into narrative.

A sensor is only real if it produces repair decisions.

A sensor pack is only real if it can be run as a loop:
snapshot → slope → bottleneck → repair → recurrence check.

What Makes a Sensor Real

A real sensor must have:

  1. One variable only
  2. How to read it (signal vs illusion)
  3. Thresholds (healthy / weakening / danger / fracture)
  4. Repair actions (what to do next)

If it doesn’t lead to repair actions, it’s not a sensor.

Planet OS Meta Sensors (Canonical Set)

These sit above all OS modules and keep the whole framework coherent.

1) Planet Sensor: Recurrence Index

Planet Sensor: Recurrence Index (Canonical)

2) Planet Sensor: Bottleneck Detector

Planet Sensor: Bottleneck Detector (Canonical)

3) Planet Sensor: Repair Capacity Growth

Planet Sensor: Repair Capacity Growth (Canonical)

4) Planet Sensor: Drift Containment Index

Planet Sensor: Drift Containment Index (Canonical)

Links to OS-Level Sensor Packs

Vocabulary OS Sensors

Vocabulary OS Sensor Directory

Education OS Sensors

Education OS Sensors Directory

Civilisation OS Sensors

Civilisation OS Sensor Directory

Sensor Clusters (Planet OS)

1) Vocabulary OS Sensor Cluster (Meaning Precision)

Purpose:
measures meaning stability and language usability.

2) Education OS Sensor Cluster (Capability Conversion)

Purpose:
measures whether time is converting into stable capability.

3) Civilisation OS Sensor Cluster (Stability Diagnostics)

Purpose:
measures civilisation brittleness and repair capacity.

4) Planet-Level Meta Sensors (Cross-Stack)

These are sensors that sit above individual OS modules.

A) Recurrence Index (Master Truth Test)

Measures whether the same failures repeat across systems.

Suggested page:
https://edukatesg.com/planet-sensor-recurrence/

B) Bottleneck Detector

Measures which OS layer is limiting the system most.

Suggested page:
https://edukatesg.com/planet-sensor-bottleneck/

C) Repair Capacity Growth

Measures whether the system is improving its ability to repair over time.

Suggested page:
https://edukatesg.com/planet-sensor-repair-capacity/

D) Drift Containment Index

Measures whether truth flow is improving or degrading across the stack.

Suggested page:
https://edukatesg.com/planet-sensor-drift-containment/

These meta sensors keep the whole framework coherent.

How to Use This Directory (Fast)

  1. open the dashboard
    https://edukatesg.com/planet-os-dashboard/
  2. pick the relevant cluster
    (vocab / education / civilisation)
  3. take snapshot readings
  4. check slopes (1m / 6m / 1y / 5y)
  5. pick bottleneck
  6. run repair plan until recurrence drops

That is execution.

Canonical Statement

Planet OS Sensors Directory is the master instrument hub that links the meta sensors and the OS-level sensor packs, so Planet OS stays executable through measurement, slopes, bottlenecks, and repair outcomes.

Planet Sensor: Recurrence Index (Canonical)
slug: planet-sensor-recurrence

Planet Sensor: Recurrence Index (Canonical)

Recurrence Index is the master truth sensor.

It asks one question:

Do the same failures repeat?

Recurrence bypasses narrative and goes straight to outcome.

If the same failure repeats, repair did not happen, or repair did not propagate.

What This Sensor Measures

Recurrence Index measures:

  1. Repeat frequency
    How often the same failure returns
  2. Repeat severity
    Whether repeats are getting worse or more costly
  3. Repeat spread
    Whether the failure is spreading across domains
  4. Repair persistence
    Whether the fix holds after delay
  5. System learning
    Whether recurrence declines over cycles

How to Read This Sensor

Healthy signal

Failures become rarer over time
Fixes hold after delay
The system improves after shocks
The same mistakes stop appearing
Repairs propagate beyond one person or one location

Danger signal

The same failures return with the same pattern
Patches work briefly then collapse
Crisis response becomes normal
Failures spread into other systems
Recurrence rises even when effort rises

Thresholds

Level 1: Low recurrence

Rare repeats, strong system learning

Level 2: Mild recurrence

Some repeats, repair works but uneven

Level 3: Rising recurrence

Repeats become visible, repair not holding

Level 4: High recurrence

Cycles dominate, crisis mode becomes normal

Level 5: Runaway recurrence

Repeats are default, repair fails to propagate, brittleness rises fast

Repair Actions

  1. Identify the top recurring failure
  2. Repair the root cause, not the symptom
  3. Retest after delay (delay is the truth test)
  4. Propagate the fix across the system
  5. Remove drift and coordination friction that block repair

Links

Planet OS Sensors Directory
https://edukatesg.com/planet-os-sensors/

Civilisation Repair Rate Sensor
https://edukatesg.com/civilisation-sensor-repair/

Vocabulary Repair Sensor
https://edukatesg.com/vocab-sensor-repair/

Canonical Statement

Recurrence Index is the truth sensor of Planet OS. If recurrence does not drop, repair is not real.

Planet Sensor: Bottleneck Detector (Canonical)
slug: planet-sensor-bottleneck

Planet Sensor: Bottleneck Detector (Canonical)

Bottleneck Detector identifies which OS layer is limiting the whole system right now.

Most systems fail because they repair the wrong layer.

A bottleneck is not the biggest visible problem.

A bottleneck is the limiting factor that prevents improvement elsewhere.

What This Sensor Measures

  1. Constraint dominance
    Which layer is binding hardest
  2. Downstream symptom mapping
    Which failures are secondary effects
  3. Repair leverage
    Which fix would drop recurrence the fastest
  4. Cross-sensor weakness
    Which panel is weakest relative to the others
  5. Time-to-stability
    Which layer takes longest to stabilise (often the limiter)

How to Read This Sensor

Healthy signal

One limiting layer becomes obvious
Fixing it improves multiple outcomes
Recurrence declines after repair

Danger signal

Effort increases but outcomes don’t change
Multiple repairs happen but recurrence stays high
Slopes stay flat
Symptoms jump around because the root limiter is untouched
Drift or coordination friction hides the real bottleneck

Bottleneck Categories (Common Limiters)

Mind bottleneck
Vocabulary bottleneck
Education bottleneck
Governance bottleneck
Production bottleneck
Constraint bottleneck
Drift bottleneck
Repair bottleneck

Usually one dominates.

Thresholds

Level 1: Clear bottleneck

One limiter is obvious, high leverage repair

Level 2: Probable bottleneck

Two candidates, needs a short test

Level 3: Mixed bottlenecks

Multiple weak layers, repair foundations first

Level 4: Hidden bottleneck

Drift or coordination cost blocks clarity

Level 5: Bottleneck cascade

Constraints + CDI + drift + coordination rising together

Repair Actions

  1. Stop optimising non-bottleneck layers
  2. Run a short repair experiment on the suspected limiter
  3. Define recurrence drop criteria
  4. Retest after delay
  5. Propagate the fix

Links

Planet OS Sensors Directory
https://edukatesg.com/planet-os-sensors/

Recurrence Index
https://edukatesg.com/planet-sensor-recurrence/

Canonical Statement

Bottleneck Detector prevents wasted effort by forcing repair to target the limiting layer that controls recurrence and slope outcomes.

Planet Sensor: Repair Capacity Growth (Canonical)
slug: planet-sensor-repair-capacity

Planet Sensor: Repair Capacity Growth (Canonical)

Repair Capacity Growth measures whether the system is becoming better at repairing over time.

A system is stable not because it has no problems, but because it learns.

If repair capacity grows, stability compounds.

If repair capacity shrinks, brittleness compounds.

What This Sensor Measures

  1. Repair speed trend
    Time-to-fix decreases over cycles
  2. Repair completeness trend
    Root-cause fixes increase, patches decrease
  3. Recurrence decline efficiency
    Each cycle produces a bigger recurrence drop
  4. Repair propagation
    Fixes spread beyond local hero efforts
  5. System memory
    Lessons remain and do not need re-learning

How to Read This Sensor

Healthy signal

Repair gets faster each cycle
Similar problems are handled with less disruption
Fixes become institutional
Best practices spread quickly
Recurrence drops more strongly over time

Danger signal

Repair takes longer each cycle
Fixes don’t hold
Turnover wipes institutional memory
Coordination friction blocks scaling
Drift corrupts feedback so the system cannot learn

Thresholds

Level 1: Compounding repair

Fast improvement in repair throughput and recurrence decline

Level 2: Growing

Clear improvement, still uneven

Level 3: Flat

Repairs happen but learning does not scale

Level 4: Shrinking

Repairs slow down, recurrence persists

Level 5: Repair capacity collapse

Crises become normal, system becomes brittle

Repair Actions

  1. Build system memory (playbooks, standards, training)
  2. Reduce drift so truth can travel
  3. Reduce coordination cost so repairs can propagate
  4. Train repair competence (tools, skills, redundancy)
  5. Prioritise recurring failures first (highest learning leverage)

Links

Planet OS Sensors Directory
https://edukatesg.com/planet-os-sensors/

Civilisation Drift Sensor
https://edukatesg.com/civilisation-sensor-drift/

Civilisation Coordination Sensor
https://edukatesg.com/civilisation-sensor-coordination/

Canonical Statement

Repair Capacity Growth measures whether the system learns. If repair capacity is not increasing, long-run stability is not improving.

Planet Sensor: Drift Containment Index (Canonical)
slug: planet-sensor-drift-containment

Planet Sensor: Drift Containment Index (Canonical)

Drift Containment Index measures whether a system can keep truth stable as it scales.

When drift containment is weak, the system becomes blind.

Blind systems cannot repair.

They respond, but they don’t fix.

What This Sensor Measures

  1. Feedback integrity
    Can bad news travel safely?
  2. Metric alignment
    Do numbers match lived reality?
  3. Gaming resistance
    How hard is it to fake success?
  4. Correction velocity
    How quickly false beliefs are corrected
  5. Truth propagation speed
    Does accurate information spread faster than misinformation?

How to Read This Sensor

Healthy signal

Truth is speakable
Feedback loops work
Mistakes are admitted early
Metrics are cross-checkable
Corrections happen quickly
Recurrence declines after corrective action

Danger signal

Self-censorship rises
Bad news is punished
Metrics look great while reality worsens
Appearance management dominates
Misinformation spreads faster than correction
Failures repeat because root causes stay hidden

Thresholds

Level 1: Strong containment

Truth flows, correction is fast, repair is accurate

Level 2: Mostly contained

Some pressure, but correction still works

Level 3: Weak containment

Incentives distort reporting, correction slows

Level 4: Severe drift

Truth becomes unsafe, narratives dominate

Level 5: Reality split

Public narrative and lived reality diverge sharply, repair becomes impossible

Repair Actions

  1. Protect truth-tellers
  2. Fix incentives (reward accuracy, not appearance)
  3. Cross-check metrics with independent channels
  4. Shorten correction loops
  5. Use recurrence as the final truth test

Links

Planet OS Sensors Directory
https://edukatesg.com/planet-os-sensors/

Civilisation Drift Sensor
https://edukatesg.com/civilisation-sensor-drift/

Recurrence Index
https://edukatesg.com/planet-sensor-recurrence/

Canonical Statement

Planet OS Sensors Directory is the master instrument hub that links all sensor clusters and meta sensors — so Planet OS can be executed through measurement, slope tracking, bottleneck detection, and repair outcomes without drifting into narrative.