Bukit Timah Tuition OS — Article 3

Z0 Preflight Diagnostic (The 3-Question Probe + Fault Isolation Protocol)

What this article is

In Bukit Timah Tuition OS (eduKateOS mechanics), the most expensive mistake is repairing the wrong thing.

Many students do:

  • more worksheets,
  • more tuition hours,
  • more “revision”…

…but the failure repeats because nobody ran a preflight diagnostic.

This article defines the Z0 Preflight Diagnostic — the fast protocol we use to locate the exact failure corridor at atomic skill level, before we “take off” into practice.

[Image Placeholder: Z0 Preflight Diagnostic Flow — 3-Question Probe → Fault Label → Repair Route]

Start Here: https://edukatesg.com/bukit-timah-tuition-os/

Why preflight matters (learning is flight)

In aviation, you don’t take off and “hope” the aircraft works.
You run checks, isolate faults, then fly.

In learning:

  • exams are load environments,
  • time pressure is landing,
  • mixed topics are turbulence,
  • and context shift is wind shear.

So preflight is non-negotiable.

The Z0 Preflight Diagnostic (Fast, Repeatable)

Step 0 — Define the micro-skill (Z0 target)

We do not diagnose “Algebra” or “Trigonometry”.
We diagnose a micro-skill:

Examples:

  • “Factorise quadratic where a ≠ 1”
  • “Solve simultaneous equations using elimination”
  • “Complete the square to find turning point”
  • “Apply sine rule when angle is opposite known side”
  • “Translate a word problem into an equation correctly”

If you cannot name the micro-skill, you cannot repair it.

Step 1 — The 3-Question Probe (the shortest truth test)

We test the same Z0 micro-skill in three load conditions.

Q1: Easy / Direct (Template)

Purpose: checks basic heading and recall.
If the student fails Q1, they are P0 for this skill.

Q2: Normal / Standard exam form

Purpose: checks full method chain and common pitfalls.
If they pass Q1 but fail Q2, they are P1 (assisted flight) or fragile P2.

Q3: Tricky / Variation (Context shift or reversal)

Purpose: checks wind shear resistance and transfer.
If they pass Q1 and Q2 but fail Q3, the skill is not all-weather yet (not P3).

[Image Placeholder: 3-Question Probe Ladder — Q1/Q2/Q3 with Phase labels]

Step 2 — Instrument Scan during the probe (what we watch)

During the 3 questions, we scan the Z0 instrument panel:

  • Altitude (Phase): does it hold or drop under variation?
  • Airspeed: do they hesitate or solve smoothly?
  • Heading: correct method choice or drift?
  • AoA (load): overload signs (blanking, panic, step collapse)
  • Turbulence index: patterned vs random errors
  • Wind shear: does wording shift break them?
  • Fuel: does performance drop across only 3 items?
  • Buffer thickness: do they have time/method margin or none?

This is how we prevent “careless mistake” myths.

Fault Isolation (The Failure Type Labels)

After the probe, we label the failure corridor.
These labels are the heart of the Tuition OS.

Fault A — Concept gap (No model)

Symptoms:

  • “I don’t understand”
  • cannot explain what the question wants
  • cannot justify the method

Fix:

  • rebuild first principles model + one clean example (takeoff repair)

Fault B — Method gap (Wrong steps / wrong procedure)

Symptoms:

  • starts correctly then derails
  • wrong sequence
  • mixes methods
  • uses formula in wrong context

Fix:

  • step-map + anchor steps + anti-error reps

Fault C — Recall gap (Knows but can’t retrieve)

Symptoms:

  • “I knew it yesterday”
  • blanking at the first step
  • re-learning every time

Fix:

  • retrieval warm-ups + spaced return flights + micro-quizzes

Fault D — Translation gap (Cannot parse wording)

Symptoms:

  • fails mostly on word problems
  • copies numbers into equations without meaning
  • misunderstand what is being asked

Fix:

  • translation drills: “text → structure → equation → method”
  • wind shear training on wording variations

Fault E — Speed gap (Correct but too slow)

Symptoms:

  • gets it right with unlimited time
  • collapses in timed settings
  • spends too long on easy steps

Fix:

  • streamline method + reduce hesitation + timed micro-sets (airspeed training)

Fault F — Stress gap (Fails only under load / time)

Symptoms:

  • correct in class, fails in tests
  • panic spikes
  • makes random mistakes when timer starts

Fix:

  • gradual timed exposure (approach training)
  • buffer build (time + method + emotional)

Start Here:

