Education OS Sensors Directory is the instrument panel for Education OS.

Education OS converts time into capability.
Sensors ensure we can measure whether that conversion is happening, how fast it is happening, and whether it is stable.

Without sensors, education becomes:

workload without direction
tuition without trajectory
effort without compounding growth

Sensors prevent drift by turning education into measurable slopes.

Education OS Sensors are the learning execution signals that tell you if the student is truly improving or only “doing work”. These sensors sit inside Education OS (daily training loops), and they are different from Planet OS sensors (global routing).

Planet OS sensors answer: Where is the problem?
Education OS sensors answer: Is the training loop working?

What a Sensor Is (Education OS Standard)

Every Education OS sensor must have:

What it measures (one variable only)
How to read it (improvement vs illusion)
Thresholds (low / stable / strong / danger)
Repair actions (what to do if weak)

If it does not do these four things, it is not a sensor.

Core Education OS Sensors (Canonical Set)

Education OS is healthiest when these four sensors rise over time:

1) Comprehension Slope Sensor

Measures whether understanding improves across weeks and months (not just one test).

https://edukatesg.com/education-sensor-comprehension

2) Writing Clarity Index

Measures whether writing becomes clearer, more coherent, and more precise (not just “more advanced vocabulary”).

https://edukatesg.com/education-sensor-clarity

3) Learning Velocity Sensor

Measures time-to-master per skill. If velocity improves, the learner is compounding.

https://edukatesg.com/education-sensor-velocity

4) Transfer Ability Sensor

Measures whether skills work in unfamiliar contexts. Transfer is the proof of real learning.

https://edukatesg.com/education-sensor-transfer

5) The Full Suite Instrument Panel (P0–P3, Z0–Z3)

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).

https://edukatesg.com/education-os-sensors-edukateos-full-suite/

How These Sensors Fit the Education OS Pipeline

Education OS converts:

input → understanding → memory → retrieval → application → feedback → repair → trajectory

These sensors correspond to pipeline health:

Comprehension Slope = understanding quality over time
Writing Clarity = application quality in language output
Learning Velocity = efficiency of the learning engine
Transfer Ability = generalisation (real capability, not memorisation)

If these four rise, Education OS is running.

The Rule of Stability (The Education OS “No Drift” Rule)

Education OS is stable when:

repair rate ≥ error rate

If errors accumulate faster than repair, the learner becomes noisy and unstable.

So these sensors must be tracked alongside repair actions.

Who Education OS Sensors Are For

Education OS Sensors are for:

Parents

To see progress without guessing, nagging, or panic.

Students

To understand what actually improves performance, and to build confidence through real trends.

Tutors and Teachers

To detect failure points early and apply targeted fixes quickly.

What Education OS Sensors Measure

Education OS sensors measure four main dimensions:

Understanding (concept clarity)
Execution (ability to do under constraints)
Correction quality (upgrade rate)
Stability (retention over time)

If you only measure marks, you miss the true engine.

Education OS Sensor Packs

Education OS sensors are grouped into packs so parents can start small.

Pack 1: Core Loop Sensors (Starter Pack)

These five sensors are enough for most families.

1) Output Accuracy Trend

Track weekly accuracy across similar difficulty.

Signal:

improving trend = learning is installing
flat trend = loop is incomplete
falling trend = drift or overload

2) Time-to-Complete Trend

Track time for similar tasks.

Signal:

time decreases while accuracy holds = mastery
time decreases but accuracy drops = rushing
time stays high with low accuracy = missing method or foundations

3) Error Pattern Stability

Track the top 3 repeated error types.

Signal:

error types change (from basic to advanced) = progress
same error repeats for weeks = missing correction loop

4) Correction Quality

Track whether mistakes are properly corrected.

A correct correction is:

wrong → explain why → rewrite correctly → store pattern → re-test later

Signal:

high correction quality = rapid improvement
low correction quality = repeated failure, even with tuition

5) Spaced Retention

Re-test weak points after a gap.

Signal:

improves after spacing = learning is sticking
collapses after spacing = shallow learning (familiarity, not mastery)

This pack alone prevents most grade drift.

Pack 2: Understanding Sensors (Concept Clarity)

Use this when the child says “I don’t get it”.

1) Explain-Back Sensor

Can the student explain the concept in simple words?

Signal:

if they can’t explain, they don’t truly understand

2) Worked Example Transfer

Can the student solve a similar question without copying?

Signal:

if they only can copy, learning is not installed

3) Misconception Detector

Does the student make the same wrong assumption repeatedly?

Signal:

stable misconception = needs targeted teaching, not more practice

Pack 3: Execution Sensors (Exam Readiness)

Use this when exams are near or performance is unstable.

1) Time Pressure Stability

Does performance collapse under timed conditions?

Signal:

collapse = practice is not exam-compatible yet

2) First-Attempt Accuracy

How often is the first attempt correct?

Signal:

low first-attempt accuracy = weak method selection or weak foundations

3) Careless Mistake Cluster

Are careless mistakes concentrated in one stage?

Examples:

copying numbers
sign errors
skipping keywords
missing units
rushing endings

Signal:

clusters are fixable with method + checking systems

Pack 4: Consistency Sensors (Training Reality)

Use this when parents say “my child studies a lot” but results don’t match.

1) Session Completion Rate

How many planned sessions were actually completed?

2) Focus Quality

Was the session focused or distracted?

3) Avoidance Pattern

Does the student always skip the hardest question types?

Signal:

avoidance is a major hidden cause of plateau

Pack 5: Learning Stability Sensors (Prevent Drift)

Use this when the child’s grades swing.

1) Week-to-Week Stability

Does performance remain stable over multiple weeks?

2) Topic Decay

Do older topics collapse when new topics begin?

Signal:

decay means spacing is missing; fix spacing, not volume

3) Memory Durability

Can the student still do a skill after a longer gap?

Signal:

durable memory = true mastery
fragile memory = cramming system

The Parent “Sensor Interpretation Rules”

Sensors work only if parents interpret them correctly:

Never judge a child by one sensor reading
Always watch trends over time
Never increase workload if correction quality is low
If the same error repeats, stop and fix the loop
If performance collapses under time, train execution not content
If nothing moves after 7–10 sessions, route to ULD diagnostics

This prevents the biggest trap: pushing harder when the system needs diagnosis.

When Education OS Sensors Tell You To Switch Layers

Education OS Sensors show you when to route elsewhere:

Route to Vocabulary OS if

comprehension errors are caused by word meaning gaps
writing is weak because vocabulary is passive
the student cannot decode questions properly

Route to ULD System if

effort is high but progress is flat
errors persist across many topics
the student is stuck despite consistent loops

Education OS sensors are the early warning system.

Links to the Substrate and Interfaces

Education OS depends on Vocabulary OS:
https://edukatesg.com/vocabulary-os/

Interface: Vocabulary OS → Education OS
https://edukatesg.com/interface-vocab-education/

Interface: Education OS → Civilisation OS
https://edukatesg.com/interface-education-civilisation/

Recommended Build Order (So It Becomes Operational Fast)

Publish this directory page (you are here).
Publish the four sensor pages in this order:

comprehension → clarity → velocity → transfer

Link each sensor to repair actions and measurement cadence.
Then connect the education sensors into Civilisation OS sensor pack (CDI and repair rate).

Yes — WordPress cut-and-paste is totally possible. Don’t use JSON. Use plain-text “Key: Value” blocks that Grok can still parse.

Below is a complete WordPress-ready section you can paste as-is.

eduKateOS Run Mode

Definition Lock Box (Do Not Edit)

eduKateOS Run Mode: A repeatable weekly input → output loop that lets an AI (Grok) classify Phase (P0–P3), detect drift, route Z0 repairs, enforce verification gates, and schedule maintenance.

Allowed Actions (only 5):

REPAIR_Z0
REDUCE_LOAD
VERIFY_UPGRADE
STRENGTHEN_BUFFERS
MAINTAIN

Minimal Runnable Sensor Pack (10):
S01, S02, S03, S07, S20, S22, S24, S29, S33, S41

Outputs required every run:

Topic Phase Map
Bottleneck Ranked List (Z0-first)
Next 7 Days Plan
Verification Gates (S20 + S22)
Maintenance Schedule
Load Adjustments
Buffer Adjustments

Step 1 — Weekly Input Template (Fill This In)

STUDENT LEVEL:
DAYS TO NEXT EXAM / TEST WINDOW:
WEEKLY HOURS AVAILABLE:
NUMBER OF SCHOOL TESTS THIS WEEK:
AVERAGE SLEEP (LAST 7 DAYS, HOURS): __

TOPIC BLOCK (Copy this block 3–8 times)

TOPIC NAME: __________

S01 Accuracy Under Load (AUL)
Easy accuracy (%):
Exam-grade accuracy (%):

S02 Time-to-Solve Distribution (TSD)
Median time per question (seconds):
Stall items count (very slow questions):

S03 Error Taxonomy (ETS)
Dominant error type (choose one): Concept / Method / Algebra Slip / Reading / Memory / Attention / Exam Technique
Optional error counts: Concept _ / Method _ / Algebra _ / Reading _ / Memory _ / Attention _ / ExamTech __

S07 Independence Ratio (IR)
Hints needed per 10 questions: __

S20 Gate Test (GTS)
Forms passed:
Forms attempted:
Notes (what failed): __________

S22 Closed-Book Retrieval (CBRS)
Closed-book accuracy (%): __

S24 Micro-Regression (MRS)
Weekly micro-check pass? Yes / No
If No: what broke? __________

S29 Cognitive Load (CLS)
Overload present? Yes / No
Signs (tick any): freezing / messy work / skipped steps / panic / time collapse

