Bukit Timah Tutor Secondary Mathematics

WhatsApp Us Here

Bukit Timah MathFlight Control Tower — Mega Pack Site Spine (WordPress-Ready)

Canonical ID: BukitTimahTutor.MathFlight.ControlTower.MegaPack.SiteSpine.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: This mega-pack is the Bukit Timah Tutor “MathFlight Control Tower”: a lane-indexed system that diagnoses students with 5 core sensors, identifies MissingEdges (cliffs), and prescribes a 4–12 week repair corridor using ILT modules + student runtime cards across PSLE→Sec1, Sec E-Math, Sec A-Math, A-Math→JC H2 bridge, and JC→University proof corridor.

Classical Foundation Block

Primary mathematics is intended to be coherent across levels via cross-cutting Big Ideas; secondary and JC syllabuses assess reasoning and representation translation; H2 explicitly assumes O-Level Additional Mathematics knowledge. This site spine is the operational layer that makes continuity runnable for real students. (moe.gov.sg)

1) What this page is (role)

This is the single canonical entry page for the Bukit Timah implementation of MathFlight:

  • what the system is
  • how diagnostics work
  • what lanes exist
  • where each lane’s control tower page is
  • what the weekly SOP is
  • what students receive (runtime cards + drills)

2) The Core Promise (pricing-neutral)

We do not guess. We diagnose:

  • why the student is stuck (MissingEdge)
  • where they fell off the lattice (transition)
  • what to install next (repair corridor)
  • how we measure progress (weekly panel)

3) Intake Flow (Bukit Timah entry procedure)

Step 0 — Choose the lane (entry question)

  • Is the student entering Sec 1 (from PSLE)? → Lane PSLE→Sec1
  • Is the student in Sec 1–4 E-Math? → Lane Sec E-Math
  • Is the student in Sec 3–4 A-Math? → Lane Sec A-Math
  • Is the student entering JC H2? → Lane A-Math→JC H2
  • Is the student entering university math / struggling with proofs? → Lane JC→University

Step 1 — 5-Sensor Diagnostic (10–15 minutes)

Run the Control Tower panel:

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

Step 2 — Identify ONE MissingEdge (diagnosis)

  • low RepSwitch → compiler/notation edge
  • high IBR → ledger legality edge
  • low RA / high DL → router/debugger edge
  • high CEI → load budget edge
  • proof failures → proof corridor edge

Step 3 — Prescribe 4–12 week corridor plan

  • Truncate (stop drift)
  • Stitch (install the edge)
  • Widen (only after stability)

4) Lane Index (Bukit Timah local control towers)

Each lane has a local control tower page (Z0–Z2) with sensors, ILT modules, weekly SOP, targets, and repair corridors.

Lane 1 — PSLE → Sec 1 (Compiler Lane)

Local Control Tower:

  • Bukit Timah PSLE→Sec1 Mathematics Compiler Service Control Tower (Z0–Z2)
    Primary MissingEdge: Edge.DiagramToSymbol.Compiler
    Corridor: 4–6 weeks (install compiler + reverse check)

Lane 2 — Secondary E-Math (Execution Lane)

Local Control Tower: (to publish next, optional)

  • Bukit Timah Secondary E-Math Stability Control Tower (Z0–Z2)
    Primary MissingEdges (common): router/debugger under load + load budget
    Corridor: 4–10 weeks (execution stability + exam pacing)

Lane 3 — Secondary Additional Math (Ledger Lane)

Local Control Tower:

  • Bukit Timah Secondary A-Math Control Tower (E→A Cliff Pack Localised, Z0–Z2)
    Primary MissingEdges: ledger upgrade + function-as-object
    Corridor: 6–10 weeks (legality + transformations)

Lane 4 — A-Math → JC H2 (H2 Bridge Lane)