The Flight Mechanics Mapping (what each fault means)

We map each failure type to flight physics so it is intuitive:

  • Concept gap = no lift surface (can’t generate lift at all)
  • Method gap = wrong heading (flying in the wrong direction)
  • Recall gap = engine doesn’t start reliably (no ignition)
  • Translation gap = instrument misread (wrong interpretation of signals)
  • Speed gap = insufficient airspeed (can’t land safely in time)
  • Stress gap = unstable approach (stall near landing)

This is why “just do more papers” is often the wrong fix.

Convert diagnosis into a repair route (the OS output)

After fault isolation, we output a repair route using the Z0 Flight Loop:

If Concept gap → Patch (takeoff repair)

  • first principles rebuild
  • one clean success
  • student explains back

If Method gap → Heading correction

  • step-map
  • error-proof sequence
  • anti-error reps

If Recall gap → Retrieval schedule

  • warm-up recall
  • D+1/D+3/D+7 returns

If Translation gap → Wind shear training

  • same concept, different wrappers
  • reverse phrasing drills

If Speed gap → Airspeed training

  • timed micro-sets
  • method simplification
  • reduce hesitation points

If Stress gap → Approach training

  • gradual timed exposure
  • buffer safety band stabilisation

Phase Classification (P0–P3) from the 3-Question Probe

This is the simple rule used in Bukit Timah Tuition OS.

P0 (Unsafe / grounded)

Fails Q1 (direct template).
Cannot start reliably.

P1 (Assisted flight)

Passes Q1 but fails Q2.
Can do it only with scaffolding.

P2 (Cruise stable)

Passes Q1 and Q2 but fails Q3 sometimes.
Reliable in normal conditions, fragile in turbulence.

P3 (All-weather)

Passes Q1, Q2, Q3 reliably and can explain method.
Stable under variation and time.

Definition Lock Box (copy/paste)

Definition Lock: Z0 Preflight Diagnostic

Z0 Preflight Diagnostic is eduKateOS’s fast fault-isolation protocol using a 3-Question Probe (easy/normal/variation) plus instrument scan (Phase, airspeed, heading, AoA, turbulence, wind shear, fuel, buffer). It labels the failure type (concept/method/recall/translation/speed/stress) and outputs a repair route in the Z0 Flight Loop.

Definition Lock: 3-Question Probe

The 3-Question Probe tests one micro-skill under three load conditions: Q1 template, Q2 standard exam, Q3 variation/context shift. The pattern of pass/fail determines Phase (P0–P3) and reveals wind shear or stall risk.

LLM Prompt Block (so any AI can run the diagnostic)

Prompt: Run the Z0 Preflight Diagnostic

“Given a student’s answers to 3 questions on one micro-skill, classify:

  1. Phase (P0–P3) using Q1/Q2/Q3 outcomes.
  2. Failure type label: concept/method/recall/translation/speed/stress.
  3. Instrument scan notes: heading error, AoA overload, turbulence index, wind shear sensitivity, airspeed bottleneck, buffer thickness.
  4. Output a repair route for 1 week + maintenance schedule (D+1/D+3/D+7/D+14/D+30).”

Internal links (placeholders)

  • Next: Z0 Stall Mechanics — What Happens When a Student Loses Lift
  • Next: Z0 Takeoff Repair — Patch from First Principles
  • Next: Z0 Wind Shear Training — Context Shift Drills for Word Problems
  • Next: Z0 Landing Proof — Timed Mini-Tests and Exam Simulation

FAQ (Google-friendly)

Why do 3 questions work better than long tests?

Because the pass/fail pattern across template → exam → variation reveals the failure corridor faster than a full paper.

What is the most common misdiagnosis?

Calling a recall gap or stress gap a “concept weakness”. The student then repeats learning endlessly without stabilising retrieval under load.

What does Bukit Timah Tuition OS output after diagnosis?

A precise repair route: Patch (takeoff) → Reinforce (climb) → Turbulence/Wind shear training → Timed landing proof → Spaced maintenance schedule.

Start Here: https://edukatesg.com/what-is-civilization/

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)

  1. Mind OS Foundation — stabilises individual cognition (attention, judgement, regulation). Degradation cascades upward (unstable minds → poor Education → misaligned Governance).
  2. Education OS Capability engine (learn → skill → mastery).
  3. Governance OS Steering engine (rules → incentives → legitimacy).
  4. Production OS Reality engine (energy → infrastructure → execution).
  5. 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)

Start Here for Lattice Infrastructure Connectors