S33 Feedback Latency (TFLS)
Days from mistake to correction: __

S41 Score Trajectory (STS)
Trend (choose one): Improving / Flat / Declining
Evidence (recent scores): __________

Step 2 — The Run Prompt (Copy/Paste to Grok)

Paste your filled Weekly Input Template above, then paste this:

PROMPT START
You are eduKateOS Run Mode.

Use ONLY these actions: REPAIR_Z0, REDUCE_LOAD, VERIFY_UPGRADE, STRENGTHEN_BUFFERS, MAINTAIN.
Do NOT invent extra actions.

From the Weekly Input Template:

Output TOPIC PHASE MAP: assign P0/P1/P2/P3 per topic with confidence (High/Med/Low).
Output BOTTLENECK RANKED LIST (Z0-first): the top 3–7 causes holding the student back.
Output NEXT 7 DAYS PLAN: daily 10–15 min tasks + 2 longer sessions; focus on ONE main Z0 repair per topic.
Output VERIFICATION GATES: S20 + S22 pass rules (2–3 varied forms + closed-book).
Output MAINTENANCE SCHEDULE: weekly micro-check + refresh intervals for stable topics.
If any topic has S29 Overload = Yes OR deadlines are near, output LOAD ADJUSTMENTS (reduce scope/volume, protect sleep).
If S33 is high OR repairs are not catching up, output BUFFER ADJUSTMENTS (shorten feedback loop, increase repair throughput).

Return results using EXACT headings below (plain text):

TOPIC PHASE MAP:
BOTTLENECK RANKED LIST:
NEXT 7 DAYS PLAN:
VERIFICATION GATES:
MAINTENANCE SCHEDULE:
LOAD ADJUSTMENTS:
BUFFER ADJUSTMENTS:
PROMPT END

Optional (Recommended) — Pass/Fail Threshold Lines (So Grok is Consistent)

Gate pass rule (S20): A topic passes only if Forms passed ≥ 2 out of 2–3 varied forms.
Closed-book pass rule (S22): Closed-book accuracy must be ≥ 70% for P2, ≥ 85% for P3.
Load collapse trigger (S01): If Exam-grade accuracy is ≥ 25% lower than Easy accuracy, treat as “collapse under load.”
Overload trigger (S29): If overload = Yes, action must include REDUCE_LOAD.

Education OS Sensors Safety Disclaimer

Education OS Sensors must be administered properly. For younger learners, use only the starter pack and keep it light. Sensors are not for punishment. If parents over-test, over-measure, or interpret trends harshly, the child can develop anxiety that reduces performance and distorts the sensor signals.

The purpose of sensors is calm clarity and early correction.

Next Page to Publish

Comprehension Slope Sensor
https://edukatesg.com/education-sensor-comprehension/

What a Sensor Is (Education OS Standard)

Core Education OS Sensors (Canonical Set)

1) Comprehension Slope Sensor

2) Writing Clarity Index

3) Learning Velocity Sensor

4) Transfer Ability Sensor

5) The Full Suite Instrument Panel (P0–P3, Z0–Z3)

How These Sensors Fit the Education OS Pipeline

The Rule of Stability (The Education OS “No Drift” Rule)

Who Education OS Sensors Are For

Parents

Students

Tutors and Teachers

What Education OS Sensors Measure

Education OS Sensor Packs

Pack 1: Core Loop Sensors (Starter Pack)

1) Output Accuracy Trend

2) Time-to-Complete Trend

3) Error Pattern Stability

4) Correction Quality

5) Spaced Retention

Pack 2: Understanding Sensors (Concept Clarity)

1) Explain-Back Sensor

2) Worked Example Transfer

3) Misconception Detector

Pack 3: Execution Sensors (Exam Readiness)

1) Time Pressure Stability

2) First-Attempt Accuracy

3) Careless Mistake Cluster

Pack 4: Consistency Sensors (Training Reality)

1) Session Completion Rate

2) Focus Quality

3) Avoidance Pattern

Pack 5: Learning Stability Sensors (Prevent Drift)

1) Week-to-Week Stability

2) Topic Decay

3) Memory Durability

The Parent “Sensor Interpretation Rules”

When Education OS Sensors Tell You To Switch Layers

Route to Vocabulary OS if

Route to ULD System if

Links to the Substrate and Interfaces

Education OS Interface

Planet OS (Top Layer)

Vocabulary OS

ULD System

Recommended Build Order (So It Becomes Operational Fast)

eduKateOS Run Mode

Definition Lock Box (Do Not Edit)

Step 1 — Weekly Input Template (Fill This In)

TOPIC BLOCK (Copy this block 3–8 times)

Step 2 — The Run Prompt (Copy/Paste to Grok)

Optional (Recommended) — Pass/Fail Threshold Lines (So Grok is Consistent)

Education OS Sensors Safety Disclaimer

Next Page to Publish

Share this:

Like this: