Bukit Timah Tutor Secondary Mathematics

WhatsApp Us Here

BukitTimahTutor Lattice Coordinate Standard (V1.1 Canonical)

Title: Lattice Coordinate Standard (BukitTimahTutor)

Definition Lock

Lattice Coordinates (BukitTimahTutor Standard) are stable IDs that encode what an education-system node is and how it connects, so content becomes a machine-readable lattice (graph), not a pile of tuition articles.

A coordinate is not a label.
A coordinate is an identity. It must never be renamed.

1) Coordinate Grammar (Canonical)

All BukitTimahTutor coordinates must follow:

BTT.<LANE>.Z<ZOOM>.<ROLE>.<TYPE>.<ID>

Example

BTT.MAT.Z0.P.ALG.001

Meaning:

  • BTT = BukitTimahTutor domain lattice
  • MAT = Mathematics lane
  • Z0 = atomic execution level
  • P = pipeline (process that must regenerate)
  • ALG = type code (algebra)
  • 001 = stable numeric ID (never reused)

2) Allowed Values (Strict)

(A) Lanes (LANE)

Use only these codes (you can expand later, but don’t rename):

  • EDU — education pipeline / transitions (system-level)
  • MAT — mathematics execution lane
  • ENG — English lane (optional later)
  • EXM — examinations & assessment lane
  • PAR — parent/household support lane
  • TUI — tuition delivery lane (operator mechanics)
  • SEN — sensors / diagnostics lane

Rule: Use the smallest lane that is still correct.
If it’s a math skill pocket, it’s MAT. If it’s exams timing, it’s EXM. If it’s dependency detection, it’s SEN.

(B) Zoom (Z)

Zoom describes where the mechanism lives:

  • Z0 — atomic execution pockets (skills under time pressure)
  • Z1 — support loops (home + tuition scaffolding, routines, dependencies)
  • Z2 — institutional/exam pipeline stage (Sec1→Sec4, O-Level binds, transitions)
  • Z3 — Singapore education interfaces (syllabus, exam structure, placement)

Rule: Zoom is not “difficulty.” Zoom is “system location.”

(C) Role (ROLE)

Role describes the system function:

  • N — node (entity/page: Sec 3 A-Math, a topic cluster)
  • P — pipeline (repeatable process that must regenerate)
  • B — bind (interface/constraint: O-Level, WA, EOY)
  • S — sensor (diagnostic: TTC, dependency, false competence)

(D) Type (TYPE)

Type is a 2–6 letter code. Use uppercase. Examples:

Mathematics (MAT)

  • ALG algebra control
  • DIF differentiation
  • GEO geometry/mensuration
  • TRI trigonometry (optional later)
  • PRB problem solving (optional later)

Exams (EXM)

  • SEC secondary exam pipeline
  • WA weighted assessment bind
  • EOY end-of-year bind
  • OLEV O-Level bind

Support loops

  • HOM household study loop
  • SCF scaffolding loop

Sensors (SEN)

  • TTC time-to-complete / time pressure
  • DEP prompt dependency
  • FCG false competence gauge
  • ERR error pattern class

(E) ID (ID)

001, 002, 003…

Rule: IDs are stable identities, not versions.
Never change an ID. Never reuse an ID. Never “fix” an ID.

If something changes meaningfully:

  • create a new coordinate (new ID),
  • link old → new with “Version Forward” notes.

3) Naming Rules (Do Not Cannibalise)

Your SEO pages must not fight each other. Use this anchor policy:

(A) Hub pages get broad anchors

Only hubs use broad phrases like:

  • “Bukit Timah Tutor”
  • “Secondary Math Tuition Bukit Timah”
  • “How Bukit Timah Tutor works”

(B) Node pages always include the coordinate

Anchor format:
<Node Name> (<COORDINATE>)

Example:

  • Secondary 3 A-Math (BTT.MAT.Z2.N.AM3.001)

This prevents “Secondary 3 A-Math” pages from cannibalising other pages.

(C) Inversion tests always include “(Inversion Test)”

Example:

  • How Mathematics Does Not Work (Inversion Test)

4) Required Sections (Every Page Must Have These)

To be lattice-valid, every page must include:

  1. Lattice Coordinates Referenced (min 5)
  2. Edges Created (BindsTo / Impacts) (min 3)
  3. Sensors Mentioned (min 1)
  4. Lattice Closure Footer links (Hub + Index + Standard)

This makes every article machine-readable as a graph node.

5) Edge Vocabulary (Use only these words)

Keep edge semantics clean:

  • BindsTo = structural link / dependence (pipeline coupling)
  • Impacts = directional influence (variance, load, drift)
  • Observes = sensor detects the signature
  • EscalatesTo = entry → endpoint routing (optional for healthcare style)
  • Stabilises = recovery action reduces variance (optional)

Rule: Default to BindsTo and Impacts.

6) Canonical Examples (Use these as templates)

Example A — Skill pipeline

BTT.MAT.Z0.P.ALG.001

  • BindsTo BTT.EXM.Z2.P.SEC.001
  • ObservedBy BTT.SEN.Z0.S.TTC.001

Example B — Grade node

BTT.MAT.Z2.N.SEC3.001

  • BindsTo BTT.MAT.Z0.P.ALG.001
  • Impacts BTT.SEN.Z1.S.FCG.001 (false competence becomes visible here)

Example C — Dependency sensor

BTT.SEN.Z1.S.DEP.001

  • Impacts BTT.EXM.Z2.B.OLEV.001 (dependency causes rupture under exam load)

7) Version Forward Rule (Never Rename)

If you later improve the model:

  • Do not edit old coordinates to mean new things.
  • Create a new coordinate with a new ID.
  • Add a line:

Version Forward: OldCoord → NewCoord (why)

This keeps Google’s graph stable.

8) WordPress Lattice Footer (Required)

<hr>
<h2>📍 BukitTimahTutor Lattice Closure</h2>
<p><strong>Back to Hub:</strong> <a href="/education-os-bukit-timah-tutor-lattice/">BukitTimahTutor Education OS (Lattice Map)</a></p>
<p><strong>Directory:</strong> <a href="/bukit-timah-tutor-lattice-index/">BukitTimahTutor Lattice Index</a></p>
<p><strong>Standard:</strong> <a href="/bukit-timah-tutor-lattice-coordinate-standard/">Lattice Coordinate Standard (BukitTimahTutor)</a></p>
<hr>

Start Here:

BukitTimahTutor Lattice Graph Block

Z0 Execution:
BTT.MAT.Z0.P.ALG.001
BTT.MAT.Z0.P.DIF.001
BTT.SEN.Z0.S.TTC.001
BTT.MAT.Z0.S.ERR.001

Z1 Support Loops:
BTT.PAR.Z1.P.HOM.001
BTT.TUI.Z1.P.SCF.001
BTT.SEN.Z1.S.DEP.001
BTT.SEN.Z1.S.FCG.001

Z2 Exam/Transition:
BTT.EXM.Z2.P.SEC.001
BTT.EDU.Z2.P.TRN.001
BTT.EXM.Z2.B.OLEV.001

Z3 Interfaces:
SG.EDU.Z3.B.SYL.001
SG.EDU.Z3.B.EXM.001
SG.EDU.Z3.B.PLC.001

Edges:
BTT.TUI.Z1.P.SCF.001 BindsTo BTT.MAT.Z0.P.ALG.001
BTT.MAT.Z0.P.ALG.001 BindsTo BTT.EXM.Z2.P.SEC.001
BTT.EDU.Z2.P.TRN.001 Impacts BTT.EXM.Z2.B.OLEV.001
BTT.SEN.Z1.S.DEP.001 Impacts BTT.EXM.Z2.P.SEC.001
BTT.SEN.Z0.S.TTC.001 Observes BTT.EXM.Z2.P.SEC.001