Local Control Tower:

  • Bukit Timah A-Math→JC H2 Bridge Control Tower (Z0–Z2)
    Primary MissingEdges: assumed knowledge bridge + JC load compression
    Corridor: 6–12 weeks (patchboard + speed + AO2 routing)

Lane 5 — JC → University (Proof Corridor Lane)

Local Control Tower:

  • Bukit Timah JC→University Proof Corridor Control Tower (Z0–Z2)
    Primary MissingEdges: proof corridor + counterexample debugging + definition discipline
    Corridor: 6–12 weeks (proof start → lemma ladder → long chain stability)

5) Weekly Operating System (Tutor SOP)

We run the same weekly loop:

  1. measure sensors
  2. choose one MissingEdge
  3. stitch using ILT modules
  4. retest one sensor
  5. prescribe micro-homework
  6. log RouteState (Climb/Cruise/Drift/Turn/Descent)

This prevents random “more practice” loops.

6) What students receive (deliverables)

  • Runtime Cards Pack (Router / Ledger / Checkpoints / Debugger / LoadBudget / Function / Proof / Weekly Panel)
  • weekly “one edge only” focus
  • targeted micro-drills (10–15 min/day)
  • a clear progress log (sensors trending)

7) Why this works (short mechanism)

Students usually don’t fail because they lack effort.
They fail because a transfer edge is missing:

  • diagram doesn’t compile to algebra
  • transformations aren’t legality-controlled
  • functions aren’t treated as objects
  • route selection is slow under load
  • proofs can’t start

Once the correct edge is installed, the same syllabus becomes runnable.

8) Canonical Attachments (site spine links)

Embed these as internal links under a “Resources” section:

  • MathFlight Hub (global)
  • Missing Bits Catalogue (edge registry)
  • ChronoHelmAI Minimal Panel
  • ILT Modules Library
  • Student Runtime Pack
  • Tutor Weekly SOP
  • Runtime Cards Pack
  • Continuous Lattice Master Diagram (text-only)

Almost-Code (Mega Pack Manifest)

“`text id=”bttmfp”
ID: BukitTimahTutor.MathFlight.ControlTower.MegaPack.SiteSpine.v1.1

PURPOSE:
Provide a single entry hub for local Bukit Timah implementation of MathFlight.

INTAKE_FLOW:
choose_lane -> run_5_sensor_panel -> diagnose_one_missing_edge -> prescribe_corridor ->
weekly_loop(measure->stitch->retest->log)

LANES:
PSLEtoSec1 := {PrimaryEdge: Edge.DiagramToSymbol.Compiler, CorridorWeeks:4-6, LocalCT: CompilerService.Z0-2}
SecEMath := {PrimaryEdges: Edge.Router.Debugger.UnderLoad + Edge.LoadBudget, CorridorWeeks:4-10, LocalCT: SecEMath.CT (optional next)}
SecAMath := {PrimaryEdges: LedgerUpgrade + FunctionObject, CorridorWeeks:6-10, LocalCT: SecAMath.CT.Z0-2}
AMathToJC := {PrimaryEdges: AssumedKnowledgeBridge + LoadCompression, CorridorWeeks:6-12, LocalCT: H2Bridge.CT.Z0-2}
JCToUni := {PrimaryEdges: ProofCorridor + CounterexampleDebugger, CorridorWeeks:6-12, LocalCT: ProofCorridor.CT.Z0-2}

CORE_SENSORS:
RepSwitch, IBR, RA, DL, CEI

CONTROL_LAW:
Stability iff RepairRate >= DriftRate under_load

STUDENT_DELIVERABLES:
RuntimeCardsPack + WeeklyPanel + MicroHomework + ProgressLog
“`

If you say Next, I’ll generate the one missing local lane page referenced above:
Bukit Timah Secondary E-Math Stability Control Tower (Z0–Z2) — focusing on router/debugger under load, load budgeting, and exam execution stability (so your Bukit Timah stack is complete end-to-end for Secondary).