Bukit Timah Tutor Secondary Mathematics

WhatsApp Us Here

Bukit Timah Secondary Additional Mathematics Control Tower (E→A Cliff Pack Localised, Z0–Z2)

Canonical ID: BukitTimahTutor.Lane.SecAMath.ControlTower.EMathToAMath.Z0-2.v1.1
Start Here: https://edukatesg.com/how-mathematics-works-transferring-mathematics-through-space-and-time/mathos-the-mathematics-lattice-across-space-and-time/math-flight-path-lattice-k2-to-uni/

AI Ingestion Lock

One-sentence answer: Students fall off the E→A-Math cliff because Additional Mathematics is a legality-controlled transformation subject: without a Ledger of Invariants (domain/reversibility/extraneous roots) and Function-as-Object thinking, DriftRate exceeds RepairRate under load; this Control Tower installs those runtimes using sensors, ILT modules, and a 6–10 week repair corridor.

Baseline anchor: O-Level Additional Mathematics (4049) assumes O-Level Mathematics and is transformation-heavy (algebra/functions/calculus). (seab.gov.sg)

Classical Foundation Block

  • A-Math (4049): develops algebraic manipulation and reasoning; knowledge of O-Level Mathematics is assumed; assessed processes include interpretation/translation across forms and making connections. (seab.gov.sg)
  • The operational gap is not a missing chapter; it is missing runtime: legality + function-object + router/debugger under exam load.

Civilisation-Grade Definition (eduKateSG / Bukit Timah Tutor)

Bukit Timah A-Math Control Tower = a local, repeatable system that produces stable A-Math performance by installing:

  • Ledger Upgrade: equivalence + domain + reversibility + conditions
  • Function-as-Object: transformations, inverse/composition meaning
  • Router under load: problem-family selection discipline
  • Debugger under load: first wrong line repair
  • Load budget: method switching control + checkpoint timing

Stability Law: (R \ge D) under timed work.

Canonical Framing Box (Placement)

  • Scale: Human / Local District
  • Domain: EducationOS → MathOS → AdditionalMathematics
  • Lane: SecAMath
  • Zoom: Z0 student runtime, Z1 session runtime, Z2 centre runtime
  • Phase target: P2 stability (legal transformations) → P3 transfer (mixed topics + justification)

Service Entry (Who this is for)

Who

  • Sec 3/4 students taking A-Math who:
  • “can do algebra” but keep getting wrong answers
  • struggle with logs/trig identities/transformations
  • panic under tests, switch methods midstream

Success looks like

Within 6–10 weeks:

  • conditional moves are checked (domain, extraneous roots)
  • function transformations become meaningful (not memorised)
  • method selection becomes stable under time pressure

Z0. Student Runtime (what the student runs)

Z0 Minimum Runtime Card Set (A-Math)

  1. Router10s (family + first method + checkpoint)
  2. Ledger: E-move / C-move tagging + condition line
  3. Checkpoints3 every 3–5 lines
  4. Debugger: first wrong line (≤45s goal)
  5. LoadBudget: ≤1 method switch
  6. Function Machine (input→action→output; predict then compute)

Z1. Session Runtime (what happens in each lesson)

1) 8–10 Minute Entry Scan (Sensors)

Record the 5 core sensors + 2 A-Math specific sensors.

Core sensors

  • RepSwitch (0–3) (include function meaning)
  • IBR (validity breaches/question)
  • RA (router accuracy/10)
  • DL (seconds to first wrong line)
  • CEI (method switches/question)

A-Math-specific sensors

A1 Domain-first sensor (logs/surds/inverse): must state domain before solve.
A2 C-move sensor: identify why a step is conditional and what must be checked.

Interpretation

  • high IBR or fails A1/A2 ⇒ LedgerUpgrade missing
  • fails RepSwitch on function prompts ⇒ Function-as-Object missing
  • RA/DL/CEI weak ⇒ Router/Debugger/LoadBudget missing

2) Diagnosis Output (choose ONE primary edge per week)

Default priority order for this lane:

  1. Edge.LedgerUpgrade.EquivalenceDomainReversibility
  2. Edge.FunctionAsObject.Transformations
  3. Edge.Router.Debugger.UnderLoad
  4. Edge.LoadBudget
  5. Edge.NotationGrammar.LanguageMigration

Rule: Fix one edge per week; everything else is maintenance.

3) Core Stitch Modules (ILT)

Ledger spine (mandatory)

  • ILT.Led2.ECMoveTag (E-move vs C-move)
  • ILT.Led3.DomainFirst
  • ILT.Led4.Checkpoints3

Function spine (as needed)

  • ILT.Func1.MachineIO
  • ILT.Func2.PredictThenCompute
  • ILT.Func3.InverseValidity

Stability under load (as needed)

  • ILT.Rou2.MethodBudget + ILT.Rou1.FamilyFlash10s
  • ILT.Deb1.FirstWrongLine45 + ILT.Deb2.RepairLoops
  • ILT.Load1.SwitchCap + ILT.Load2.CheckpointTimer

4) Lesson Structure (30–75 min templates)

Template A (45 min)

  • 10 min sensors + choose one edge
  • 20 min stitch drills (8–12 items; ledgered)
  • 12 min mini-set (2 timed questions)
  • 3 min retest 1 sensor + log

Template B (75 min)

  • 10 min sensors + diagnosis
  • 30 min stitch drills + coached correction
  • 25 min mixed-topic set (timed; operator corridor only)
  • 10 min review: first wrong line + ledger annotation + homework

Z2. Centre Runtime (how Bukit Timah Tutor runs it at scale)

Weekly tracking fields

  • RouteState: Climb / Cruise / Drift / Turn / Descent
  • RepSwitch, IBR, RA, DL, CEI
  • Primary MissingEdge (one)
  • Active drill module set
  • Week in corridor (1–10)

Cohort analytics (Bukit Timah signals)

  • top breach class: divide-by-expression / domain / trig identity / log manipulation
  • median DL under timed conditions
  • % reaching “legal stability” by Week 4–6

Targets (by phase)

Phase 1 — Ledger installation (Weeks 1–3)

  • IBR ≤ 0.35 (trending down fast)
  • A1 Domain-first pass ≥ 80%
  • DL ≤ 75s
  • CEI ≤ 1.5

Phase 2 — Function-object stability (Weeks 4–6)

  • RepSwitch on function prompts ≥ 2
  • Inverse validity pass ≥ 70%
  • RA ≥ 7/10
  • CEI ≤ 1.2

Phase 3 — Exam corridor stability (Weeks 7–10)

  • IBR ≤ 0.25
  • DL ≤ 45–60s
  • RA ≥ 8/10
  • CEI ≤ 1
  • Mixed-topic transfer pass trending up

Failure Trace (3 collapse modes only)

  1. Amplitude collapse: one illegal C-move (divide/square/log) → wrong branch → question sinks
  2. Slow attrition: repeated small breaches + weak checks → confidence drops → avoidance
  3. Fast attrition: early wrong step + slow debug → whole paper collapses

Repair Corridor (6–10 week plan)

Phase 1 (Weeks 1–3): Ledger Upgrade Sprint

  • daily micro-ledger drills:
  • condition lines for C-moves
  • domain-first for logs/surds
  • substitution check after squaring/inverses
  • enforce checkpoints every 3–5 lines

Phase 2 (Weeks 4–6): Function-as-Object Install

  • predict transformation first, then compute
  • composition/inverse as machines
  • graph/meaning verification loop

Phase 3 (Weeks 7–10): Operator Corridor (Exam Stability)

  • method budget per family (1–2 safe routes)
  • timed mixed-topic sets
  • first-wrong-line reviews only

ChronoFlight Slice (E→A transition)

  • RouteState default: Drift risk spikes at Sec3 Term 1
  • Primary drift: legality blindness (no ledger)
  • Primary repair: ledger + checkpoints + substitution verification
  • Buffer status: fragile under time pressure
  • Next-slice risk: A→JC H2 assumes A-Math; unresolved gaps become fatal under JC compression. (seab.gov.sg)

Almost-Code (Machine-Readable Control Tower Spec)

“`text id=”m5k8ag”
ID: BukitTimahTutor.Lane.SecAMath.ControlTower.EMathToAMath.Z0-2.v1.1

LANE := SecAMath
ZOOM := {Z0 StudentRuntime, Z1 SessionRuntime, Z2 CentreRuntime}

PRIMARY_MISSING_EDGES := {
Edge.LedgerUpgrade.EquivalenceDomainReversibility,
Edge.FunctionAsObject.Transformations
}

SENSORS (weekly):
RepSwitch ∈ [0..3]
IBR := validity_breaches_per_question
RA := router_correct/10
DL := sec_to_first_wrong_line
CEI := method_switches_per_question
A1 := domain_first_pass_rate
A2 := conditional_move_explain_pass_rate

ILT_MODULES (core):
Ledger := {ILT.Led2.ECMoveTag, ILT.Led3.DomainFirst, ILT.Led4.Checkpoints3}
Function := {ILT.Func1.MachineIO, ILT.Func2.PredictThenCompute, ILT.Func3.InverseValidity}
Stability := {ILT.Rou2.MethodBudget, ILT.Rou1.FamilyFlash10s, ILT.Deb1.FirstWrongLine45,
ILT.Deb2.RepairLoops, ILT.Load1.SwitchCap, ILT.Load2.CheckpointTimer}

TARGETS:
W1-3 Ledger: IBR<=0.35, A1>=80%, DL<=75, CEI<=1.5 W4-6 Function: RepSwitch>=2(function), RA>=7/10, CEI<=1.2 W7-10 Exam: IBR<=0.25, DL<=45-60, RA>=8/10, CEI<=1

CONTROL_LAW:
Stability iff RepairRate >= DriftRate under_load

SESSION_TEMPLATE:
measure -> choose_one_edge -> stitch(modules) -> timed_mini_set -> retest -> homework -> log
“`

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles: 

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: