ULD Diagnostics is what happens after a probe shows you there is a problem.
A probe tells you where to look. Diagnostics tells you what exactly is broken.
In eduKate OS, “weak in math” is not a diagnosis. “Needs to read more” is not a diagnosis. “Careless” is not a diagnosis. Those are labels that create more practice and more frustration.
ULD Diagnostics is a disciplined process for locating the exact failure node so the repair is small, targeted, and effective.
The One-Sentence Definition
Diagnostics is the process of identifying the exact failure mode and root cause behind performance loss using high-definition evidence (time, steps, error patterns, stability), so recovery is precise and measurable.
Why Families Need Diagnostics
Without diagnostics, families do:
- random practice (high effort, low results)
- emotional cycles (scolding → resistance → shutdown)
- endless switching (books, tutors, schedules)
- false stories (“my child just can’t do it”)
Diagnostics replaces stories with evidence.
What Diagnostics Produces (A Real Output)
A diagnostic output should be specific enough to repair.
Examples of real diagnostic outputs:
- “Fails at converting mixed numbers to improper fractions under time pressure”
- “Expands brackets correctly but loses signs when subtracting expressions”
- “Can infer when options are direct, fails when inference requires linking 2 clues”
- “Vocabulary retrieval is weak; cannot access precise verbs under writing load”
- “Under stress, attention narrows and student stops checking units”
This is why we call it high-definition.
The ULD Diagnostic Stack (From Symptom to Root Cause)
Level 1 — Symptom (What you see)
Wrong answers, slow speed, avoidance, inconsistent performance.
Level 2 — Failure Mode (How it fails)
Misread, method loss, step skipping, weak retrieval, poor transfer, careless under load.
Level 3 — Root Cause (Why it fails)
Examples:
- missing prerequisite node
- overloaded working memory
- weak retrieval strength
- unstable attention / threat response
- poor encoding (learnt once, never consolidated)
- environment/sleep creating high drift rate
Where Diagnostics Sits in the Phase System
Diagnostics is the heart of Phase 1:
https://edukatesg.com/phase-1-diagnose-and-recover
But it is also used in:
- Phase 0 (gentle diagnostics to stabilise without overwhelming)
- Phase 3 (diagnostics when drift sensors detect early degradation)
How to Run Parent-Friendly Diagnostics (Simple Method)
Step 1 — Pick one failed question
Do not diagnose from an entire paper. Start small.
Step 2 — Reconstruct the steps
Ask: where exactly did it go wrong?
- reading the question?
- choosing the method?
- executing steps?
- checking?
Step 3 — Classify the failure mode
Pick ONE dominant failure mode.
Step 4 — Ask the root-cause question
“What would make this failure mode happen repeatedly?”
Step 5 — Confirm with a second micro-probe
If it repeats, your diagnosis is likely correct.
Diagnostics and ULD (Why This Is Different From Normal “Tuition”)
Normal practice assumes the student is fine and just needs more exposure.
ULD Diagnostics assumes:
- there is a broken node
- load and drift amplify the problem
- repairing the node changes everything
- verification is mandatory
This is how Phase 0 becomes Phase 1 safely.
Lock-In Terms (Use These Words Only)
Diagnostics
High-definition identification of the exact failure mode and root cause.
Failure Mode
The observable way performance breaks (misread, method loss, weak retrieval, etc.).
Root Cause
The underlying reason the failure mode keeps repeating.
Diagnostic Output
A specific statement that is repairable, testable, and verifiable.
Disclaimer (High-Precision Use)
Mind OS and ULD-style diagnostics are high-precision training tools intended for specific use cases under clear rules, safeguards, and responsible supervision. Misuse, over-interpretation, or untrained self-administration can lead to incorrect conclusions and unnecessary harm. Use only with appropriate consent, privacy safeguards, and within applicable rules and regulations.