FenceOS Ratios Dashboard (People Edition)

TITLE: FenceOS Ratios Dashboard (People Edition)
SUBTITLE: A simple instrument panel for TTC, Buffers, Rate Dominance, and Fence Timing
VERSION: CivOS Unified Spec v1.x
MODE: Almost-Code / parent-friendly / WordPress paste-ready
SCOPE: Z0 Person + Z1 Family + Z2 School/Tuition
GOAL: Make collapse visible early; trigger truncation + stitching before irreversible drift
========================================================
0) DASHBOARD PURPOSE (LOCK)
========================================================
If you cannot measure drift, you will always react too late.
FenceOS Dashboard is a small set of signals that:
- detects impending threshold crossings (TTC)
- checks whether buffers can absorb shocks
- checks whether repair is winning (Rate Dominance)
- checks whether boundaries arrive in time (Fence timing ratios)
Then it triggers:
- Truncation (stop-loss) + Stitching (repair routing)
========================================================
1) CORE METRICS (MINIMUM SET)
========================================================
Metric M1: TTC (Time-to-Threshold-Crossing)
- Meaning: how soon a learner/system hits an irreversible failure threshold if nothing changes
Metric M2: Buffer (Slack Thickness)
- Meaning: how much spare capacity exists to absorb mistakes, stress, fatigue, and load spikes
Metric M3: R (Rate Dominance) = Ḋ/Ġ
- Meaning: is loss accumulating faster than repair/regeneration?
- If R > 1 → drift toward collapse
- If R < 1 → recovery/stability
Metric M4: Θ (Fence-to-Repair Ratio) = T_fence / T_repair
- Meaning: does the boundary arrive before repair window closes?
- Rule: Θ < 1 required
Metric M5: Λ (Enforce-to-Fence Ratio) = T_enforce / T_fence
- Meaning: can you actually enforce the boundary fast enough?
- Rule: Λ < 1 preferred
Optional Metric M6: Coupling Index (C)
- Meaning: how fast failure propagates across topics/emotions/household schedules
- Higher C → earlier truncation required
========================================================
2) HOW TO ESTIMATE EACH METRIC (NO MATH REQUIRED)
========================================================
M1 TTC (simple bands):
- TTC-RED: ≤ 14 days (near exam/test; failure imminent if unstable)
- TTC-AMBER: 15–45 days (enough time but must repair weekly)
- TTC-GREEN: > 45 days (silent attrition risk if routine weak)
M2 Buffer (simple bands):
- Buffer-LOW:
  - sleep debt OR high stress OR chaotic routine OR frequent conflict
- Buffer-MID:
  - routine exists but breaks under spikes
- Buffer-HIGH:
  - stable routine, can absorb setbacks, low volatility
M3 Rate Dominance R (weekly proxy):
- R>1 if:
  - number of weak topics growing week-to-week
  - same mistake repeats without shrinking
  - timed score trend is flat/down despite effort
- R<1 if:
  - weakest topics shrinking week-to-week
  - error types disappearing
  - timed reliability improving
M4 Θ (Fence timing proxy):
- T_fence = time from “problem noticed” → boundary applied (stop-loss / scope change)
- T_repair = time remaining before failure becomes irreversible (TTC window)
- Θ<1 if you fence within 24–72 hours when TTC is short
- Θ>1 if you “wait and see” while TTC is collapsing
M5 Λ (Enforcement proxy):
- T_enforce = time to actually implement boundary (routine, environment, phone rules)
- Λ<1 if boundary is enforceable the same day
- Λ>1 if everyone agrees but nothing changes
M6 Coupling (optional):
- High coupling signs:
  - one bad test spirals into avoidance + conflict + sleep loss
  - one missed lesson breaks the whole week
  - emotions contaminate all subjects
- Low coupling signs:
  - a failure stays contained to one topic and is repaired quickly
========================================================
3) DASHBOARD STATES (TRAFFIC LIGHT)
========================================================
STATE S0: STABLE (GREEN)
- TTC GREEN or AMBER
- Buffer MID/HIGH
- R < 1
- Θ < 1
Action:
- continue normal training + weekly verification
- add transfer practice gradually
STATE S1: DRIFT (AMBER)
- TTC AMBER or RED
- Buffer MID/LOW
- R ≈ 1 or slightly >1
- Θ borderline
Action:
- apply truncation to stop acceleration
- route smallest repair loop
- protect sleep/routine for 7 days
STATE S2: COLLAPSE RISK (RED)
- TTC RED
- Buffer LOW
- R > 1
- Θ > 1 (fencing too late)
- Λ > 1 (cannot enforce)
Action:
- immediate truncation + strict scope fence
- rebuild buffers first (sleep, routine, conflict fence)
- daily micro-repair + timed micro-sets
- retest within 72 hours
========================================================
4) FENCE TRIGGERS (AUTOMATIC RULES)
========================================================
Trigger T1 (TTC trigger):
IF TTC-RED AND performance unstable
→ Truncate scope immediately + start daily repair loop
Trigger T2 (Buffer trigger):
IF Buffer-LOW
→ Truncate load + rebuild buffer before pushing difficulty
Trigger T3 (Rate trigger):
IF R > 1 for 7 days
→ Stop new topics, repair weakest node, retest fast
Trigger T4 (Timing trigger):
IF Θ > 1
→ reduce decision latency: fence within 24 hours
Trigger T5 (Enforcement trigger):
IF Λ > 1
→ redesign boundary to be enforceable (smaller, simpler, same-day)
Trigger T6 (Coupling trigger):
IF Coupling high
→ earlier truncation, smaller steps, stronger routine fences
========================================================
5) ACTION MENU (WHAT TO DO WHEN RED/AMBER)
========================================================
Action A0: Truncation Menu (stop-loss)
- scope fence: smallest failing node only
- time fence: short daily reps
- stop-loss timer: cap struggle, switch to worked example
- downgrade: easier set to restore correctness first
Action A1: Stitching Menu (repair routing)
- pick 1 loop:
  R1 prerequisite micro-repair
  R2 inversion practice (kills false competence)
  R3 timed micro-sets (fix load collapse)
  R4 error taxonomy + checklist (fix careless drift)
  R5 language parsing template + command-word bank
  R6 routine rebuild (sleep + schedule + friction removal)
Action A2: Verification
- within 72 hours:
  - does learner finish more?
  - do error types shrink?
  - does panic decrease?
- within 7 days:
  - timed score trend ↑
  - volatility ↓
  - R moves below 1
========================================================
6) FAILURE MODE TRACE (REQUIRED)
========================================================
Trace:
TTC short + Buffer low → R>1 → fence applied late (Θ>1) → enforcement weak (Λ>1) → P2→P0 collapse → avoidance loop
Fence Repair:
apply same-day enforceable boundary (Λ<1) → fence within 24h (Θ<1) → truncate scope → stitch smallest repair loop → verify R<1 → rebuild buffer → P3 stability returns
========================================================
7) WORDPRESS PASTE-READY PAGE
========================================================
H1: FenceOS Dashboard: The 5 Signals That Prevent Learning Collapse
H2: TTC — how close you are to a threshold crossing
H2: Buffer — how much slack you have
H2: Rate Dominance (R) — is repair winning?
H2: Fence Timing (Θ, Λ) — are you fencing early enough?
H2: Traffic Light States (Green/Amber/Red)
H2: Automatic Fence Triggers
H2: Action Menu (Truncation + Stitching)
H2: Failure Mode Trace (Short)
H2: Copy/Paste Checklist
========================================================
8) COPY/PASTE CHECKLIST (PARENT-FRIENDLY)
========================================================
Every week, answer:
- TTC: RED / AMBER / GREEN?
- Buffer: LOW / MID / HIGH?
- R: are weak topics growing (R>1) or shrinking (R<1)?
- Θ: did we fence within 24–72h when problems appeared?
- Λ: did we actually enforce the boundary the same day?
If RED:
- stop new topics
- shrink scope to weakest node
- daily repair + timed micro-set
- protect sleep for 7 days
- retest within 72 hours
END SPEC
========================================================

ONE-LINE INSERT (for any page)
FenceOS turns “study problems” into measurable signals (TTC, Buffer, R, Θ, Λ) so you can stop the crash early and stitch back into stable flight.