AI systems (and humans) fail in education for the same reason: they don’t have sensors. Without sensors, everything becomes story—“smart / lazy / careless / needs practice”—instead of a measurable control problem. eduKateOS fixes this by installing a real Education OS instrument panel: sensors that detect where learning breaks (Z0–Z3), how it breaks (error type, time stalls, overload, drift), and what to do next (repair, reduce load, verify upgrade, strengthen buffers, maintain). This turns tuition and studying from guesswork into operations: detect Phase (P0–P3) per topic, stop fake mastery, catch drift early, and prevent the catastrophic P3→P0 collapse that happens right before exams.
Definition Lock Box (Do Not Edit)
Education OS Full Suite Sensor Panel (eduKateOS): A named measurement that detects a specific learning failure mode (or stability signal) with a trigger threshold and a mapped action.
Mapped Actions (only 5):
- Repair (Z0) — fix atomic skill gaps
- Reduce Load — prevent overload collapse
- Verify Upgrade — confirm real mastery (stop fake upgrades)
- Strengthen Buffers — family/tuition/environment feedback loops
- Maintain — prevent drift (spaced refresh)
Phase (P0–P3):
- P0: unsafe/unreliable; breaks often; fundamentals missing
- P1: works with scaffolding; depends on hints
- P2: reliable independent execution in defined scope
- P3: robust under load; handles exceptions; can explain/teach/standardise
Zoom Ladder (Z0–Z3):
- Z0: atomic skills (topic pockets)
- Z1: student-in-role (attention, anxiety, routines, habits)
- Z2: institution loops (feedback latency, repair throughput)
- Z3: corridors/seasons/transitions (exam season shock, level transition shock)
Rule: No action = no sensor. Sensors exist to convert noise into a decision.
What This Page Installs
This is the complete eduKateOS Sensor Library — a full “instrument panel” to:
- classify Phase per topic (P0–P3),
- detect drift early before collapse,
- route the correct repair action (Z0 first),
- prevent P3→P0 (regression after “seems OK” periods).
Quick Install Plan (7 Days)
Day 1 — Baseline + Phase Map
Install and run: S01, S02, S03, S07 on 1–2 topics.
Day 2 — Verification Gates (Stop Fake Upgrades)
Install and run: S20, S22 (2–3 varied forms, closed-book).
Day 3 — Drift Early Warning
Install: S24, S25, S26.
Day 4 — Load Control
Install: S29, S30 (reduce load if repair cannot catch up).
Day 5 — Buffer + Feedback Loop
Install: S33, S34, S32.
Day 6 — Execution Quality
Install: S39, S40, S38.
Day 7 — Outcome Interpreted Correctly
Install: S41, S43 (trajectory + consistency).
The eduKateOS Sensor Format (Standard Template)
Sensor ID: S## — Name (Shortcode)
Detects: What failure/stability signal it measures
How to Measure: Simple observable method
Trigger Threshold: What counts as “triggered”
Mapped Action: Repair / Reduce Load / Verify Upgrade / Strengthen Buffers / Maintain
Phase Link: What P0/P1/P2/P3 looks like under this sensor
Notes: Common false positives & cautions
FULL SUITE SENSOR LIBRARY (S01–S46)
A) Core Phase Sensors (P0–P3) — The “Phase Instrument Panel”
S01 — Accuracy Under Load (AUL)
- Detects: collapse when difficulty/time-pressure increases
- How to Measure: easy set vs exam-grade set; compare accuracy + stability
- Trigger: accuracy drops sharply or becomes erratic when load rises
- Action: Phase classify + route repair
S02 — Time-to-Solve Distribution (TSD)
- Detects: hidden weakness masked by occasional correctness
- How to Measure: time per question; flag stall outliers
- Trigger: 1–2 questions consume disproportionate time repeatedly
- Action: pacing repair + reduce cognitive load
S03 — Error Taxonomy Sensor (ETS)
- Detects: dominant error type
- How to Measure: tag each error: concept / method / algebra / reading / memory / attention / exam technique
- Trigger: one category dominates across attempts
- Action: choose correct intervention type
S04 — Retry Elasticity (RE)
- Detects: responsiveness after feedback
- How to Measure: correct and retest same skill within 24–72h
- Trigger: same mistake repeats 3+ times
- Action: redesign drills + increase scaffolding
S05 — Transfer & Generalisation (TG)
- Detects: whether skill transfers across contexts
- How to Measure: same concept, new framing/source/paper
- Trigger: “can do worksheet A, fails worksheet B”
- Action: generalisation training
S06 — Explanation Fidelity (EF)
- Detects: whether student can explain “why” clearly
- How to Measure: oral explanation + written reasoning
- Trigger: correct answer but explanation is broken or missing
- Action: P2→P3 upgrade gate
S07 — Independence Ratio (IR)
- Detects: dependence on hints/prompts
- How to Measure: count hints per problem; “prompt-to-move” rate
- Trigger: cannot progress without stepwise prompts
- Action: fade scaffolds; push P1→P2
S08 — Exception Handling (EH)
- Detects: robustness on twist/edge cases
- How to Measure: inject 1–2 non-template questions
- Trigger: template works but twist causes collapse
- Action: exception drills + P3 verification
B) Z0 Sensors (Atomic Skills / Topic Pockets)
S09 — Prerequisite Integrity Sensor (PIS)
- Detects: missing prerequisite bricks
- How to Measure: prerequisite checklist micro-test (5–10 items)
- Trigger: prerequisite failure blocks downstream work
- Action: repair prerequisites first (stop advanced grinding)
S10 — Micro-Drill Stability (MDS)
- Detects: unstable performance on micro-skills
- How to Measure: 10–20 rep drills; track consistency
- Trigger: large variability; “random correctness”
- Action: stabilise before advancing
S11 — Recall Latency (RL)
- Detects: slow retrieval of facts/formulas/definitions
- How to Measure: closed-book timed recall
- Trigger: knows it but too slow to retrieve reliably under exam load
- Action: spaced retrieval schedule (maintenance + repair)
S12 — Representation Switching (RS)
- Detects: inability to translate between forms
- How to Measure: word↔equation, diagram↔algebra, sentence↔inference conversions
- Trigger: student succeeds only in one representation
- Action: multi-representation practice
S13 — Misconception Trigger Sensor (MTS)
- Detects: repeatable misconception patterns
- How to Measure: targeted misconception items
- Trigger: same wrong pattern repeats across papers
- Action: misconception correction protocol (expose → name → counterexample → rebuild → retest)
C) Z1 Sensors (Student-in-Role / Human Factors)
S14 — Attention Drift Sensor (ADS)
- Detects: attention drop across session time
- How to Measure: accuracy trend over minutes 0–45
- Trigger: consistent decline after a predictable time threshold
- Action: redesign session blocks + breaks (reduce load)
S15 — Anxiety / Threat Response Sensor (ATR)
- Detects: threat mode hijacking cognition
- How to Measure: blanking/avoidance spikes under evaluation
- Trigger: practice OK, test context collapses
- Action: reduce load + gradual exposure + rebuild safety
S16 — Sleep / Energy Correlation Sensor (SECS)
- Detects: performance tightly coupled to sleep/energy
- How to Measure: simple sleep log vs accuracy/time stalls
- Trigger: predictable slump linked to sleep debt
- Action: protect sleep; move hard work to high-energy windows
S17 — Motivation & Avoidance Sensor (MAS)
- Detects: avoidance loops
- How to Measure: homework delay patterns, stalling behaviors
- Trigger: repeated “tomorrow” loop + missing reps
- Action: smaller tasks + fast feedback + micro-wins (strengthen buffers)
S18 — Self-Correction Sensor (SCS)
- Detects: ability to catch own mistakes
- How to Measure: enforce a “check pass” before submission
- Trigger: avoidable errors persist
- Action: install checking protocol (repair reliability)
S19 — Help-Seeking Quality Sensor (HSQ)
- Detects: whether questions asked are diagnostic
- How to Measure: can student say “I’m stuck at step 3 because ___”
- Trigger: vague “I don’t know” dominates
- Action: teach diagnostics language (repair the meta-skill)
D) Verification Sensors (Upgrade Verification OS)
S20 — Gate Test Sensor (GTS)
- Detects: real readiness vs lucky run
- How to Measure: pass 2–3 varied forms
- Trigger: pass one style but fail variations
- Action: do not upgrade Phase until stable
S21 — Anti-Cram Robustness Sensor (ACRS)
- Detects: collapse after 7–21 days
- How to Measure: delayed retest
- Trigger: rapid decay after “mastery”
- Action: rebuild maintenance loop
S22 — Closed-Book Retrieval Sensor (CBRS)
- Detects: internalisation vs dependence on notes
- How to Measure: closed-book mini-quiz
- Trigger: cannot perform without notes
- Action: enforce retrieval practice (verify upgrade)
S23 — Under-Noise Test Sensor (UNTS)
- Detects: performance under distractions/time/noise
- How to Measure: timed conditions + mild distractions
- Trigger: home OK, exam simulation collapses
- Action: harden under noise (verify upgrade)
E) Drift Sensors (Early Warning)
S24 — Micro-Regression Sensor (MRS)
- Detects: first small drop in stable skill
- How to Measure: weekly micro-check per mastered topic
- Trigger: new minor errors in “mastered” content
- Action: immediate small refresh (maintain)
S25 — Variance Spike Sensor (VSS)
- Detects: instability (randomness)
- How to Measure: rolling variance in accuracy/time
- Trigger: one day 90%, next day 40% without clear cause
- Action: check sleep/anxiety/prereqs; reduce load
S26 — Forgetting Curve Sensor (FCS)
- Detects: memory half-life per topic
- How to Measure: spaced retests; track decay interval
- Trigger: consistent fade after X days/weeks
- Action: maintenance scheduling
S27 — Confidence–Reality Gap Sensor (CRGS)
- Detects: calibration failure (overconfidence/helplessness)
- How to Measure: predicted score vs actual score
- Trigger: persistent mismatch
- Action: recalibrate self-model
F) Load Sensors (Overload / Underload)
S28 — Workload Compression Sensor (WCS)
- Detects: too many subjects compressing time budget
- How to Measure: weekly calendar vs task volume
- Trigger: constant rushing + no recovery windows
- Action: triage + minimum viable targets (reduce load)
S29 — Cognitive Load Sensor (CLS)
- Detects: task exceeds working memory
- How to Measure: mid-solution loss, skipped steps, messy overload
- Trigger: consistent overload symptoms
- Action: chunking + templates + smaller steps (reduce load)
S30 — Deadline Pressure Sensor (DPS)
- Detects: panic mode due to deadlines
- How to Measure: “no time” narrative + rushed errors
- Trigger: deadlines drive error spikes and avoidance
- Action: repair routing + reduce incoming load
G) Buffer Sensors (Family / Tuition / Support Lattice)
S31 — Parent Buffer Integrity Sensor (PBIS)
- Detects: home support helps vs harms
- How to Measure: conflict frequency + consistency of rules
- Trigger: support becomes a stress amplifier
- Action: parent protocol (strengthen buffers)
S32 — Study Environment Sensor (SES)
- Detects: environment friction
- How to Measure: sustained focus blocks; distraction count
- Trigger: cannot hold 25 minutes focus reliably
- Action: environment redesign (strengthen buffers)
S33 — Tutor/Teacher Feedback Latency Sensor (TFLS)
- Detects: how long errors remain uncorrected
- How to Measure: days/weeks between mistake and correction
- Trigger: wrong method persists for weeks
- Action: shorten feedback loop (strengthen buffers)
S34 — Repair Throughput Sensor (RTS)
- Detects: repair volume vs damage volume
- How to Measure: topics fixed/week vs topics breaking/week
- Trigger: falling behind despite effort
- Action: increase repair throughput or cut load
H) Curriculum Reference Sensors (Syllabus as Constraints)
S35 — Coverage Map Sensor (CMS)
- Detects: real coverage vs assumed coverage
- How to Measure: topic checklist + proof-of-mastery
- Trigger: “covered” topics fail gate checks
- Action: coverage truth map (repair planning)
S36 — Dependency Graph Sensor (DGS)
- Detects: prerequisite chain behind failures
- How to Measure: cluster failures; map upstream causes
- Trigger: repeated downstream failures from one upstream gap
- Action: repair in correct order
S37 — Exam Blueprint Alignment Sensor (EBAS)
- Detects: practice mismatch vs exam demand
- How to Measure: tag items by exam skill type
- Trigger: easy drills dominate while exam requires mixed reasoning
- Action: adjust practice mix (reduce waste)
I) Behaviour & Process Sensors (Execution Quality)
S38 — Homework Completion Integrity Sensor (HCIS)
- Detects: real completion vs copied completion
- How to Measure: “redo without looking” spot checks
- Trigger: cannot reproduce own submitted work
- Action: enforce integrity + shrink tasks
S39 — Workmanship Sensor (WS)
- Detects: execution clarity (layout, units, labels, step discipline)
- How to Measure: mark loss due to messiness/process
- Trigger: correct thinking lost to poor execution
- Action: standardise work format (repair reliability)
S40 — Checking Protocol Sensor (CPS)
- Detects: systematic checking habit
- How to Measure: checklist compliance (units, reasonableness, inverse check)
- Trigger: avoidable errors persist
- Action: install check loop as habit
J) Outcome Sensors (Interpret Correctly)
S41 — Score Trajectory Sensor (STS)
- Detects: slope of improvement
- How to Measure: rolling trend across tests
- Trigger: plateau/regression despite work
- Action: pivot plan or repair deeper
S42 — Rank/Percentile Context Sensor (RPCS)
- Detects: cohort-relative performance
- How to Measure: percentile movement over time
- Trigger: score stable but percentile falls
- Action: adjust intensity/strategy
S43 — Paper-to-Paper Consistency Sensor (PPCS)
- Detects: reliability across different papers
- How to Measure: variance across 3 papers
- Trigger: A then E then B = unstable
- Action: treat as Phase instability, rebuild fundamentals
K) Corridor Sensors (Z3: Transitions & Seasons)
S44 — Transition Shock Sensor (TSS)
- Detects: Primary→Secondary, Sec2→Sec3, teacher change shocks
- How to Measure: Phase drop after transitions
- Trigger: sudden instability after a change
- Action: bridging modules + pre-emptive repairs
S45 — Examination Season Shock Sensor (ESSS)
- Detects: systemic overload periods
- How to Measure: multi-subject collision + fatigue signals
- Trigger: burnout risk rising + performance volatility
- Action: triage + protect sleep + narrow targets
S46 — System Friction Sensor (SFS)
- Detects: logistics/admin friction stealing learning time
- How to Measure: missed lessons, late starts, chaotic schedule
- Trigger: routine breaks repeatedly
- Action: tighten routines + protect learning windows
Weekly Operating Loop (Detect → Repair → Verify → Maintain)
Weekly (30–60 minutes)
- Detect: run S24 + 1 topic gate (S20)
- Classify: update Phase per topic using S01/S02/S03/S07
- Repair: smallest Z0 repair that moves Phase (S09–S13)
- Verify: closed-book (S22) + alternate-form transfer (S05)
- Maintain: schedule refresh using S26 (prevent drift)
Daily (10–15 minutes)
- 1 micro-drill (S10) + 1 retrieval burst (S11/S22)
- 1 workmanship/check pass (S39/S40)
Minimal Must-Install Pack (Fastest Working System)
If you want the smallest complete panel:
S01, S02, S03, S07, S20, S22, S24, S29, S33, S41
eduKateOS Sensor Library (Install → Detect → Act)
Copy/paste block. Edit names to match your pages.
A) Core Phase Sensors (P0–P3) — the “Phase Instrument Panel”
S01 — Accuracy Under Load (AUL)
- Detects: whether performance collapses when difficulty/time-pressure increases
- Signals: easy questions OK, exam questions fail; late-paper cliff; careless bursts
- Use: Phase classification (P0/P1/P2/P3) per topic
S02 — Time-to-Solve Distribution (TSD)
- Detects: hidden P0 masked by lucky correctness
- Signals: correct but slow; long stalls; “one question eats 12 minutes”
- Use: Education TTC (Time-to-Competence) + pacing repair
S03 — Error Taxonomy Sensor (ETS)
- Detects: what kind of failure dominates
- Buckets: concept gap / method gap / algebra slip / reading/interpretation / memory lapse / attention drift / exam technique
- Use: correct intervention type (teach vs drill vs scaffold vs repair)
S04 — Retry Elasticity (RE)
- Detects: learning responsiveness after feedback
- Signals: same mistake repeats 3+ times = P0/P1; fixes quickly = P2/P3
- Use: coaching intensity + homework design
S05 — Transfer & Generalisation (TG)
- Detects: whether skill transfers to new contexts
- Signals: can do worksheet A, fails on worksheet B with same concept
- Use: distinguish “pattern memorised” vs “concept installed”
S06 — Explanation Fidelity (EF)
- Detects: whether student can explain the “why” clearly
- Signals: correct answer but cannot explain steps/assumptions
- Use: Phase upgrade gate (P2→P3 requires teachable explanation)
S07 — Independence Ratio (IR)
- Detects: dependency on hints/scaffolds
- Signals: only moves when prompted; asks “is this correct?” each step
- Use: P1→P2 transition monitoring
S08 — Exception Handling (EH)
- Detects: robustness when problem deviates from template
- Signals: panic on twist questions; breaks when numbers look “weird”
- Use: P3 verification (handles edge-cases calmly)
B) Z0 Sensors (Atomic Skills / “Pocket Sensors”) — install at topic level
S09 — Prerequisite Integrity Sensor (PIS)
- Detects: missing prerequisite bricks (fractions, algebra, ratio, indices, grammar)
- Signals: random failures; “I forgot how” on basics
- Use: stop wasting time on advanced topics until prerequisites restored
S10 — Micro-Drill Stability (MDS)
- Detects: stability on tiny drills (10–20 reps)
- Signals: accuracy fluctuates >20% day-to-day
- Use: drift detection + refresh scheduling
S11 — Recall Latency (RL)
- Detects: slow retrieval of formulas/definitions/vocab
- Signals: knows it but takes too long to recall
- Use: memory half-life maintenance (spaced retrieval)
S12 — Representation Switching (RS)
- Detects: ability to switch forms (word↔equation, diagram↔algebra, sentence↔inference)
- Signals: stuck because only one representation works
- Use: unlock multi-path solving (prevents brittle learning)
S13 — Misconception Trigger Sensor (MTS)
- Detects: classic misconceptions per topic
- Signals: consistent wrong pattern (sign errors, ratio inversion, science cause-effect reversal)
- Use: targeted misconception correction (fastest gains)
C) Z1 Sensors (Student-in-Role) — the “Human Factors Layer”
S14 — Attention Drift Sensor (ADS)
- Detects: drop in attention over session/time
- Signals: accuracy decreases after minute 25–35; careless spike
- Use: session design, break timing, shorter cycles
S15 — Anxiety / Threat Response Sensor (ATR)
- Detects: threat mode hijacking cognition
- Signals: blanking, avoidance, perfection paralysis, tears/anger
- Use: reduce load, rebuild safety, micro-wins, gradual exposure
S16 — Sleep / Energy Correlation Sensor (SECS)
- Detects: performance tied to sleep/energy
- Signals: predictable slump days; late-night study backfires
- Use: schedule hard work when brain is usable
S17 — Motivation & Avoidance Sensor (MAS)
- Detects: avoidance behaviors (stalling, “later”, missing homework)
- Signals: “I’ll do tomorrow” loop; fake busywork
- Use: redesign tasks to be smaller + high-feedback
S18 — Self-Correction Sensor (SCS)
- Detects: whether student catches own mistakes
- Signals: submits without checking; cannot spot inconsistency
- Use: build checking protocol (P2 reliability)
S19 — Help-Seeking Quality Sensor (HSQ)
- Detects: whether questions are productive
- Signals: “I don’t know” vs “I’m stuck at step 3 because…”
- Use: teach diagnostics language (massive acceleration)
D) Verification Sensors (Upgrade Verification OS) — prevent fake upgrades & P3→P0 traps
S20 — Gate Test Sensor (GTS)
- Detects: true readiness via short gate tests
- Rules: must pass 2–3 different forms, not one paper
- Use: certify P1/P2/P3 per topic
S21 — Anti-Cram Robustness Sensor (ACRS)
- Detects: whether performance survives 7–21 days later
- Signals: instant drop after test = not installed
- Use: stop “temporary P2” illusions
S22 — Closed-Book Retrieval Sensor (CBRS)
- Detects: whether knowledge is internalised
- Signals: only works with notes open
- Use: enforce retrieval practice before exam season
S23 — Under-Noise Test Sensor (UNTS)
- Detects: performance under distractions/time/noisy context
- Signals: home OK, exam hall collapse
- Use: simulate exam conditions to harden P3
E) Drift Sensors (Early Warning) — detect Phase decay before collapse
S24 — Micro-Regression Sensor (MRS)
- Detects: first small drop in a stable topic
- Signals: new minor errors in previously mastered steps
- Use: immediate small refresh (cheapest repair)
S25 — Variance Spike Sensor (VSS)
- Detects: instability (performance becomes “random”)
- Signals: one day 90%, next day 40% without reason
- Use: check sleep/stress/prerequisites + reduce load
S26 — Forgetting Curve Sensor (FCS)
- Detects: memory half-life per topic
- Signals: reliable for 2 weeks then fades
- Use: schedule spaced maintenance
S27 — Confidence–Reality Gap Sensor (CRGS)
- Detects: overconfidence or learned helplessness
- Signals: “I know” but fails; or “I can’t” but succeeds
- Use: calibrate self-model (prevents self-sabotage)
F) Load Sensors (Overload / Underload) — keep student inside safe operating envelope
S28 — Workload Compression Sensor (WCS)
- Detects: too many subjects/tests compressing time budget
- Signals: constant rushing; sleep reduction; skipping basics
- Use: triage plan + minimum viable targets
S29 — Cognitive Load Sensor (CLS)
- Detects: tasks exceed working memory capacity
- Signals: loses track mid-solution; messy work; step skipping
- Use: chunking, templates, shorter steps, worked example ladders
S30 — Deadline Pressure Sensor (DPS)
- Detects: time-pressure turning learning into panic
- Signals: “No time” becomes dominant narrative
- Use: switch to repair routing + high-yield drills
G) Buffer Sensors (Family / Tuition / Support Lattice) — detect when buffers are failing
S31 — Parent Buffer Integrity Sensor (PBIS)
- Detects: whether home support helps or harms
- Signals: nagging fights, micromanagement, inconsistent rules
- Use: parent protocol (calm + structure + short checks)
S32 — Study Environment Sensor (SES)
- Detects: environment friction (noise, phone, clutter, chaos)
- Signals: cannot sustain 25 minutes focus
- Use: environment redesign (cheap but powerful)
S33 — Tutor / Teacher Feedback Latency Sensor (TFLS)
- Detects: how long student waits for correction
- Signals: repeats wrong method for weeks
- Use: shorten feedback loop (fast Phase gains)
S34 — Repair Throughput Sensor (RTS)
- Detects: whether weekly repair volume exceeds damage volume
- Signals: falling behind despite effort
- Use: increase repair throughput or reduce incoming load
H) Curriculum Coverage Sensors (Syllabus as Reference Constraint)
S35 — Coverage Map Sensor (CMS)
- Detects: what is truly covered vs assumed covered
- Signals: “we learned already” but never mastered
- Use: coverage truth map per topic
S36 — Dependency Graph Sensor (DGS)
- Detects: which topics depend on which prerequisites
- Signals: repeated failure clusters
- Use: route repairs in correct order (stop random tuition)
S37 — Exam Blueprint Alignment Sensor (EBAS)
- Detects: mismatch between practice and actual exam demand
- Signals: doing easy drills while exam tests mixed reasoning
- Use: shift practice mix to exam reality
I) Behavioural & Process Sensors (Execution Quality)
S38 — Homework Completion Integrity Sensor (HCIS)
- Detects: real completion vs fake completion
- Signals: copied answers; “done” but cannot redo
- Use: enforce redo checks, oral explain, mini-quizzes
S39 — Workmanship Sensor (WS)
- Detects: layout clarity, step discipline, units, labels
- Signals: correct thinking lost to messy execution
- Use: standardise work format (raises reliability)
S40 — Checking Protocol Sensor (CPS)
- Detects: whether student checks systematically
- Signals: never verifies; loses marks to avoidable errors
- Use: install “check loop” as habit (P2→P3 gate)
J) Outcome Sensors (Z2/Z3 Outputs) — results, but interpreted correctly
S41 — Score Trajectory Sensor (STS)
- Detects: slope of improvement, not just absolute score
- Signals: plateaus, regressions, volatility
- Use: decide if plan works
S42 — Rank / Percentile Context Sensor (RPCS)
- Detects: performance relative to cohort
- Signals: score stable but percentile drops (cohort improves faster)
- Use: adjust intensity
S43 — Paper-to-Paper Consistency Sensor (PPCS)
- Detects: reliability across different papers
- Signals: one paper A, next paper E = unstable
- Use: treat as Phase instability, not “bad luck”
K) Corridor Sensors (Z3) — cross-institution “flow” signals (optional but powerful)
S44 — Transition Shock Sensor (TSS)
- Detects: Primary→Secondary, Sec2→Sec3, topic jumps, new teacher
- Signals: sudden Phase drop after transitions
- Use: pre-emptive bridging modules
S45 — Examination Season Shock Sensor (ESSS)
- Detects: systemic overload periods
- Signals: multi-subject collision, burnout risk
- Use: triage + protect sleep + narrow targets
S46 — System Friction Sensor (SFS)
- Detects: admin/logistics friction causing learning loss (travel, schedule chaos)
- Signals: missed lessons, late starts, inconsistent routines
- Use: tighten routines, protect learning windows
L) Minimal “Must-Install” Pack (if you want the smallest complete instrument panel)
- S01 AUL, 2) S02 TSD, 3) S03 ETS, 4) S07 IR, 5) S20 GTS, 6) S24 MRS, 7) S29 CLS, 8) S33 TFLS, 9) S35 CMS, 10) S41 STS
M) The eduKateOS Rule (so sensors don’t become noise)
- Every sensor must map to an action: Repair / Reduce Load / Upgrade Verification / Buffer Strengthening / Drift Maintenance.
- No action = no sensor.
- Phase is the single summary gauge: Sensors exist to classify Phase and prevent P3→P0 collapse.
Education OS Sensors (eduKateOS) — Full Suite Instrument Panel (Master Page)
Suggested canonical slug (this page): education-os-sensors-edukateos-full-suite
Purpose: This is the master index + install guide for every eduKateOS sensor used to classify Phase (P0–P3), detect drift early, and route the correct repair action at Z0–Z3.
Definition Lock Box (Do Not Edit)
Education OS Sensor (eduKateOS): A named measurement that detects a specific failure mode (or stability signal) in learning, with a trigger threshold and a mapped action (Repair / Reduce Load / Verify Upgrade / Strengthen Buffer / Maintain).
Phase (P0–P3):
- P0: unsafe/unreliable; breaks often; fundamentals missing
- P1: works with scaffolding; depends on hints
- P2: reliable independent execution in defined scope
- P3: robust under load; handles exceptions; can explain/teach/standardise
Zoom Ladder (Z0–Z3):
- Z0: atomic skills (topic pockets: algebra, reading, inference, etc.)
- Z1: student-in-role (habits, attention, anxiety, routines)
- Z2: institution loop (school/tuition feedback latency, repair throughput)
- Z3: corridor/season transitions (exam season shocks, level transitions)
Rule: No action = no sensor. Sensors exist to convert noise into an operational decision.
What This Page Installs
- A complete sensor library (S01–S46)
- A standard sensor format (measure → threshold → action)
- A weekly operating loop (detect → classify → repair → verify → maintain)
- A “Phase Instrument Panel” so you can prevent P3→P0 collapse (regression)
Quick Start (7-Day Install Plan)
Day 1 — Baseline & Phase Map
- Run S01 AUL, S02 TSD, S03 ETS, S07 IR on 1–2 topics.
- Assign provisional Phase per topic (P0–P3).
Day 2 — Verification Gates
- Install S20 GTS + S22 CBRS for the same topics.
- Lock “pass rules” (2–3 forms, not one lucky paper).
Day 3 — Drift Early-Warning
- Install S24 MRS + S25 VSS + S26 FCS.
Day 4 — Load Control
- Install S29 CLS + S30 DPS.
- Reduce incoming load if repair can’t catch up.
Day 5 — Buffer & Feedback Loop
- Install S33 TFLS + S34 RTS + S32 SES.
Day 6 — Execution Quality
- Install S39 WS + S40 CPS + S38 HCIS.
Day 7 — Outcome Interpreted Correctly
- Install S41 STS + S43 PPCS (trajectory + consistency).
The eduKateOS Sensor Format (Standard Template)
Use this exact template whenever you create a new sensor page.
Sensor ID: S## — Name (Shortcode)
Detects: (the failure/stability signal)
How to Measure: (simple observable method)
Thresholds: (what counts as “triggered”)
Mapped Action: Repair / Reduce Load / Verify / Buffer / Maintain
Phase Link: What P0/P1/P2/P3 looks like under this sensor
Notes: common false positives / cautions
The Full Suite Sensor Library (S01–S46)
A) Core Phase Sensors (P0–P3) — “Phase Instrument Panel”
S01 — Accuracy Under Load (AUL)
- Detects: collapse when difficulty/time pressure increases
- How to measure: easy vs exam-grade set; compare accuracy + stability
- Action: Phase classify + route repair
S02 — Time-to-Solve Distribution (TSD)
- Detects: hidden weakness masked by occasional correctness
- How to measure: time per question; identify long-stall outliers
- Action: pacing repair + reduce cognitive load
S03 — Error Taxonomy Sensor (ETS)
- Detects: dominant error type (concept/method/algebra/reading/memory/attention/exam technique)
- How to measure: tag each error category per question
- Action: choose the correct intervention type
S04 — Retry Elasticity (RE)
- Detects: responsiveness to feedback
- How to measure: same concept retest after correction
- Action: adjust coaching intensity + drill design
S05 — Transfer & Generalisation (TG)
- Detects: whether skill transfers across contexts
- How to measure: same concept, different framing/paper/source
- Action: generalisation training (not pattern memorisation)
S06 — Explanation Fidelity (EF)
- Detects: teachability / “why” clarity
- How to measure: student explains steps + assumptions aloud
- Action: upgrade gate for P2→P3
S07 — Independence Ratio (IR)
- Detects: dependence on prompts/hints
- How to measure: count hints per problem; monitor “prompt-to-move”
- Action: fade scaffolds; push P1→P2
S08 — Exception Handling (EH)
- Detects: robustness on twist/edge cases
- How to measure: inject 1–2 “non-template” questions
- Action: P3 verification + exception drills
B) Z0 Sensors (Atomic Skills / Topic Pockets)
S09 — Prerequisite Integrity Sensor (PIS)
- Detects: missing prerequisite bricks
- How to measure: micro-checklist of prerequisites
- Action: repair prerequisites first (stop wasting time)
S10 — Micro-Drill Stability (MDS)
- Detects: unstable micro-skill performance
- How to measure: 10–20 rep mini-drills; track variance
- Action: stabilise before advancing
S11 — Recall Latency (RL)
- Detects: slow retrieval of facts/formulas/definitions
- How to measure: closed-book recall timed
- Action: spaced retrieval schedule
S12 — Representation Switching (RS)
- Detects: inability to switch between forms
- How to measure: word↔equation, diagram↔algebra, sentence↔inference tasks
- Action: multi-representation practice
S13 — Misconception Trigger Sensor (MTS)
- Detects: classic misconception patterns
- How to measure: trigger items designed to expose misconception
- Action: targeted misconception correction
C) Z1 Sensors (Student-in-Role / Human Factors)
S14 — Attention Drift Sensor (ADS)
- Detects: attention collapse across session time
- How to measure: accuracy trend across minutes 0–45
- Action: redesign session blocks + breaks
S15 — Anxiety / Threat Response Sensor (ATR)
- Detects: threat mode hijacking cognition
- How to measure: blanking/avoidance spikes during assessments
- Action: reduce load + gradual exposure + safety rebuild
S16 — Sleep / Energy Correlation Sensor (SECS)
- Detects: performance coupled to sleep/energy
- How to measure: simple sleep log vs accuracy/time
- Action: move hard work to high-energy windows
S17 — Motivation & Avoidance Sensor (MAS)
- Detects: avoidance loops
- How to measure: homework delays + stalling behaviors
- Action: smaller tasks + fast feedback + micro-wins
S18 — Self-Correction Sensor (SCS)
- Detects: ability to catch own mistakes
- How to measure: forced “check pass” before submission
- Action: install checking protocol (P2 reliability)
S19 — Help-Seeking Quality Sensor (HSQ)
- Detects: quality of questions asked
- How to measure: “where exactly stuck + why” clarity
- Action: teach diagnostics language (accelerates learning)
D) Verification Sensors (Upgrade Verification OS)
S20 — Gate Test Sensor (GTS)
- Detects: real readiness vs lucky run
- How to measure: pass 2–3 varied forms
- Action: certify Phase per topic
S21 — Anti-Cram Robustness Sensor (ACRS)
- Detects: collapse after 7–21 days
- How to measure: delayed retest
- Action: install maintenance + retrieval schedule
S22 — Closed-Book Retrieval Sensor (CBRS)
- Detects: internalisation vs dependence on notes
- How to measure: closed-book mini-quiz
- Action: enforce retrieval practice
S23 — Under-Noise Test Sensor (UNTS)
- Detects: performance under distractions/time/noise
- How to measure: timed conditions + mild distractions
- Action: harden for exam context
E) Drift Sensors (Early Warning)
S24 — Micro-Regression Sensor (MRS)
- Detects: first small drop in stable skill
- How to measure: weekly micro-check per mastered topic
- Action: immediate small refresh
S25 — Variance Spike Sensor (VSS)
- Detects: instability (randomness)
- How to measure: rolling variance in accuracy/time
- Action: check sleep/stress/prereqs; reduce load
S26 — Forgetting Curve Sensor (FCS)
- Detects: memory half-life per topic
- How to measure: spaced retests; track decay interval
- Action: maintenance scheduling
S27 — Confidence–Reality Gap Sensor (CRGS)
- Detects: calibration failure (overconfidence / helplessness)
- How to measure: predicted score vs actual score
- Action: recalibrate self-model + rebuild trust
F) Load Sensors (Overload / Underload)
S28 — Workload Compression Sensor (WCS)
- Detects: too many subjects compressing time budget
- How to measure: weekly calendar vs task volume
- Action: triage + minimum viable targets
S29 — Cognitive Load Sensor (CLS)
- Detects: task exceeds working memory
- How to measure: mid-solution loss, skipped steps, messy overload
- Action: chunking + templates + smaller steps
S30 — Deadline Pressure Sensor (DPS)
- Detects: panic mode due to deadlines
- How to measure: “no time” narrative dominance + rushed errors
- Action: switch to repair routing + reduce incoming load
G) Buffer Sensors (Family / Tuition / Support Lattice)
S31 — Parent Buffer Integrity Sensor (PBIS)
- Detects: home support helps vs harms
- How to measure: conflict frequency + consistency of rules
- Action: parent protocol (calm + structure + short checks)
S32 — Study Environment Sensor (SES)
- Detects: environment friction
- How to measure: sustained focus blocks; distraction count
- Action: environment redesign
S33 — Tutor/Teacher Feedback Latency Sensor (TFLS)
- Detects: how long errors go uncorrected
- How to measure: days/weeks between mistake and correction
- Action: shorten feedback loop
S34 — Repair Throughput Sensor (RTS)
- Detects: repair volume vs damage volume
- How to measure: topics fixed per week vs topics breaking per week
- Action: increase repair throughput or cut load
H) Curriculum Reference Sensors (Syllabus as Constraints)
S35 — Coverage Map Sensor (CMS)
- Detects: real coverage vs assumed coverage
- How to measure: topic checklist with proof-of-mastery
- Action: coverage truth map
S36 — Dependency Graph Sensor (DGS)
- Detects: prerequisite dependency chain
- How to measure: cluster failures; map upstream causes
- Action: repair in correct order
S37 — Exam Blueprint Alignment Sensor (EBAS)
- Detects: practice mismatch vs exam demand
- How to measure: tag practice items by exam skill type
- Action: adjust practice mix
I) Behaviour & Process Sensors (Execution Quality)
S38 — Homework Completion Integrity Sensor (HCIS)
- Detects: real completion vs copied completion
- How to measure: “redo without looking” spot checks
- Action: integrity enforcement + smaller tasks
S39 — Workmanship Sensor (WS)
- Detects: execution clarity (layout, units, labels, step discipline)
- How to measure: mark loss due to presentation/process
- Action: standardise work format
S40 — Checking Protocol Sensor (CPS)
- Detects: presence of systematic checking
- How to measure: checklist compliance (units, reasonableness, inverse check)
- Action: install check loop as habit
J) Outcome Sensors (Interpret Correctly)
S41 — Score Trajectory Sensor (STS)
- Detects: slope of improvement
- How to measure: rolling trendline across tests
- Action: confirm plan works or pivot
S42 — Rank/Percentile Context Sensor (RPCS)
- Detects: cohort-relative performance
- How to measure: percentile movement over time
- Action: adjust intensity if cohort outruns
S43 — Paper-to-Paper Consistency Sensor (PPCS)
- Detects: reliability across different papers
- How to measure: variance across 3 papers
- Action: treat as Phase instability, not luck
K) Corridor Sensors (Z3: Transitions & Seasons)
S44 — Transition Shock Sensor (TSS)
- Detects: Primary→Secondary, Sec2→Sec3, teacher change shocks
- How to measure: Phase drop right after transitions
- Action: bridging modules + pre-emptive repairs
S45 — Examination Season Shock Sensor (ESSS)
- Detects: systemic overload periods
- How to measure: multi-subject collision + fatigue signals
- Action: triage + protect sleep + narrow targets
S46 — System Friction Sensor (SFS)
- Detects: logistics/admin friction stealing learning time
- How to measure: missed lessons, late starts, chaotic schedule
- Action: tighten routines + protect learning windows
Minimal Must-Install Pack (If You Want the Fastest Working System)
Install these first, then expand:
- S01, S02, S03, S07, S20, S24, S29, S33, S35, S41
Weekly Operating Loop (eduKateOS “Detect → Repair → Verify → Maintain”)
Weekly (30–60 minutes)
- Detect: run S24 + one topic gate (S20)
- Classify: update Phase per topic using S01/S02/S03/S07
- Repair: pick the smallest repair that moves Phase (Z0 first)
- Verify: closed-book mini-check (S22) + 1 alternate-form check (S05)
- Maintain: schedule spaced refresh (S26) for anything newly stabilised
Daily (10–15 minutes)
- 1 micro-drill (S10) + 1 retrieval burst (S11/S22)
- 1 workmanship/checking pass (S39/S40)
Escalation Ladder (When Sensors Trigger)
- If S09 (prereqs) triggers: stop advanced work → repair prerequisites
- If S29/S30 triggers: reduce load immediately (protect stability)
- If S25 triggers (variance spike): check sleep/anxiety/attention (S14–S16)
- If S20 fails twice: treat as P0/P1; return to Z0 repairs
- If S21 fails (anti-cram): rebuild maintenance loop; don’t “advance”
Definition Lock Box (Do Not Edit)
Education OS Sensor (eduKateOS): A named measurement that detects a specific learning failure mode (or stability signal) with a trigger threshold and a mapped action.
Mapped Actions (only 5):
- Repair (Z0) — fix atomic skill gaps
- Reduce Load — prevent overload collapse
- Verify Upgrade — confirm real mastery (stop fake upgrades)
- Strengthen Buffers — family/tuition/environment feedback loops
- Maintain — prevent drift (spaced refresh)
Phase (P0–P3):
- P0: unsafe/unreliable; breaks often; fundamentals missing
- P1: works with scaffolding; depends on hints
- P2: reliable independent execution in defined scope
- P3: robust under load; handles exceptions; can explain/teach/standardise
Zoom Ladder (Z0–Z3):
- Z0: atomic skills (topic pockets)
- Z1: student-in-role (attention, anxiety, routines, habits)
- Z2: institution loops (feedback latency, repair throughput)
- Z3: corridors/seasons/transitions (exam season shock, level transition shock)
Rule: No action = no sensor. Sensors exist to convert noise into a decision.
What This Page Installs
This is the eduKateOS Sensor Library — the complete “instrument panel” to:
- classify Phase per topic (P0–P3),
- detect drift early before collapse,
- route the correct repair action (Z0 first),
- prevent P3→P0 (regression after “seems OK” periods).
Quick Install Plan (7 Days)
Day 1 — Baseline + Phase Map
Install and run: S01, S02, S03, S07 on 1–2 topics.
Day 2 — Verification Gates (Stop Fake Upgrades)
Install and run: S20, S22 (2–3 varied forms, closed-book).
Day 3 — Drift Early Warning
Install: S24, S25, S26.
Day 4 — Load Control
Install: S29, S30 (reduce load if repair cannot catch up).
Day 5 — Buffer + Feedback Loop
Install: S33, S34, S32.
Day 6 — Execution Quality
Install: S39, S40, S38.
Day 7 — Outcome Interpreted Correctly
Install: S41, S43 (trajectory + consistency).
The eduKateOS Sensor Format (Standard Template)
Sensor ID: S## — Name (Shortcode)
Detects: What failure/stability signal it measures
How to Measure: Simple observable method
Trigger Threshold: What counts as “triggered”
Mapped Action: Repair / Reduce Load / Verify Upgrade / Strengthen Buffers / Maintain
Phase Link: What P0/P1/P2/P3 looks like under this sensor
Notes: Common false positives & cautions
FULL SUITE SENSOR LIBRARY (S01–S46)
A) Core Phase Sensors (P0–P3) — The “Phase Instrument Panel”
S01 — Accuracy Under Load (AUL)
- Detects: collapse when difficulty/time-pressure increases
- How to Measure: easy set vs exam-grade set; compare accuracy + stability
- Trigger: accuracy drops sharply or becomes erratic when load rises
- Action: Phase classify + route repair
S02 — Time-to-Solve Distribution (TSD)
- Detects: hidden weakness masked by occasional correctness
- How to Measure: time per question; flag stall outliers
- Trigger: 1–2 questions consume disproportionate time repeatedly
- Action: pacing repair + reduce cognitive load
S03 — Error Taxonomy Sensor (ETS)
- Detects: dominant error type
- How to Measure: tag each error: concept / method / algebra / reading / memory / attention / exam technique
- Trigger: one category dominates across attempts
- Action: choose correct intervention type
S04 — Retry Elasticity (RE)
- Detects: responsiveness after feedback
- How to Measure: correct and retest same skill within 24–72h
- Trigger: same mistake repeats 3+ times
- Action: redesign drills + increase scaffolding
S05 — Transfer & Generalisation (TG)
- Detects: whether skill transfers across contexts
- How to Measure: same concept, new framing/source/paper
- Trigger: “can do worksheet A, fails worksheet B”
- Action: generalisation training
S06 — Explanation Fidelity (EF)
- Detects: whether student can explain “why” clearly
- How to Measure: oral explanation + written reasoning
- Trigger: correct answer but explanation is broken or missing
- Action: P2→P3 upgrade gate
S07 — Independence Ratio (IR)
- Detects: dependence on hints/prompts
- How to Measure: count hints per problem; “prompt-to-move” rate
- Trigger: cannot progress without stepwise prompts
- Action: fade scaffolds; push P1→P2
S08 — Exception Handling (EH)
- Detects: robustness on twist/edge cases
- How to Measure: inject 1–2 non-template questions
- Trigger: template works but twist causes collapse
- Action: exception drills + P3 verification
B) Z0 Sensors (Atomic Skills / Topic Pockets)
S09 — Prerequisite Integrity Sensor (PIS)
- Detects: missing prerequisite bricks
- How to Measure: prerequisite checklist micro-test
- Trigger: prerequisite failure blocks downstream topics
- Action: repair prerequisites first
S10 — Micro-Drill Stability (MDS)
- Detects: unstable micro-skill performance
- How to Measure: 10–20 rep drills; track consistency
- Trigger: performance fluctuates widely for same micro-skill
- Action: stabilise before advancing
S11 — Recall Latency (RL)
- Detects: slow retrieval of facts/formulas/definitions
- How to Measure: closed-book timed recall
- Trigger: knows but too slow to retrieve reliably
- Action: spaced retrieval schedule
S12 — Representation Switching (RS)
- Detects: inability to switch forms
- How to Measure: word↔equation, diagram↔algebra, sentence↔inference tasks
- Trigger: only one representation works; others cause failure
- Action: multi-representation practice
S13 — Misconception Trigger Sensor (MTS)
- Detects: classic misconception patterns
- How to Measure: targeted misconception items
- Trigger: consistent wrong pattern repeats
- Action: misconception correction protocol
C) Z1 Sensors (Student-in-Role / Human Factors)
S14 — Attention Drift Sensor (ADS)
- Detects: attention drop across session time
- How to Measure: accuracy trend over minutes 0–45
- Trigger: consistent decline after a time threshold
- Action: redesign session blocks + breaks
S15 — Anxiety / Threat Response Sensor (ATR)
- Detects: threat mode hijacking cognition
- How to Measure: blanking/avoidance spikes under evaluation
- Trigger: student collapses only in test context
- Action: reduce load + gradual exposure + safety rebuild
S16 — Sleep / Energy Correlation Sensor (SECS)
- Detects: performance coupled to sleep/energy
- How to Measure: simple sleep log vs accuracy/time
- Trigger: predictable slump tied to sleep debt
- Action: move hard work to high-energy windows
S17 — Motivation & Avoidance Sensor (MAS)
- Detects: avoidance loops
- How to Measure: homework delay patterns, stalling behaviors
- Trigger: repeated “tomorrow” loop + missing reps
- Action: smaller tasks + fast feedback + micro-wins
S18 — Self-Correction Sensor (SCS)
- Detects: ability to catch own mistakes
- How to Measure: forced “check pass” before submission
- Trigger: errors persist that a check would catch
- Action: install checking protocol (P2 reliability)
S19 — Help-Seeking Quality Sensor (HSQ)
- Detects: quality of questions asked
- How to Measure: can they specify where/why stuck
- Trigger: vague “I don’t know” dominates
- Action: teach diagnostics language
D) Verification Sensors (Upgrade Verification OS)
S20 — Gate Test Sensor (GTS)
- Detects: real readiness vs lucky run
- How to Measure: pass 2–3 varied forms
- Trigger: pass one style but fail variations
- Action: do not upgrade Phase until stable
S21 — Anti-Cram Robustness Sensor (ACRS)
- Detects: collapse after 7–21 days
- How to Measure: delayed retest
- Trigger: rapid decay after “mastery”
- Action: rebuild maintenance loop
S22 — Closed-Book Retrieval Sensor (CBRS)
- Detects: internalisation vs dependence on notes
- How to Measure: closed-book mini-quiz
- Trigger: cannot perform without notes
- Action: enforce retrieval practice
S23 — Under-Noise Test Sensor (UNTS)
- Detects: performance under distractions/time/noise
- How to Measure: timed conditions + mild distractions
- Trigger: home OK but exam simulation collapses
- Action: harden under noise
E) Drift Sensors (Early Warning)
S24 — Micro-Regression Sensor (MRS)
- Detects: first small drop in stable skill
- How to Measure: weekly micro-check per mastered topic
- Trigger: new minor errors in “mastered” content
- Action: immediate small refresh
S25 — Variance Spike Sensor (VSS)
- Detects: instability (randomness)
- How to Measure: rolling variance in accuracy/time
- Trigger: one day 90%, next day 40% without clear cause
- Action: check sleep/anxiety/prereqs; reduce load
S26 — Forgetting Curve Sensor (FCS)
- Detects: memory half-life per topic
- How to Measure: spaced retests; track decay interval
- Trigger: consistent fade after X days/weeks
- Action: maintenance scheduling
S27 — Confidence–Reality Gap Sensor (CRGS)
- Detects: calibration failure (overconfidence/helplessness)
- How to Measure: predicted score vs actual score
- Trigger: persistent mismatch
- Action: recalibrate self-model
F) Load Sensors (Overload / Underload)
S28 — Workload Compression Sensor (WCS)
- Detects: too many subjects compressing time budget
- How to Measure: weekly calendar vs task volume
- Trigger: constant rushing + no recovery windows
- Action: triage + minimum viable targets
S29 — Cognitive Load Sensor (CLS)
- Detects: task exceeds working memory
- How to Measure: mid-solution loss, skipped steps, messy overload
- Trigger: consistent overload symptoms
- Action: chunking + templates + smaller steps
S30 — Deadline Pressure Sensor (DPS)
- Detects: panic mode due to deadlines
- How to Measure: “no time” narrative + rushed errors
- Trigger: deadlines drive error spikes and avoidance
- Action: repair routing + reduce incoming load
G) Buffer Sensors (Family / Tuition / Support Lattice)
S31 — Parent Buffer Integrity Sensor (PBIS)
- Detects: home support helps vs harms
- How to Measure: conflict frequency + consistency of rules
- Trigger: support becomes a stress amplifier
- Action: parent protocol (calm + structure + short checks)
S32 — Study Environment Sensor (SES)
- Detects: environment friction
- How to Measure: sustained focus blocks; distraction count
- Trigger: cannot hold 25 minutes focus reliably
- Action: environment redesign
S33 — Tutor/Teacher Feedback Latency Sensor (TFLS)
- Detects: how long errors remain uncorrected
- How to Measure: days/weeks between mistake and correction
- Trigger: repeated wrong method persists for weeks
- Action: shorten feedback loop
S34 — Repair Throughput Sensor (RTS)
- Detects: repair volume vs damage volume
- How to Measure: topics fixed/week vs topics breaking/week
- Trigger: falling behind despite effort
- Action: increase repair throughput or cut load
H) Curriculum Reference Sensors (Syllabus as Constraints)
S35 — Coverage Map Sensor (CMS)
- Detects: real coverage vs assumed coverage
- How to Measure: topic checklist + proof-of-mastery
- Trigger: “covered” topics fail gate checks
- Action: coverage truth map
S36 — Dependency Graph Sensor (DGS)
- Detects: prerequisite chain behind failures
- How to Measure: cluster failures; map upstream causes
- Trigger: repeated downstream failures from one upstream gap
- Action: repair in correct order
S37 — Exam Blueprint Alignment Sensor (EBAS)
- Detects: practice mismatch vs exam demand
- How to Measure: tag items by exam skill type
- Trigger: doing easy drills while exam needs mixed reasoning
- Action: adjust practice mix
I) Behaviour & Process Sensors (Execution Quality)
S38 — Homework Completion Integrity Sensor (HCIS)
- Detects: real completion vs copied completion
- How to Measure: “redo without looking” spot checks
- Trigger: cannot reproduce own submitted work
- Action: enforce integrity + shrink tasks
S39 — Workmanship Sensor (WS)
- Detects: execution clarity (layout, units, labels, step discipline)
- How to Measure: mark loss due to messiness/process
- Trigger: correct thinking lost to poor execution
- Action: standardise work format
S40 — Checking Protocol Sensor (CPS)
- Detects: systematic checking habit
- How to Measure: checklist compliance (units, reasonableness, inverse check)
- Trigger: avoidable errors persist
- Action: install check loop as habit
J) Outcome Sensors (Interpret Correctly)
S41 — Score Trajectory Sensor (STS)
- Detects: slope of improvement
- How to Measure: rolling trend across tests
- Trigger: plateau/regression despite work
- Action: pivot plan or reduce load + repair deeper
S42 — Rank/Percentile Context Sensor (RPCS)
- Detects: cohort-relative performance
- How to Measure: percentile movement over time
- Trigger: score stable but percentile falls
- Action: adjust intensity/strategy
S43 — Paper-to-Paper Consistency Sensor (PPCS)
- Detects: reliability across different papers
- How to Measure: variance across 3 papers
- Trigger: A then E then B = unstable
- Action: treat as Phase instability, rebuild fundamentals
K) Corridor Sensors (Z3: Transitions & Seasons)
S44 — Transition Shock Sensor (TSS)
- Detects: Primary→Secondary, Sec2→Sec3, new teacher shocks
- How to Measure: Phase drop after transitions
- Trigger: sudden instability after a change
- Action: bridging modules + pre-emptive repairs
S45 — Examination Season Shock Sensor (ESSS)
- Detects: systemic overload periods
- How to Measure: multi-subject collision + fatigue signals
- Trigger: burnout risk rising + performance volatility
- Action: triage + protect sleep + narrow targets
S46 — System Friction Sensor (SFS)
- Detects: logistics/admin friction stealing learning time
- How to Measure: missed lessons, late starts, chaotic schedule
- Trigger: routine breaks repeatedly
- Action: tighten routines + protect learning windows
Minimal Must-Install Pack (Fastest Working System)
Install these first if you want the smallest complete panel:
S01, S02, S03, S07, S20, S24, S29, S33, S35, S41
Weekly Operating Loop (Detect → Repair → Verify → Maintain)
Weekly (30–60 minutes)
- Detect: run S24 + 1 topic gate (S20)
- Classify: update Phase per topic using S01/S02/S03/S07
- Repair: smallest Z0 repair that moves Phase (S09–S13)
- Verify: closed-book (S22) + alternate-form transfer (S05)
- Maintain: schedule refresh using S26 (prevent drift)
Daily (10–15 minutes)
- 1 micro-drill (S10) + 1 retrieval burst (S11/S22)
- 1 workmanship/check pass (S39/S40)
Definition Lock Box (Do Not Edit)
Sensor: a measurement with a trigger threshold and a mapped action.
Rule: No action = no sensor.
Actions: Repair (Z0) / Reduce Load / Verify Upgrade / Strengthen Buffers / Maintain.
Goal: classify Phase (P0–P3), detect drift early, prevent P3→P0 collapse.
What “Install” Means (In eduKateOS)
Installing a sensor means 3 things are defined:
- Where it runs (Z0 topic / Z1 student / Z2 loop / Z3 corridor)
- How it is measured (simple repeatable method)
- What it triggers (threshold → mapped action)
If any of these are missing, the sensor is not installed.
The Minimum Data You Need (No spreadsheets required)
You only need a weekly page section with:
- Topic list (3–8 active topics)
- Phase per topic (P0–P3)
- Notes: top 1–2 errors + top 1 load issue
- Next actions (Repair / Reduce Load / Verify / Buffer / Maintain)
Optional: time-per-question notes for S02.
Full Suite Install Order (Do This Sequence)
Stage 1 — Phase Instrument Panel (Core)
Install first because everything else depends on Phase truth:
- S01 Accuracy Under Load (AUL)
- S02 Time-to-Solve Distribution (TSD)
- S03 Error Taxonomy Sensor (ETS)
- S07 Independence Ratio (IR)
Output you must produce: a Phase label for each active topic.
Stage 2 — Upgrade Verification OS (Stop Fake Mastery)
Install second so you don’t build on illusions:
- S20 Gate Test Sensor (GTS)
- S22 Closed-Book Retrieval Sensor (CBRS)
- (Optional next) S05 Transfer & Generalisation (TG)
Rule: No topic upgrades Phase unless it passes S20 + S22.
Stage 3 — Drift Early Warning (Prevent Collapse)
Install third to catch decay before it becomes a crisis:
- S24 Micro-Regression Sensor (MRS)
- S25 Variance Spike Sensor (VSS)
- S26 Forgetting Curve Sensor (FCS)
Rule: If drift triggers, you repair immediately while it’s cheap.
Stage 4 — Load Control (Keep student inside safe envelope)
Install fourth because overload destroys everything:
- S29 Cognitive Load Sensor (CLS)
- S30 Deadline Pressure Sensor (DPS)
- (Optional) S28 Workload Compression Sensor (WCS)
Rule: If load triggers, you reduce load before doing more work.
Stage 5 — Z0 Repairs (Atomic Fixes that actually move Phase)
Install fifth so your repairs hit the real bottleneck:
- S09 Prerequisite Integrity Sensor (PIS)
- S10 Micro-Drill Stability (MDS)
- S11 Recall Latency (RL)
- S13 Misconception Trigger Sensor (MTS)
Rule: Z0 repairs first. No advanced topic grinding if prerequisites fail.
Stage 6 — Buffers & Feedback Loops (Z2 Support Lattice)
Install sixth so errors don’t persist for weeks:
- S33 Feedback Latency Sensor (TFLS)
- S34 Repair Throughput Sensor (RTS)
- S32 Study Environment Sensor (SES)
- (Optional) S31 Parent Buffer Integrity Sensor (PBIS)
Rule: Long feedback latency produces long-term damage.
Stage 7 — Execution Quality (Stop losing marks to process)
Install last because it stabilises outcomes:
- S39 Workmanship Sensor (WS)
- S40 Checking Protocol Sensor (CPS)
- S38 Homework Completion Integrity (HCIS)
How to Run Sensors in a Single Tuition Session (60–90 minutes)
Part 1 (10 min): Warm-up + Drift Check
- 5 questions from last week (S24)
- Note any variance (S25)
Part 2 (20–30 min): Core Diagnostic
- 6–10 mixed difficulty questions (S01)
- Record time per question (S02)
- Tag each error (S03)
- Count hints used (S07)
Part 3 (20–30 min): Z0 Repair Block
- Repair the dominant bottleneck: S09/S10/S11/S13
- Keep reps small but precise
Part 4 (10–15 min): Verification Gate
- Closed-book mini-check (S22)
- 1 alternate-form transfer check (S05)
- If stable → allow Phase upgrade; if not → stay and repair
Part 5 (2 min): Load Decision
- If cognitive overload is present (S29/S30), reduce load immediately next week.
Trigger → Action Table (The Only 5 Actions)
If Prerequisites fail (S09)
→ Repair (Z0) and stop advanced work.
If load is too high (S28/S29/S30)
→ Reduce Load (triage topics, cut volume, protect sleep).
If gate test fails (S20/S22)
→ Verify Upgrade (do not promote Phase; return to repair).
If drift triggers (S24/S25/S26)
→ Maintain (small refresh now, not big rescue later).
If feedback is slow / repairs can’t catch up (S33/S34)
→ Strengthen Buffers (shorten feedback loop, increase repair throughput).
The “Minimal Working Install” (If you only do 10)
Install these and eduKateOS becomes operational immediately:
S01, S02, S03, S07, S20, S22, S24, S29, S33, S41
Education OS Sensors — Weekly Operating Loop (Detect → Repair → Verify → Maintain)
Slug: education-os-sensors-weekly-operating-loop
Definition Lock Box (Do Not Edit)
Goal: Keep the student inside a stable learning envelope by detecting drift early, repairing at Z0, verifying upgrades, and maintaining mastery so Phase does not collapse (P3→P0).
The 5 Actions: Repair / Reduce Load / Verify Upgrade / Strengthen Buffers / Maintain.
The Weekly Rhythm (Simple, Repeatable, Scalable)
1) Detect (10–15 minutes)
Run these every week:
- S24 Micro-Regression (MRS): 5 quick questions from last week’s “mastered” material
- S25 Variance Spike (VSS): note if performance becomes random
- S02 Time-to-Solve (TSD): flag stalls (questions that eat time)
Output: Which topic drifted, and whether the drift is small (cheap) or large (urgent).
2) Classify Phase (10 minutes)
Update Phase per active topic using:
- S01 Accuracy Under Load (AUL)
- S03 Error Taxonomy (ETS)
- S07 Independence Ratio (IR)
Rule: Phase is assigned per topic, not as a personality label.
3) Repair (20–40 minutes)
Repair must start at Z0:
- If S09 Prerequisites triggered → repair prerequisites first
- If S13 Misconception triggered → correct misconception immediately
- If S11 Recall Latency triggered → install retrieval schedule
- If S10 Micro-Drill Stability triggered → stabilise micro-skill before advancing
Output: One bottleneck repaired (not 10 scattered topics).
4) Verify Upgrade (10–15 minutes)
No upgrade without verification:
- S22 Closed-Book Retrieval (CBRS): short closed-book check
- S20 Gate Test (GTS): pass 2–3 varied forms
- (Optional) S05 Transfer (TG): one “same concept, new framing” question
Rule: One lucky pass is not an upgrade.
5) Maintain (5 minutes)
Schedule anti-drift maintenance:
- S26 Forgetting Curve (FCS): set refresh intervals for stabilised topics
- Micro-maintenance beats crisis rescue.
Daily Micro-Loop (10–15 minutes)
This keeps Phase stable between sessions:
- Micro-drill (S10) — 10 minutes
- Retrieval burst (S11/S22) — 3–5 minutes
- Checking habit (S40) — 1 minute
The 1-Page Weekly Log (Copy/Paste Template)
Week of: ________
Active Topics (3–8 only)
- Topic 1: Phase __ | Drift? Y/N | Bottleneck: ____ | Action: ____
- Topic 2: Phase __ | Drift? Y/N | Bottleneck: ____ | Action: ____
- Topic 3: Phase __ | Drift? Y/N | Bottleneck: ____ | Action: ____
Sensor Signals (Fast Notes)
- S01 (Load Accuracy): ____________________
- S02 (Time Stalls): ______________________
- S03 (Error Type): _______________________
- S07 (Hint Dependence): __________________
- S24 (Micro Drift): _______________________
- S29/S30 (Load/Deadline): ________________
This Week’s One Repair Target (Z0 first)
- Target: __________________________
- Repair method used (S09/S10/S11/S13): ________
- Proof of repair (S22 + S20): ________________
Maintenance Scheduled (S26)
- Topic: ______ | Refresh: Day __ / Day __ / Day __
Trigger Rules (So You Don’t Guess)
If S24 triggers (micro-regression)
→ Maintain now (small refresh) before it becomes Phase collapse.
If S20/S22 fails twice
→ Do not advance. Treat as P0/P1 for that topic and return to Z0 repairs.
If S29/S30 triggers (overload/deadline panic)
→ Reduce load immediately. Too much work breaks learning.
If S33/S34 triggers (feedback too slow / repairs can’t catch up)
→ Strengthen buffers (shorten feedback loop, increase repair throughput).
What “Good” Looks Like (Operational Targets)
- Phase upgrades happen only after verification (S20 + S22).
- Drift is caught when it is small (S24).
- Repair throughput stays ahead of damage throughput (S34).
- Exam season becomes a controlled narrow envelope, not chaos (S45 + S30).
Education OS Sensors — Minimal Pack (Fastest Working System)
Slug: education-os-sensors-minimal-pack
Definition Lock Box (Do Not Edit)
Minimal Pack: The smallest set of sensors that makes eduKateOS operational.
Goal: Classify Phase truthfully, prevent fake upgrades, detect drift early, and keep learning stable under load.
Rule: If a sensor triggers, you must take one of 5 actions:
Repair / Reduce Load / Verify Upgrade / Strengthen Buffers / Maintain
The Minimal Pack (10 Sensors Only)
1) S01 — Accuracy Under Load (AUL)
Why it’s mandatory: tells you whether the student collapses when questions become exam-grade.
2) S02 — Time-to-Solve Distribution (TSD)
Why it’s mandatory: catches hidden weakness even when answers are sometimes correct.
3) S03 — Error Taxonomy Sensor (ETS)
Why it’s mandatory: prevents wrong intervention (drill vs teach vs fix reading vs fix algebra).
4) S07 — Independence Ratio (IR)
Why it’s mandatory: distinguishes P1 (scaffolded) from P2 (independent).
5) S20 — Gate Test Sensor (GTS)
Why it’s mandatory: stops fake upgrades; requires stability across varied forms.
6) S22 — Closed-Book Retrieval Sensor (CBRS)
Why it’s mandatory: ensures knowledge is inside the student, not in the notes.
7) S24 — Micro-Regression Sensor (MRS)
Why it’s mandatory: early warning drift detector (cheap to fix early).
8) S29 — Cognitive Load Sensor (CLS)
Why it’s mandatory: overload destroys learning even if tuition quality is high.
9) S33 — Feedback Latency Sensor (TFLS)
Why it’s mandatory: long correction delays create long-term damage.
10) S41 — Score Trajectory Sensor (STS)
Why it’s mandatory: confirms whether the system is improving outcomes over time.
How to Run the Minimal Pack (One Session Workflow)
Step 1 (10 min): Drift Check
- Run S24 with 5 quick questions from last week.
Step 2 (25–35 min): Core Diagnostic
- Mixed difficulty set to run S01
- Record time per question for S02
- Tag every error using S03
- Count hints/prompts for S07
Step 3 (10–15 min): Verification Gate
- Closed-book mini-check (S22)
- 2nd form/variation check (S20)
- If fail → no upgrade, return to repair next time.
Step 4 (2 min): Load + Buffer Decision
- If overload appears (S29) → reduce load
- If feedback is slow (S33) → tighten feedback loop
Step 5 (Monthly / every test): Outcome Confirmation
- Track trend (S41) not just single scores.
Trigger → Action Rules (Minimal Pack Edition)
If S01 triggers (collapse under load)
→ Repair fundamentals and reduce difficulty ladder until stable.
If S02 triggers (time stalls)
→ Repair bottleneck skill and Reduce Load (pacing + chunking).
If S03 shows “reading/interpretation” as dominant
→ Repair comprehension/representation before more math drilling.
If S07 shows high hint-dependence
→ Repair with fading scaffolds; treat as P1 until independence rises.
If S20 or S22 fails
→ Verify Upgrade (do not advance Phase).
If S24 triggers
→ Maintain immediately (small refresh beats big rescue).
If S29 triggers
→ Reduce Load now (volume reduction beats collapse later).
If S33 triggers
→ Strengthen Buffers (shorten feedback loop).
If S41 plateaus/regresses
→ Re-check Phase truth (S01/S02/S03/S07) and repair deeper.
The Minimal Weekly Log (Copy/Paste)
Week of: ________
Active Topics (max 5):
- Topic 1: Phase __ | S01 __ | S02 __ | S03 __ | S07 __ | Gate (S20/S22) Pass/Fail
- Topic 2: Phase __ | S01 __ | S02 __ | S03 __ | S07 __ | Gate (S20/S22) Pass/Fail
- Topic 3: Phase __ | S01 __ | S02 __ | S03 __ | S07 __ | Gate (S20/S22) Pass/Fail
Drift (S24): ____________________
Load (S29): _____________________
Feedback latency (S33): __________
Trajectory (S41): _______________
This week’s action: Repair / Reduce Load / Verify Upgrade / Strengthen Buffers / Maintain
One repair target: ______________________
Education OS Sensors — Phase Instrument Panel (P0–P3) (Compressed)
Slug (reserve, optional): education-os-sensors-phase-instrument-panel
(If you’re keeping everything in one master page, just paste this section into it.)
Definition Lock Box (Do Not Edit)
Phase Instrument Panel: The minimum set of sensors that lets you classify P0–P3 truthfully for any topic.
Core truth: A student is not “P2” globally. The student is P0–P3 per topic pocket (Z0), which rolls up to overall readiness.
The 8 Phase Sensors (S01–S08)
S01 — Accuracy Under Load (AUL)
- Measure: compare easy vs exam-grade accuracy
- P0: collapses even on basic load
- P1: works only with heavy scaffolds; collapses under timed load
- P2: stable on normal exam items within scope
- P3: stable under high load + long papers; minimal collapse
S02 — Time-to-Solve Distribution (TSD)
- Measure: time per question; flag stalls
- P0: frequent stalls + random guessing
- P1: can solve but time explodes unless prompted
- P2: predictable timing with occasional slow items
- P3: tight timing, recovers quickly from hard items
S03 — Error Taxonomy Sensor (ETS)
- Measure: label each error type
- P0: errors are foundational (concept/prereq/reading)
- P1: errors are method + scaffolding dependency
- P2: errors are mostly slips/edge cases
- P3: errors are rare; mostly due to extreme novelty or speed
S04 — Retry Elasticity (RE)
- Measure: retest after correction
- P0: repeats same mistake 3+ times
- P1: improves but regresses easily
- P2: fixes quickly and retains
- P3: fixes instantly and generalises
S05 — Transfer & Generalisation (TG)
- Measure: same concept, new framing
- P0: cannot transfer
- P1: transfers only with hints
- P2: transfers within known family
- P3: transfers across unfamiliar contexts
S06 — Explanation Fidelity (EF)
- Measure: student explains the “why”
- P0: cannot explain; guesses steps
- P1: partial explanation; relies on memorised steps
- P2: clear explanation for standard cases
- P3: can teach; explains exceptions and checks
S07 — Independence Ratio (IR)
- Measure: hints needed per problem
- P0: cannot move without step-by-step prompting
- P1: frequent prompts/hints needed
- P2: mostly independent; asks targeted questions
- P3: independent + self-correcting
S08 — Exception Handling (EH)
- Measure: twist/edge-case items
- P0: collapses immediately
- P1: collapses unless heavily scaffolded
- P2: handles some twists with time
- P3: handles twists calmly; builds method on the fly
Phase Classification Rule (Practical)
A topic is:
- P0 if S01 collapses + S09 prerequisites fail OR S07 hint-dependence is extreme
- P1 if correct with scaffolds but fails independence + fails under load
- P2 if stable independent execution in defined scope + passes gate checks
- P3 if stable under load + passes transfer + handles exceptions + can explain/teach
The “No Fake Upgrades” Add-On (Mandatory Pair)
Even for Phase Instrument Panel, always attach:
- S20 Gate Test (GTS)
- S22 Closed-Book Retrieval (CBRS)
If either fails, you do not upgrade Phase.
Micro-Checklist (Copy/Paste)
Topic: ________
- S01 Load accuracy: ____
- S02 Time stalls: ____
- S03 Error type: ____
- S07 Hint dependence: ____
- S20 Gate test: Pass/Fail
- S22 Closed-book: Pass/Fail
Phase now: P0 / P1 / P2 / P3
Action: Repair / Reduce Load / Verify / Buffer / Maintain
Education OS Sensors — Z0 Atomic Skills (Repair Sensors) (Compressed)
Slug (reserve, optional): education-os-sensors-z0-atomic-skills
(If you’re keeping everything in one master page, paste this section into it.)
Definition Lock Box (Do Not Edit)
Z0 (Atomic Skills): The smallest skill units that actually break learning: prerequisites, recall, micro-stability, misconceptions, and representation switching.
Z0 Rule: If Z0 is broken, higher-level practice does not fix it. It only creates fatigue and confusion.
The Z0 Repair Sensor Set (S09–S13)
S09 — Prerequisite Integrity Sensor (PIS)
- Detects: missing prerequisite bricks (fractions, algebra, ratio, vocabulary, inference)
- How to Measure: micro-checklist test (5–10 items)
- Trigger: prerequisite failure blocks downstream work
- Action: Repair (Z0) prerequisites first (stop advanced grinding)
Typical causes: gaps from earlier years, poor consolidation, rushed curriculum, exam-season compression.
S10 — Micro-Drill Stability (MDS)
- Detects: unstable performance on micro-skills
- How to Measure: 10–20 rep drills (same micro-skill)
- Trigger: large variability; “random correctness”
- Action: Repair (Z0) until stable, then climb difficulty ladder
Use: This is how you convert P1-looking skills into P2 reliability.
S11 — Recall Latency (RL)
- Detects: slow retrieval of facts/formulas/definitions
- How to Measure: closed-book timed recall (30–90 seconds)
- Trigger: knows it but can’t retrieve fast enough under exam load
- Action: Maintain/Repair with spaced retrieval bursts
Interpretation: This is a hidden “time tax” that causes late-paper collapse.
S12 — Representation Switching (RS)
- Detects: inability to translate between forms
- How to Measure: word↔equation, diagram↔algebra, sentence↔inference conversions
- Trigger: student succeeds only in one representation
- Action: Repair (Z0) by training multiple representations
Why it matters: exam questions are often representation switches disguised as “hard questions.”
S13 — Misconception Trigger Sensor (MTS)
- Detects: specific misconception patterns (repeatable wrong logic)
- How to Measure: targeted misconception items designed to expose the error
- Trigger: same wrong pattern repeats across papers
- Action: Repair (Z0) with misconception correction protocol
Protocol (short): expose misconception → name it → show counterexample → rebuild correct rule → retest.
The Z0 Repair Routing Rule (Practical)
When a topic fails, do not guess. Route repairs in this order:
- S09 prerequisites (if fail, stop and repair)
- S13 misconception (if present, correct immediately)
- S10 micro-stability (stabilise reps)
- S11 recall latency (speed up retrieval)
- S12 representation switching (unlock translation)
Z0 Repair Block (20–30 minutes Session Template)
Target micro-skill: ____________
- Step 1: Prereq check (S09)
- Step 2: Misconception trigger (S13)
- Step 3: 10–20 reps (S10)
- Step 4: Timed recall burst (S11)
- Step 5: Representation switch item (S12)
- Step 6: Verify (S22 closed-book) + (S20 gate mini)
Z0 Log (Copy/Paste)
Topic: ________
- S09 prereqs: Pass/Fail (which?) ________
- S13 misconception: Yes/No (which?) ________
- S10 stability: Stable/Unstable
- S11 recall: Fast/Slow
- S12 switching: OK/Weak
Action this week: Repair / Maintain
Proof (S22 + S20): Pass/Fail
Education OS Sensors — Z1 Human Factors (Student-in-Role) (Compressed)
Slug (reserve, optional): education-os-sensors-z1-human-factors
(If you’re keeping everything in one master page, paste this section into it.)
Definition Lock Box (Do Not Edit)
Z1 (Student-in-Role): Sensors that detect whether the student’s human operating conditions are breaking learning: attention, anxiety, sleep/energy, motivation, self-correction, and help-seeking quality.
Z1 Rule: Even perfect teaching fails if the student is running in threat mode, overload, or exhaustion.
The Z1 Sensor Set (S14–S19)
S14 — Attention Drift Sensor (ADS)
- Detects: attention drop across session time
- How to Measure: track accuracy trend from minute 0→45
- Trigger: consistent decline after a predictable time threshold
- Action: Reduce Load (shorter blocks + breaks) + tighten session structure
Common fix: 2×25-minute blocks, short reset, then verification.
S15 — Anxiety / Threat Response Sensor (ATR)
- Detects: threat mode hijacking cognition
- How to Measure: student blanks/panics only during tests, not during practice
- Trigger: sudden collapse under evaluation conditions
- Action: Reduce Load + gradual exposure + rebuild safety + smaller gates
Note: Threat mode mimics “concept weakness” but is not fixed by more drilling.
S16 — Sleep / Energy Correlation Sensor (SECS)
- Detects: performance tightly coupled to sleep/energy
- How to Measure: simple sleep log vs accuracy/time stalls
- Trigger: predictable slump linked to sleep debt / late nights
- Action: Reduce Load + schedule hard work in high-energy windows
Rule: If sleep is broken, treat learning as maintenance, not expansion.
S17 — Motivation & Avoidance Sensor (MAS)
- Detects: avoidance loops (stalling, “tomorrow”, missing reps)
- How to Measure: task start delay + homework follow-through patterns
- Trigger: repeated failure to start/finish despite “wanting to do well”
- Action: Strengthen Buffers (smaller tasks + fast feedback + micro-wins)
Key: Reduce activation energy. Make the first 5 minutes easy to start.
S18 — Self-Correction Sensor (SCS)
- Detects: ability to catch own mistakes
- How to Measure: enforce a “check pass” before submission
- Trigger: avoidable errors persist that checks would catch
- Action: Repair the checking habit + standardise the protocol (links to S40)
This is a P2 reliability gate.
S19 — Help-Seeking Quality Sensor (HSQ)
- Detects: whether questions asked are diagnostic and useful
- How to Measure: can student say: “I’m stuck at step 3 because ____”
- Trigger: vague “I don’t know” dominates; cannot point to the failure point
- Action: Repair diagnostics language (teach how to describe stuckness)
Why it matters: good help-seeking shortens feedback loops dramatically.
Z1 Routing Rules (What to Do When Z1 Triggers)
If S14 triggers (attention drift)
→ shorten blocks + structured breaks; stop long chaotic sessions.
If S15 triggers (threat response)
→ reduce difficulty ladder, use small gates, rebuild confidence with proof.
If S16 triggers (sleep coupling)
→ protect sleep, reduce volume, do maintenance not expansion.
If S17 triggers (avoidance)
→ shrink tasks to “startable” size; add immediate feedback.
If S18 triggers (no self-correction)
→ install checking protocol; treat as reliability defect, not intelligence.
If S19 triggers (poor help-seeking)
→ teach “where I’m stuck + why” language; require pinpointing.
Z1 Log (Copy/Paste)
Week of: ________
- S14 attention drift: Yes/No | threshold minute: ____
- S15 threat response: Yes/No | when: ____
- S16 sleep coupling: Yes/No | pattern: ____
- S17 avoidance: Yes/No | pattern: ____
- S18 self-correction: Weak/OK
- S19 help-seeking: Weak/OK
Action: Reduce Load / Strengthen Buffers / Repair
One change this week: _____________________
Master Spine
https://edukatesg.com/civilisation-os/
https://edukatesg.com/what-is-phase-civilisation-os/
https://edukatesg.com/what-is-drift-civilisation-os/
https://edukatesg.com/what-is-repair-rate-civilisation-os/
https://edukatesg.com/what-are-thresholds-civilisation-os/
https://edukatesg.com/what-is-phase-frequency-civilisation-os/
https://edukatesg.com/what-is-phase-frequency-alignment/
https://edukatesg.com/phase-0-failure/
https://edukatesg.com/phase-1-diagnose-and-recover/
https://edukatesg.com/phase-2-distinction-build/
https://edukatesg.com/phase-3-drift-control/
Block B — Phase Gauge Series (Instrumentation)
Phase Gauge Series (Instrumentation)
https://edukatesg.com/phase-gauge
https://edukatesg.com/phase-gauge-trust-density/
https://edukatesg.com/phase-gauge-repair-capacity/
https://edukatesg.com/phase-gauge-buffer-margin/
https://edukatesg.com/phase-gauge-alignment/
https://edukatesg.com/phase-gauge-coordination-load/
https://edukatesg.com/phase-gauge-drift-rate/
https://edukatesg.com/phase-gauge-phase-frequency/
The Full Stack: Core Kernel + Supporting + Meta-Layers
Core Kernel (5-OS Loop + CDI)
- Mind OS Foundation — stabilises individual cognition (attention, judgement, regulation). Degradation cascades upward (unstable minds → poor Education → misaligned Governance).
- Education OS Capability engine (learn → skill → mastery).
- Governance OS Steering engine (rules → incentives → legitimacy).
- Production OS Reality engine (energy → infrastructure → execution).
- Constraint OS Limits (physics → ecology → resources).
Control: Telemetry & Diagnostics (CDI) Drift metrics (buffers, cascades), repair triggers (e.g., low legitimacy → Governance fix).
Supporting Layers (Phase 1 Expansions)
- Medical OS: Bio-repair for Mind/capability.
- Technology & Infrastructure OS: Amplifies all layers.
- Culture & Language OS: Norms, trust, meaning. •
- Security & Stability OS: Threat protection.
- Planetary & Ecological OS: Biosphere constraints.
- https://edukatesg.com/additional-mathematics-os/
- https://edukatesg.com/secondary-math-os/
- https://edukatesg.com/vocabulary-os/
- https://edukatesg.com/what-regeneration-means-in-civilisation-in-simple-terms/
- https://edukatesg.com/the-root-of-civilisation-why-everything-depends-on-regeneration/
Start Here for Lattice Infrastructure Connectors
- https://edukatesg.com/singapore-international-os-level-0/
- https://edukatesg.com/singapore-city-os/
- https://edukatesg.com/singapore-parliament-house-os/
- https://edukatesg.com/smrt-os/
- https://edukatesg.com/singapore-port-containers-os/
- https://edukatesg.com/changi-airport-os/
- https://edukatesg.com/tan-tock-seng-hospital-os-ttsh-os/
- https://edukatesg.com/bukit-timah-os/
- https://edukatesg.com/bukit-timah-schools-os/
- https://edukatesg.com/bukit-timah-tuition-os/
- https://edukatesg.com/family-os-level-0-root-node/
- https://bukittimahtutor.com
- https://edukatesg.com/punggol-os/
- https://edukatesg.com/tuas-industry-hub-os/
- https://edukatesg.com/shenton-way-banking-finance-hub-os/
- https://edukatesg.com/singapore-museum-smu-arts-school-district-os/
- https://edukatesg.com/orchard-road-shopping-district-os/
- https://edukatesg.com/singapore-integrated-sports-hub-national-stadium-os/
Start Here
- https://edukatesg.com/new-york-os-civos/
- https://edukatesg.com/singapore-city-os/
- https://edukatesg.com/beijing-os-civos/
- https://edukatesg.com/the-beijing-singapore-new-york-corridor-as-a-z3-shock-absorption-mechanism-civos/
- Start Here:
- https://edukatesg.com/environment-planetary-os-level-1/
- https://edukatesg.com/international-os-level-1/
- https://edukatesg.com/city-os-level-1/
- https://edukatesg.com/culture-language-os-level-1/
- https://edukatesg.com/governance-os-level-1/
- https://edukatesg.com/healthcare-os-level-1/
- https://edukatesg.com/infrastructure-os-level-1/
- https://edukatesg.com/production-os-level-1/
- https://edukatesg.com/finance-os-level-1/
- https://edukatesg.com/singapore-museum-arts-district-os-level-1/
- https://edukatesg.com/singapores-sports-os-level-1/
- https://edukatesg.com/orchard-road-os-level-1/
- https://edukatesg.com/security-stability-os-level-1/
- https://edukatesg.com/education-os-level-1
- https://edukatesg.com/community-os-level-1/
- https://edukatesg.com/family-os-operating-system-in-civilisation-os/
