Bukit Timah Tutor Secondary Mathematics

WhatsApp Us Here

Bukit Timah A-Math → JC H2 Bridge Control Tower (Assumed Knowledge Patchboard + Load Compression, Z0–Z2)

Canonical ID: BukitTimahTutor.Lane.AMathToJC.ControlTower.H2Bridge.Z0-2.v1.1
Suggested slug: /bukit-timah-a-math-to-jc-h2-bridge-control-tower/

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: JC H2 Math is a compression gate that explicitly assumes O-Level Additional Mathematics knowledge; this Control Tower bridges the assumed-knowledge dependency and stabilises routing/debugging under JC load using a Patchboard + sensors + a 6–12 week repair corridor.
Baseline anchor: H2 Mathematics appends assumed knowledge from O-Level Additional Mathematics. (seab.gov.sg)

Classical Foundation Block

  • H2 Mathematics (9758): includes an “Assumed Knowledge” section for O-Level Additional Mathematics and expects GC use (with limitations); AOs require selecting strategies, translating between forms, and integrating concepts. (seab.gov.sg)
  • Operationally: if assumed-knowledge gaps exist, the student’s DriftRate spikes; if routing/debugging speed is low, time debt accumulates.

Civilisation-Grade Definition (eduKateSG / Bukit Timah Tutor)

H2 Bridge Control Tower = a local service that ensures JC H2 is runnable by installing:

  • Assumed Knowledge completeness + speed (Patchboard)
  • Router under load (AO2 discipline)
  • Debugger under load (first wrong line speed)
  • Load budget tightening (checkpoint timer; method switch cap)
  • GC verification discipline (verify, don’t outsource thinking)

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

Canonical Framing Box (Placement)

  • Scale: Human / Local District
  • Domain: EducationOS → MathOS → FlightPath
  • Lane: AMathToJC (H2 bridge)
  • Zoom: Z0 (student runtime), Z1 (session runtime), Z2 (centre runtime)
  • Phase target: P2 stability (runnable H2 baseline) → P3 transfer (mixed-topic AO2 integration)

Service Entry (Who this is for)

Who

  • Students entering JC1 H2 Mathematics (or planning to)
  • Students in JC1 struggling early because prerequisites are shaky
  • Strong students aiming for H3 / Further Math but with hidden gaps

Success looks like

Within 6–12 weeks:

  • assumed-knowledge items are stable and fast
  • mixed-topic questions become startable with a plan
  • time debt decreases; confidence returns

Z0. Student Runtime (what the student runs)

Z0 Minimum Runtime Card Set (JC H2)

  1. Router10s + 2-minute route plan for mixed questions
  2. Ledger (C-move checks) + checkpoints every 3–5 lines
  3. Debugger: first wrong line (≤40s goal by mid-JC1)
  4. LoadBudget: checkpoint timer (2–3 min), ≤1 method switch
  5. GC discipline: verify + sketch + sanity check (not replace working)

Z1. Session Runtime (weekly lesson operation)

1) 10–12 Minute Entry Scan (Sensors)

Core sensors

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

H2 Bridge sensors (Patchboard)

AK-Scan (10 items): quick micro-tasks sampled from the H2 assumed-knowledge dependency list (O-Level A-Math). (seab.gov.sg)

Minimum AK items to scan weekly:

  1. completing square for max/min
  2. discriminant condition reasoning
  3. surd rationalisation
  4. partial fractions (basic permitted forms)
  5. log laws + change of base + solve with domain
  6. trig identities/equations basics
  7. chain rule + product/quotient
  8. stationary point classification basics
  9. basic integration set (poly/exp/trig)
  10. graph/meaning sanity check (GC verify)

Output metrics

  • AK-PassRate (% correct)
  • AK-Speed (seconds/item average)
  • AK-LedgerRate (domain/condition lines present when required)

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

Priority order for this lane:

  1. Edge.AssumedKnowledge.BridgeToH2
  2. Edge.Router.Debugger.UnderLoad
  3. Edge.LoadBudget.JCCompression
  4. Edge.LedgerUpgrade (if IBR high)

Rule: One primary edge per week.

3) Patchboard System (the core of this control tower)

Patchboard categories (local naming)

  • AK-A Algebra core (quadratics/surds/polynomials/PF)
  • AK-B Functions/logs/trig (graphs, identities, equations)
  • AK-C Calculus core (diff rules, stationary points, integration basics)

Each patch is tagged:

  • G (Green): stable + fast
  • Y (Yellow): correct but slow / shaky
  • R (Red): broken (causes drift)

Policy: Fix Reds first, then Yellow speed, then widen.

4) Core Stitch Modules (ILT)

Assumed-knowledge stitching

  • ILT.Rou2.MethodBudget (safe route per AK family)
  • ILT.Led4.Checkpoints3 (prevent long drift)
  • ILT.Deb2.RepairLoops (patch specific breach classes)

JC load compression stitching

  • ILT.Rou3.MixedTopicAO2 (2-minute plan)
  • ILT.Deb1.FirstWrongLine45 (target ≤40s)
  • ILT.Load2.CheckpointTimer
  • ILT.Load1.SwitchCap

GC discipline stitching

  • ILT.GC1.VerifySketchSanity (local alias of GC protocol)

5) Lesson Structure (60–90 min templates)

Template A (60 min)

  • 12 min sensors + AK-Scan
  • 25 min patchboard drills (Reds only)
  • 18 min 2-question timed mini-set (mixed)
  • 5 min retest AK-PassRate or DL + log

Template B (90 min)

  • 12 min sensors + AK-Scan
  • 35 min patchboard drills + coached correction
  • 30 min mixed-topic integration set (AO2 plan required)
  • 13 min review: first wrong line + ledger checks + homework

Z2. Centre Runtime (Bukit Timah cohort control)

Weekly tracking fields

  • RouteState (Climb/Cruise/Drift/Turn/Descent)
  • RepSwitch, IBR, RA, DL, CEI
  • AK-PassRate, AK-Speed, AK-LedgerRate
  • Primary MissingEdge (one)
  • Active patchboard Reds list
  • Week in corridor (1–12)

Cohort analytics (district signal)

  • top 3 broken patches (usually logs/trig/calculus rules)
  • median DL under timed conditions
  • % students reaching AK-PassRate ≥ 80% by Week 4–6

Targets (by phase)

Phase 1 — Make H2 runnable (Weeks 1–4)

  • AK-PassRate ≥ 70%
  • DL ≤ 60s
  • CEI ≤ 1.5
  • IBR trending down (ledger enforcement begins)

Phase 2 — Stabilise under JC load (Weeks 5–8)

  • AK-PassRate ≥ 80%
  • AK-Speed ≤ 60–75s/item (rough band; trend matters)
  • DL ≤ 40–50s
  • RA ≥ 7/10
  • CEI ≤ 1.2

Phase 3 — AO2 integration (Weeks 9–12)

  • RA ≥ 8/10
  • DL ≤ 40s
  • CEI ≤ 1
  • AK-PassRate stable ≥ 85%
  • Mixed-topic transfer pass trending ↑

Failure Trace (3 collapse modes only)

  1. Amplitude collapse: one red patch (logs/trig/calc rule) blocks whole question → panic
  2. Slow attrition: many yellow patches → constant remediation → time debt grows
  3. Fast attrition: early wrong line + slow debug → entire timed set collapses

Repair Corridor (6–12 week plan)

Phase 1 (Weeks 1–4): Patch Reds

  • weekly AK-Scan
  • fix only Reds (do not widen yet)
  • enforce checkpoints and condition lines

Phase 2 (Weeks 5–8): Speed + Load Compression

  • timed mini-sets
  • enforce checkpoint timer
  • reduce method switching

Phase 3 (Weeks 9–12): Mixed-topic AO2 corridor

  • 2-minute route plan before each question
  • integrate topics (functions + calculus + stats reasoning)
  • GC used only for verify/sanity unless explicitly required

ChronoFlight Slice (A-Math → JC H2)

  • RouteState default: Drift risk spikes in JC1 Term 1
  • Primary drift: assumed-knowledge mismatch + compressed time
  • Primary repair: patchboard + router/debugger speed + load control
  • Next-slice risk: H3/Further assumes H2; if this gate fails, corridor narrows sharply. (seab.gov.sg)

Almost-Code (Machine-Readable Control Tower Spec)

“`text id=”mkh2b8″
ID: BukitTimahTutor.Lane.AMathToJC.ControlTower.H2Bridge.Z0-2.v1.1

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

EVIDENCE_ANCHOR:
H2_9758 includes “Assumed Knowledge for O-Level Additional Mathematics appended”

PRIMARY_MISSING_EDGES := {
Edge.AssumedKnowledge.BridgeToH2,
Edge.Router.Debugger.UnderLoad,
Edge.LoadBudget.JCCompression
}

SENSORS (weekly):
Core := {RepSwitch, IBR, RA, DL, CEI}
AK := {AK-PassRate, AK-Speed, AK-LedgerRate}

PATCHBOARD:
Categories := {AK-A Algebra, AK-B Functions/Logs/Trig, AK-C Calculus}
Status := {G stable, Y shaky/slow, R broken}
Policy := fix R then Y-speed then widen

ILT_MODULES (core):
Routing := {ILT.Rou3.MixedTopicAO2, ILT.Rou2.MethodBudget}
Debug := {ILT.Deb1.FirstWrongLine45, ILT.Deb2.RepairLoops}
Load := {ILT.Load2.CheckpointTimer, ILT.Load1.SwitchCap}
Ledger := {ILT.Led4.Checkpoints3, ILT.Led3.DomainFirst}
GC := {ILT.GC1.VerifySketchSanity}

TARGETS:
W1-4: AK-PassRate>=70%, DL<=60, CEI<=1.5 W5-8: AK-PassRate>=80%, DL<=50, RA>=7/10, CEI<=1.2 W9-12: RA>=8/10, DL<=40, CEI<=1, AK-PassRate>=85%

CONTROL_LAW:
Stability iff RepairRate >= DriftRate under_load

SESSION_TEMPLATE:
measure -> choose_one_edge -> patchboard(Reds) -> timed_mini_set -> retest -> homework -> log
“`

If you say Next, I’ll generate the final local page in this Bukit Timah stack:
Bukit Timah JC → University Proof Corridor Control Tower (Z0–Z2) (premium pathway, proof start engine, counterexample debugger, lemma ladder, weekly sensors).