eduKate Singapore

VIEW THIS AS

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

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

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

Next useful routeCanonical hubHELP

Education Repair Router OS

Education OS V1.1 — decision tree routing to the correct intervention (retention vs transfer vs execution vs control) + a 7-day recovery plan template

Definition Lock

A repair router is a deterministic decision tree that selects the correct intervention module.
Most education fails because the wrong repair is applied to the right symptom.

Master Lock

Education prevents self-decay.
Repair works only when you route the learner to the correct module fast.

The four failure classes (the router categories)

All learning failure falls into one dominant category:

  1. Retention failure — “I knew it, but I forgot.”
  2. Transfer failure — “I can do it in practice, not in exam / new context.”
  3. Execution failure — “Careless / messy / wrong steps under speed.”
  4. Control failure — “Panic, time collapse, cannot recover mid-task.”

Lock

Do not treat control failure like knowledge failure. More worksheets can worsen it.

Router Step 1 — Untimed baseline test (the gate)

Give 3 items (easy / medium / medium) untimed.

Outcome A — cannot do untimed

→ Not a control issue. Likely retention or Z0 gap.

Outcome B — can do untimed, but fails timed

→ Likely execution or control.

Outcome C — can do untimed and timed on standard format, but fails when mixed/varied

→ Likely transfer.

Router Step 2 — Variation test (transfer gate)

Give 5 items:

  • same topic, different surfaces
  • 2 “tempt wrong method” questions
  • no topic labels

Outcome A — chooses wrong method repeatedly

→ Transfer failure (method choice).

Outcome B — chooses correct method but makes slips

→ Execution failure.

Outcome C — freezes / gives up when unfamiliar

→ Control failure (triggered by uncertainty).

Router Step 3 — Error-pattern check (execution gate)

Look for:

  • sign errors
  • skipping steps
  • miscopying
  • misreading constraints
  • missing units
  • vague writing
  • irrelevant evidence
  • contradictory arguments

If errors are repetitive and identical, it’s a Z0 micro-gap.
If errors appear only under speed, it’s execution.

Lock

Repeated error across questions = missing micro-skill, not carelessness.

Router Step 4 — Stress signature (control gate)

Control failure has a signature:

  • speed spikes early then crashes
  • stuck too long on one item
  • blanking out after one hard question
  • avoidance statements (“I don’t know”, immediately)
  • emotional escalation or shutdown

If these appear, route to Exam Flight Control OS first, not more content.

The Router (Decision Tree)

Copy this block into any repair page.

Decision Tree

  1. Can the learner do it untimed?
  • No → Z0 localisation + Retention OS
  • Yes → go to (2)
  1. Can the learner do it timed in standard format?
  • No → Execution OS + Flight Control OS
  • Yes → go to (3)
  1. Can the learner do it when mixed and varied (no topic labels)?
  • No → Transfer Training OS
  • Yes → go to (4)
  1. Is performance still inconsistent?
  • Yes → Control or maintenance problem (Retention schedule missing)
  • No → stable P2

Module routing table (symptom → module)

  • “Forgot after a week” → Retention & Spacing OS
  • “Homework ok, exam fail” → Transfer Training OS + Exam Flight Control OS
  • “Careless” → Execution discipline + checking protocol
  • “Blank out / panic” → Exam Flight Control OS (first)
  • “Same wrong step always” → Z0 Gap Localisation OS
  • “Writes a lot but low marks” → English evidence discipline + editing control
  • “Science keywords but cannot explain” → Model rebuild + causal chain training
  • “Humanities opinion dumping” → Argument frame + evidence linkage + context control

7-Day Recovery Plan Template (copy-paste)

Use this after routing. Keep it narrow. One failure class per week.

Day 0 (today): Diagnose + truncate

  • Identify the failure class (retention/transfer/execution/control)
  • Remove overload (short tasks only)
  • Pick ONE micro-skill to repair

Day 1–2: Stabilise (untimed)

  • 10–15 min daily
  • focus only on micro-skill + correct first wrong step
  • end with 1 independent reproduction

Day 3–4: Add spacing + small variation

  • recall from memory first
  • 3–5 short items
  • 2 slight variations
  • correct immediately

Day 5: Mixed mini-set (transfer probe)

  • 6–10 questions mixed
  • must name method/structure before solving/writing
  • no timing unless stability is high

Day 6: Light timing or control drill (depending on route)

  • if execution/control route: do a short timed section
  • practice skip-and-return
  • practice landing check routine

Day 7: Audit + stitch plan

  • list: what improved? what still breaks?
  • choose next week’s single target
  • stitch back to syllabus speed gradually

Lock

A repair plan that tries to fix everything fixes nothing. One week = one dominant failure class.

Subject-specific “7-day focus” examples

Math

  • focus: algebra manipulation stability OR method choice in mixed sets

English

  • focus: claim–evidence–explanation OR inference proof discipline

Science

  • focus: one model + “what changes if…” drills

Humanities

  • focus: argument frame + evidence linkage sentences

AI as a repair assistant (safe use)

AI can help only if it:

  • classifies the failure type
  • localises first wrong step
  • generates spaced quizzes and variation sets
  • forces the learner to attempt first

Safe prompt (Router)

“Given this work and these mistakes, classify the failure as retention/transfer/execution/control and explain why. Then give a 7-day plan focusing only on that failure type. Do not provide full solutions.”

Summary Lock

Education Repair Router OS prevents wasted effort:

Diagnose the dominant failure class → route to the correct module → run a narrow 7-day plan → audit and stitch.

This is how repair becomes systematic instead of emotional.

Recommended Internal Links (Spine)

Start Here: