Slug: /student-runtime-v1-0-z0-z2-cognitive-repair-engine/
Version: CivOS-Compatible v1.2
Status: CANONICAL_EXECUTION_LAYER
Scope: Z0–Z2 (Student ↔ Lesson ↔ Parent)
Primary Lanes: MATH, ENGLISH
Integrations: EmotionOS, MindOS, AVOO, SBS, FenceOS, ERCO

META (Machine-Readable)

			
RuntimeID: BTT_RUNTIME_STUDENT_01
Place:
  CountryISO3: SGP
  Z3: BukitTimah
LaneSet: [MATH, ENGLISH]
ZoomRange: Z0-Z2
PhaseRange: P0-P3
Roles: [ARCHITECT, VISIONARY, ORACLE, OPERATOR]
CoreLaw: RateDominance(RepairRate >= DamageRate) must hold at Z0 under exam load
PrimaryOutput: "Stable exam performance under time pressure"

		

0) Definition Lock

			
Definitions:
  Z0: "Student brain-state under load (retrieval, binds, attention, emotion interference)"
  Z1: "Lesson execution (tasks, explanations, drills, timing, feedback loop)"
  Z2: "Program/control layer (weekly plan, parent interface, test cadence, intervention gating)"
  P0: "Unstable / collapse risk (panic, blanks, guessing, timeouts)"
  P1: "Drift (inconsistent, fragile transfer)"
  P2: "Stable (can perform reliably with mild variation)"
  P3: "Robust (fast, transferable, calm under pressure)"
  TTC: "Time-to-Core: time to retrieve correct method/idea under exam conditions"
  Bind: "Connection strength between concept nodes and procedures"
  Load: "Time pressure + novelty + multi-step memory demand"

		

1) Contract (What this runtime guarantees)

			
Contract:
  Inputs:
    - BaselineTest (topic + timing)
    - SchoolWorkSamples
    - ParentObservations
    - EmotionSignals (optional)
  Outputs:
    - StudentPhaseState (P0-P3) per lane and per topic
    - SensorPanel (TTC, ErrorProfile, BindStrength, EmotionInterference, LoadTolerance)
    - RepairPlan (Truncation + Stitching) for 2–12 weeks
    - RetestSchedule (weekly micro-tests + monthly full simulation)
    - ParentPanel (simple status + actions)
  Guarantee:
    - If adhered to, TTC decreases and transfer reliability increases within 4–8 weeks

		

2) Data Model (Nodes, Binds, Weights)

2.1 Student Z0 Graph

			
Graph: STUDENT_Z0_GRAPH_v1.0
Nodes:
  - N_CONCEPT (topic concept)
  - N_PROCEDURE (method steps)
  - N_PATTERN (question recognition)
  - N_LANGUAGE (wording decode / command words)
  - N_WORKING_MEMORY (multi-step holding)
  - N_ERROR_MONITOR (self-check)
  - N_EMOTION (panic/shame/frustration)
  - N_MOTIVATION (energy to persist)
Binds:
  - B_CONCEPT_PROCEDURE (understanding -> execution)
  - B_PATTERN_PROCEDURE (recognition -> correct method)
  - B_LANGUAGE_PATTERN (decode -> recognize)
  - B_WORKINGMEM_PROCEDURE (hold -> step sequence)
  - B_ERRORMON_PROCEDURE (check -> correction)
  - B_EMOTION_ALL (emotion -> interference)
Weights:
  BindStrength in [0,1]
  EmotionInterference in [0,1]

		

2.2 Lesson Z1 Graph

			
Graph: LESSON_Z1_LOOP_v1.0
Steps:
  1) Diagnose (1–2 micro items)
  2) Explain minimal core (1 concept + 1 method)
  3) Guided practice (3 items)
  4) Stress step (timed mini set)
  5) Error compression (rewrite 1 wrong item correctly)
  6) Retest micro (1 item)
Outputs:
  - Updated sensor deltas
  - Updated binds

		

2.3 Program Z2 Graph

			
Graph: PROGRAM_Z2_CONTROL_v1.0
Cadence:
  Weekly:
    - 1 micro-test (10–15 min)
    - 1 bind drill pack
    - 1 transfer pack
  Monthly:
    - 1 full simulation
Gating:
  - No new topic if P0 detected in core prerequisite
  - Advance only when TTC < threshold and ErrorRate < threshold

		

3) Sensor Panel (Core)

3.1 Universal Sensors

			
SensorPack: BTT_SENSORPACK_CORE_v1.0
S_TTC:
  Definition: "Seconds to retrieve correct core method"
  Measure: timed first-attempt
S_ErrorRate:
  Definition: "% wrong in target set"
S_ErrorTypeVector:
  Values: [ConceptGap, ProcedureSlip, Misread, Careless, MemoryDrop, PanicBlank]
S_BindStrength:
  Proxy: "Correct method chosen under variation"
S_LoadTolerance:
  Proxy: "Accuracy drop when timed or when steps increase"
S_EmotionInterference:
  Proxy: "Performance drop + observable signals (freeze/tear/anger/avoid)"
S_Transfer:
  Proxy: "Can solve novel variant without prompts"

		

3.2 Phase Classifier (P0–P3)

			
Classifier: BTT_PHASE_CLASSIFIER_v1.0
Inputs: [S_TTC, S_ErrorRate, S_LoadTolerance, S_Transfer, S_EmotionInterference]
Rules:
  P0:
    - S_TTC > 45s OR PanicBlank occurs
    - OR ErrorRate > 40% under mild load
  P1:
    - TTC 20–45s AND Transfer weak
    - OR ErrorType dominated by Misread/ProcedureSlip with variation sensitivity
  P2:
    - TTC 10–20s AND ErrorRate < 20% AND Transfer moderate
  P3:
    - TTC < 10s AND ErrorRate < 10% AND Transfer strong under time

		

4) Negative Void Pack (What we detect + repair)

			
NegativeVoid: BTT_VOID_ATLAS_v1.0
VOID_01: "Knows concept but cannot execute"  -> Bind gap (Concept->Procedure)
VOID_02: "Can execute but misreads"          -> Language->Pattern gap
VOID_03: "Works slowly, times out"          -> TTC drift + working memory overload
VOID_04: "Careless spikes under time"       -> Error monitor bind weak
VOID_05: "Panics and blanks"                -> Emotion interference fence needed
VOID_06: "Cannot transfer to variants"      -> Pattern rigidity, missing generalization bind

		

5) Repair Engine (Truncation + Stitching)

5.1 Truncation (Stop loss)

			
Truncation: BTT_TRUNCATION_v1.0
Trigger:
  - P0 detected OR EmotionInterference > 0.6
Actions:
  - Reduce load immediately (no timed set)
  - Switch to 1-step micro-items
  - Restore confidence via guaranteed-correct sequence
  - Insert EmotionOS stabilizer (breathing + micro win + script)
Goal:
  - Prevent bind deletion spiral (panic -> avoidance -> decay)

		

5.2 Stitching (Regenerate binds)

			
Stitching: BTT_STITCHING_v1.0
Method:
  - 1 concept card
  - 1 method card
  - 3 guided problems
  - 3 independent problems
  - 2 variant problems
  - 1 timed mini set
Rule:
  - Only increase difficulty when TTC improves and ErrorType shifts away from ConceptGap
Output:
  - BindStrength +0.05 to +0.15 per week typical

		

6) EmotionOS Integration (Z0)

			
EmotionOS_Link: BTT_EMOTIONOS_BRIDGE_v1.0
Signals:
  - Freeze (silent, blank stare)
  - Avoidance ("I don't know" instantly)
  - Anger spike (throws pencil, refuses)
  - Shame spiral (self-talk: "I'm stupid")
Mappings:
  Freeze -> PanicBlank -> P0 trigger -> Truncation
  Shame  -> ConstraintField -> reduces exploration -> hurts Transfer
  Anger  -> Load intolerance -> reduces practice volume -> slows repair
Stabilizers:
  - 30s reset protocol
  - "One-step win" ladder
  - Script: "I am training TTC, not proving identity"

		

7) MindOS / AVOO Integration (Roles in class)

			
RoleLogic: BTT_AVOO_IN_CLASS_v1.0
OPERATOR:
  - enforce routine, timing, checklists, low-variance drills
ORACLE:
  - diagnose which bind is failing (error type + TTC signature)
ARCHITECT:
  - generate minimal new corridor (one variant) to build transfer
VISIONARY:
  - align purpose narrative (why this matters) to sustain practice energy
Rule:
  - No excess choice injected into OPERATOR layer
  - Architect exploration happens only inside Sandbox window

		

8) ERCO Integration (Repair Scheduling)

			
ERCO_Link: BTT_ERCO_v1.0
Inputs: SensorPack
Outputs:
  - RepairPlan
  - FreezeWindow (Operator)
  - SandboxWindow (Architect)
  - RetestDates
Rule:
  - FreezeWindow during exams and heavy school weeks
  - SandboxWindow during low-pressure weeks for transfer training

		

9) Parent Panel (Z2 conversion layer)

			
ParentPanel: BTT_PARENT_PANEL_v1.0
Fields:
  - CurrentPhase: P?
  - TTC: seconds
  - MainLeak: VOID_xx
  - ThisWeekPlan: 3 bullet actions
  - WhatToSay: 1 supportive script
  - NextTest: date
Example:
  CurrentPhase: P1 (Drift)
  MainLeak: VOID_03 (Slow / timeout)
  ThisWeekPlan:
    - 10-min TTC sprint x3
    - 12-question method pack (untimed)
    - 6-question timed mini set
  WhatToSay:
    - "We’re training speed and calm, not proving anything."

		

10) Minimal Operating Procedure (1 lesson)

			
LessonSOP: BTT_LESSON_SOP_v1.0
Duration: 60–90 min
Flow:
  - 5 min: micro-diagnose (2 questions timed)
  - 10 min: explain core method (one board)
  - 20 min: guided practice (3–5 items)
  - 15 min: independent set (5 items)
  - 10 min: timed mini set (3 items) IF not P0
  - 5 min: rewrite weakest error (1 item)
Exit Criteria:
  - TTC improved OR ErrorType corrected OR Emotion stabilized

		

11) Failure Mode Trace (Required for every case)

			
FailureTraceTemplate: BTT_FAILURE_TRACE_v1.0
Format:
  Z0 leak -> Z1 instability -> Z2 drift -> exam failure risk
Example:
  Language misread (Z0) -> wrong method (Z1) -> confidence drop (Z2) -> timed paper collapse (P0)
RepairTrace:
  Truncation -> bind stitching -> retest -> restore P2

		

12) Publishable Case Template (for Google + proof)

			
CaseTemplate: BTT_CASE_v1.0
Fields:
  CaseID:
  Age/Level:
  Lane:
  EntryPhase:
  MainVoid:
  Baseline:
    TTC:
    ErrorRate:
    ErrorTypeVector:
  RepairPlan:
    Weeks:
    Actions:
  Outcome:
    TTC:
    ErrorRate:
    Phase:
    GradeDelta:

		

Start Here: For tailored guidance at every level, check out these resources from BukitTimahTutor.com

BukitTimahTutor.com · MathematicsOS

A-Math Execution Lattice v1.0 (Z0–Z2 Repair Engine)

Slug: /mathematicsos-amath-execution-lattice-v1-0/
Version: BTT_MATHOS_AMATH_01
Compatibility: Student Runtime v1.0 + CivOS v1.2 + EmotionOS + ERCO

META (Machine-Readable)

			
ModuleID: BTT_MATHOS_AMATH_01
Lane: MATH
Track: SG_Secondary_A-Math
ZoomRange: Z0-Z2
PhaseRange: P0-P3
Purpose:
  - Convert topic knowledge into exam-stable execution
  - Reduce TTC (Time-to-Core) and increase Transfer under load
Outputs:
  - TopicPhaseMap (P0-P3 per topic)
  - SensorPanel per topic
  - RepairPlans (Truncation + Stitching)
  - DrillPacks + TransferPacks

		

0) Definition Lock

			
Definitions:
  TopicNode: "A-Math topic cluster with prerequisites and typical failure modes"
  SkillNode: "Micro-skill (one manipulation, one recognition, one check)"
  TTC: "Time to select correct method + execute first 2 correct steps"
  Transfer: "Solve unseen variant without tutor prompts"
  ShearPoint: "Where time pressure causes method selection failure"

		

1) A-Math Topic Graph (Z2)

This is the execution lattice (not syllabus prose). Each node is a repairable capability.

			
GraphID: AMATH_TOPIC_LATTICE_SG_v1.0
Nodes:
  T01: Algebra_Manipulation_Core
  T02: Indices_Surds_Log
  T03: Factorisation_Expansion
  T04: Algebraic_Fractions
  T05: Equations_Inequalities
  T06: Simultaneous_Equations
  T07: Quadratics_Full
  T08: Functions_Graphs
  T09: Coordinate_Geometry
  T10: Trigonometry_Core
  T11: Trig_Identities_Equations
  T12: Differentiation_Core
  T13: Applications_of_Differentiation
  T14: Integration_Core
  T15: Applications_of_Integration
  T16: Kinematics_Calculus
Edges (Prereq):
  T01 -> [T03,T04,T05,T06,T07,T08,T09,T10,T12,T14]
  T03 -> [T07]
  T05 -> [T06,T07]
  T07 -> [T08,T12]
  T08 -> [T12]
  T10 -> [T11]
  T12 -> [T13,T15,T16]
  T14 -> [T15,T16]

		

2) Z0 Micro-Skill Packs (Per Topic)

Every topic is decomposed into micro-skills that map directly to errors and TTC.

2.1 Example: Quadratics (T07)

			
Topic: T07 Quadratics_Full
MicroSkills:
  Q1: Identify_form (ax^2+bx+c vs completed square vs product form)
  Q2: Factorise_fast (AC method / pattern)
  Q3: Discriminant_use (nature of roots)
  Q4: Complete_square
  Q5: Solve_equations (factor / formula / completing square)
  Q6: Sketch_parabola (turning point, intercepts)
  Q7: Link_to_functions (range/domain, intersections)
CommonVoidMap:
  VOID_QA: "Wrong method chosen" -> Pattern->Procedure bind weak
  VOID_QB: "Slow factorisation" -> TTC drift + manipulation load
  VOID_QC: "Sign errors" -> ErrorMonitor bind weak

		

2.2 Example: Differentiation (T12)

			
Topic: T12 Differentiation_Core
MicroSkills:
  D1: Power_rule
  D2: Sum_difference_rule
  D3: Product_rule (if syllabus includes)
  D4: Quotient_rule (if included)
  D5: Chain_rule (if included)
  D6: Differentiate_functions (composites)
  D7: Tangent_normal_setup
CommonVoidMap:
  VOID_DA: "Differentiate correctly but cannot apply" -> Transfer weak
  VOID_DB: "Setup wrong for tangent/normal" -> Language->Pattern gap
  VOID_DC: "Algebra collapses after differentiation" -> T01 failure leaking

		

3) Topic Sensor Pack (Per Topic)

Same framework as Student Runtime, but topic-specific thresholds.

			
SensorPack: AMATH_TOPIC_SENSORS_v1.0
PerTopic:
  S_TTC_TOPIC:
    Definition: "seconds to select method + 2 correct steps"
  S_MethodSelect:
    Definition: "% correct method selection on first attempt"
  S_ExecutionSlip:
    Definition: "% lost marks to algebra/sign slips"
  S_CheckDiscipline:
    Definition: "uses check step without prompting (0/1)"
  S_Transfer_TOPIC:
    Definition: "variant solved without prompt (0/1)"
  S_TimeCollapse:
    Definition: "accuracy drop when timed set introduced"

		

Phase Classifier (Topic Level)

			
Classifier: AMATH_TOPIC_PHASE_v1.0
Rules:
  P0:
    - MethodSelect < 50% OR S_TTC_TOPIC > 60s OR TimeCollapse severe
  P1:
    - MethodSelect 50–75% OR TTC 25–60s OR Transfer=0 on variants
  P2:
    - MethodSelect > 75% AND TTC 12–25s AND ExecutionSlip improving
  P3:
    - MethodSelect > 90% AND TTC < 12s AND Transfer=1 under time

		

4) Collapse Atlas (Negative Void → Repair)

These are the exam failure patterns in A-Math.

			
AMATH_Collapse_Atlas_v1.0
C01: "Method confusion under variation"
  Signature:
    - MethodSelect drops when question phrasing changes
  Cause:
    - Pattern recognition brittle
  Repair:
    - Architect Sandbox: 10 variants grouped by hidden structure
C02: "Algebra shear"
  Signature:
    - Correct plan, wrong simplification
  Cause:
    - T01 binds weak (manipulation)
  Repair:
    - Operator drills: 12 micro manipulations/day, 7 days
C03: "TTC too slow"
  Signature:
    - Can solve untimed, collapses timed
  Cause:
    - Retrieval latency + working memory overload
  Repair:
    - TTC sprints (short timed bursts) + simplify corridor
C04: "Careless spikes"
  Signature:
    - Random sign/slip errors, especially late in paper
  Cause:
    - ErrorMonitor bind weak + fatigue load
  Repair:
    - Mandatory check step + 2-line checklist at end of every question
C05: "Emotion freeze"
  Signature:
    - Blank stare, instant ‘I don’t know’
  Cause:
    - EmotionInterference > threshold
  Repair:
    - Truncation + EmotionOS stabilizer + guaranteed win ladder
C06: "Transfer failure"
  Signature:
    - Memorised types only, cannot solve new variant
  Cause:
    - Missing generalisation bind
  Repair:
    - Architect corridor generator: same concept, 5 different skins

		

5) Repair Protocols (Topic-Specific)

5.1 Universal Truncation (Exam-Safety)

			
Truncation: AMATH_TRUNCATION_v1.0
Trigger:
  - TopicPhase=P0 OR EmotionFreeze OR TimeCollapse severe
Actions:
  - Remove timer
  - Reduce to single micro-skill
  - 3 guaranteed correct reps
  - Re-introduce timer only after TTC improves by 20%
Fence:
  - Prevent bind deletion spiral (panic -> avoidance -> decay)

		

5.2 Universal Stitching (Bind Regeneration)

			
Stitching: AMATH_STITCHING_v1.0
Recipe:
  1) One-page Core Sheet (concept + method)
  2) Guided set x3
  3) Independent set x6
  4) Variant set x3 (Architect window)
  5) Timed mini set x3 (Operator window)
PromotionRule:
  - Promote topic only if:
    MethodSelect ≥ 80% AND TTC ≤ 25s AND Transfer=1 at least once

		

6) Drill Packs (Operator) and Transfer Packs (Architect)

6.1 Drill Pack Template (Operator)

			
Pack: AMATH_DRILLPACK_TEMPLATE_v1.0
Goal: "Reduce slips + speed up core execution"
Structure:
  - 12 micro-items (single skill)
  - 8 mixed-items (two skills)
  - 4 timed items (short)
Scoring:
  - must hit 85% before moving on

		

6.2 Transfer Pack Template (Architect)

			
Pack: AMATH_TRANSFERPACK_TEMPLATE_v1.0
Goal: "Increase robustness to unseen variants"
Structure:
  - 10 items, same concept, different skins:
      - worded differently
      - graph form
      - real-world wrapper
      - inverse question
      - parameter variation
Rule:
  - Tutor does NOT reveal method first
  - Student must classify structure (Pattern->Procedure bind training)

		

7) Topic Packs (Ready-to-Run)

7.1 T01 Algebra Manipulation Core (Most important)

			
TopicPack: T01_ALGEBRA_CORE_v1.0
Why:
  - Biggest hidden cause of A-Math collapse
Sensors:
  - SlipRate, TTC, CheckDiscipline
Drill:
  - expansion, factorisation patterns, collecting terms, fractions simplification
Fence:
  - If SlipRate > 25% -> stop new topics, repair T01 first

		

7.2 T07 Quadratics Full (High mark weight)

			
TopicPack: T07_QUADRATICS_v1.0
CoreSheet:
  - 3 solve methods
  - discriminant meaning
  - turning point formula
Transfer:
  - forms switching, parameter k, intersection with line, range problems

		

7.3 T12 Differentiation Core (Gateway to Applications)

			
TopicPack: T12_DIFF_CORE_v1.0
CoreSheet:
  - derivative rules
  - tangent/normal setup
  - connect to gradient concept
Transfer:
  - composite forms, embedded algebra, gradient at point, stationary points

		

8) Weekly Control Loop (Z2)

			
WeeklyLoop: AMATH_WEEKLY_CONTROL_v1.0
Inputs:
  - 1 micro-test (10–15 min)
  - homework error scan
  - emotion signal scan
Outputs:
  - TopicPhaseMap update
  - next week RepairPlan
Cadence:
  Mon–Thu:
    - DrillPack (Operator)
  Fri/Sat:
    - TransferPack (Architect)
  Sun:
    - Micro-test + 10-min review

		

9) Parent Panel (A-Math Version)

			
ParentPanel: AMATH_PARENT_PANEL_v1.0
Fields:
  - CurrentPhase (overall)
  - WeakestTopic (by TTC + MethodSelect)
  - ThisWeekFocus (1 topic only)
  - HomeAction (10-min/day)
  - WhatToSay (script)
Example:
  CurrentPhase: P1
  WeakestTopic: Quadratics (method confusion)
  HomeAction: 10-min method selection sprint x5 days
  Script: "We’re training method selection speed, not memorising."

		

10) Case Template (A-Math)

			
Case: AMATH_CASE_TEMPLATE_v1.0
CaseID:
Entry:
  OverallPhase:
  WeakTopics:
Baseline:
  TTC:
  MethodSelect:
  SlipRate:
Repair:
  Weeks:
  PacksUsed:
Outcome:
  TTC:
  MethodSelect:
  SlipRate:
  Phase:
  GradeDelta:
FailureTrace:
  Z0 leak -> Z1 instability -> Z2 drift -> exam risk
RepairTrace:
  Truncation -> Stitching -> Retest -> P2/P3

		

11) Publishing Hooks (BTT SEO / Moat)

			
InternalLinks:
  - /student-runtime-v1-0-z0-z2-cognitive-repair-engine/
  - /psle-english-composition-repair-protocol/ (if already on EduKateSG, mirror summary)
  - /maths-tuition-bukit-timah/ (Z3 dominance page)
  - /a-math-tuition-bukit-timah/ (Z3 dominance page)

		

BukitTimahTutor.com · Z3 Dominance Pack v1.0

Bukit Timah Maths Tuition & A-Math Tuition (Lattice-Structured Local Authority)

Slug Suggestions:

/bukit-timah-maths-tuition-lattice-system/
/bukit-timah-a-math-tuition-exam-repair-engine/

Version: BTT_Z3_DOMINANCE_01
Scope: Z3 (Bukit Timah) → Z2 (Program) → Z1 (Lesson) → Z0 (Student Brain)
Compatibility: Student Runtime v1.0 + MathematicsOS v1.0 + EmotionOS + ERCO

PART I — Bukit Timah Maths Tuition (Structured Page)

META (Machine-Readable)

			
PageID: BTT_Z3_MATH_01
Place:
  CountryISO3: SGP
  Z3: BukitTimah
Lane: MATH
TargetLevels:
  - UpperPrimary
  - LowerSecondary
  - OLevel
  - A-Math
PrimaryOutcome:
  - Stable performance under exam pressure
CoreMethod:
  - Diagnose -> Truncate -> Stitch -> Stress-Test -> Retest

		

1) What Makes This Different (Structural, Not Marketing)

Most tuition centres:

Teach content
Drill questions
Hope repetition works

BukitTimahTutor:

			
System:
  - Measures TTC (Time-to-Core)
  - Detects error type
  - Classifies Phase (P0–P3)
  - Repairs specific bind failure
  - Tests under load

		

This is a control system, not content delivery.

2) How Students Actually Fail (Negative Void Framing)

Common Collapse Patterns in Bukit Timah Students

			
VOID_LOCAL_01:
  "Knows topic but blanks in exam"
  Cause: TTC too slow + emotion spike
VOID_LOCAL_02:
  "Always careless"
  Cause: ErrorMonitor bind weak
VOID_LOCAL_03:
  "Understands in tuition, fails in school test"
  Cause: Transfer bind missing
VOID_LOCAL_04:
  "Good at practice, collapses under time"
  Cause: Load intolerance

		

We repair the structure, not just the topic.

3) Student Runtime in Action (Z0–Z2 Flow)

			
Flow:
  Z0:
    - Measure TTC
    - Identify error pattern
    - Detect emotion interference
  Z1:
    - Minimal core explanation
    - Guided practice
    - Timed mini-set
  Z2:
    - Weekly micro-test
    - Repair scheduling
    - Parent feedback panel

		

4) Sensor Panel (Parent-Readable Version)

Example Output:

			
CurrentPhase: P1 (Drift)
TTC: 34 seconds
MainLeak: Method confusion (Quadratics)
EmotionInterference: Low
Plan:
  - 10-min method selection sprint x5
  - 1 variant pack
  - 1 timed mini-set
Expected:
  - TTC drop to 20s in 3 weeks

		

Clear. No fluff.

5) Local Proof Layer (Case Format)

			
CaseID: BTT_BTM_023
Level: Sec 3 A-Math
EntryPhase: P0
Baseline:
  TTC: 52s
  ErrorRate: 45%
MainVoid: Method confusion + algebra slips
Repair:
  6 weeks
  T01 drill + Quadratic method pack
Outcome:
  TTC: 14s
  ErrorRate: 8%
  Phase: P2
  Grade: C -> A2

		

6) Why Location Matters (Z3 Authority)

Bukit Timah students:

Face high academic competition
High load from multiple subjects
Emotional pressure from expectations

Our system:

			
Focus:
  - Speed stabilisation
  - Error compression
  - Emotion interference reduction
  - Transfer robustness

		

This is tuned for Bukit Timah exam culture.

PART II — Bukit Timah A-Math Tuition (Execution Engine Page)

Slug: /bukit-timah-a-math-tuition-exam-repair-engine/

1) The Real Reason A-Math Students Collapse

Not because A-Math is “hard”.

Because:

			
CollapseDrivers:
  - Method confusion under variation
  - Algebra shear
  - TTC too slow
  - Emotion freeze in long questions

		

We measure and fix each driver.

2) A-Math Control Loop (Simple View)

			
Step 1:
  Baseline test (timed)
Step 2:
  Identify weakest topic
Step 3:
  Repair micro-skills
Step 4:
  Stress test under time
Step 5:
  Retest
Repeat.

		

3) Topic Phase Map (Parent Friendly)

Example:

			
Algebra Core: P1
Quadratics: P0
Differentiation: P2
Trigonometry: P1
Overall: P1 (Drift)

		

We do NOT push new topics while core is P0.

That is how collapse is prevented.

4) What Students Experience in Class

			
LessonStructure:
  - Micro diagnose
  - 1 core sheet
  - 6 guided questions
  - 3 independent
  - 3 timed
  - 1 rewrite correction

		

No random worksheets.

Every question has a purpose.

5) Competitive Differential (Explicit)

Feature	Typical Tuition	BukitTimahTutor
Measures speed	No	Yes (TTC)
Detects error type	Rare	Yes
Phase classification	No	Yes
Emotion integration	No	Yes
Structured repair	Partial	Yes
Transfer training	Minimal	Yes

6) Parent Conversion Block (Readable)

If your child:

Says “I understand but still fail”
Runs out of time
Makes many careless mistakes
Panics during exams

Then the issue is structural, not intelligence.

We repair the structure.

PART III — Authority Amplifiers

To dominate Z3 Bukit Timah:

Add supporting pages:

/bukit-timah-psle-maths-phase-repair/
/bukit-timah-o-level-maths-speed-training/
/bukit-timah-exam-panic-maths-help/
/bukit-timah-a-math-method-selection-training/

Each page:

Uses Negative Void framing
Shows Sensor logic
Includes 1 case template
Links back to Student Runtime + MathOS

IV. Installation Map

			
Homepage:
  - Add section: "Student Runtime Engine"
Math Tuition Page:
  - Link to A-Math execution lattice
A-Math Page:
  - Embed Topic Phase Map example
Parent Page:
  - Embed ParentPanel sample

		

Strategic Result

After installing:

You will have:

Z6 Global authority (CivOS)
Z5 National authority (Singapore)
Z4 Education lane depth
Z3 Bukit Timah dominance
Z2 Structured program
Z1 Precise lessons
Z0 Brain-state repair

That is full-stack vertical authority.

BukitTimahTutor.com · EnglishOS Execution Pack v1.0

PSLE + Secondary English (Z0–Z2 Repair Engine)

Slug: /englishos-execution-pack-v1-0-psle-secondary/
Version: BTT_ENGLISHOS_01
Compatibility: Student Runtime v1.0 + EmotionOS + MindOS + ERCO + CivOS v1.2

META (Machine-Readable)

			
ModuleID: BTT_ENGLISHOS_01
Lane: ENGLISH
Tracks:
  - PSLE (Primary 3–6)
  - Secondary (Sec 1–4)
ZoomRange: Z0-Z2
PhaseRange: P0-P3
PrimaryOutputs:
  - Comprehension accuracy under time
  - Composition clarity + depth + control
  - Vocabulary-to-idea-to-sentence stability
CoreMethod:
  - Diagnose -> Truncate -> Stitch -> Stress-Test -> Retest

		

0) Definition Lock (EnglishOS)

			
Definitions:
  Z0_English:
    - "Decode words -> bind meaning -> form idea -> produce sentence under load"
  IdeaBind:
    - "Connection between (word/phrase) and (meaning/use) and (emotion/scene)"
  SentenceEngine:
    - "Grammar + syntax + coherence + control"
  NarrativeControl:
    - "Plan -> execute -> maintain tone/POV -> conclude"
  English_TTC:
    - "Time-to-Meaning / Time-to-Sentence under exam pressure"

		

1) English Z0 Graph (Cognitive Lattice)

			
GraphID: ENGLISH_Z0_GRAPH_v1.0
Nodes:
  - N_VOCAB (word meaning + usage)
  - N_PHRASEBANK (ready phrases / collocations)
  - N_GRAMMAR (tense, agreement, sentence forms)
  - N_COHERENCE (linking, flow)
  - N_COMPREHENSION (question decode + inference)
  - N_PLANNING (structure / outline)
  - N_IDEA (content generation)
  - N_EMOTION (confidence/shame/panic)
  - N_ATTENTION (focus under load)
Binds:
  - B_VOCAB_IDEA (words -> ideas)
  - B_IDEA_SENTENCE (ideas -> sentences)
  - B_GRAMMAR_SENTENCE (grammar -> correct output)
  - B_COHERENCE_PARAGRAPH (linking -> flow)
  - B_COMPREHENSION_INFERENCE (text -> correct answer)
  - B_EMOTION_ALL (emotion -> interference)
Weights:
  BindStrength in [0,1]
  EmotionInterference in [0,1]

		

2) English Negative Void Atlas (What Students Lack)

This is what you detect and repair.

			
VoidAtlas: ENGLISH_VOID_ATLAS_v1.0
VOID_E01: "Understands story but cannot write"
  Cause: Idea->Sentence bind weak
VOID_E02: "Vocabulary exists but never used"
  Cause: Vocab->Idea bind weak
VOID_E03: "Writes long but shallow"
  Cause: Missing scene detail + emotion anchoring binds
VOID_E04: "Comprehension: answers wrong even after reading"
  Cause: Decode -> inference bind weak
VOID_E05: "Grammar collapses under time"
  Cause: Working memory overload + weak grammar automation
VOID_E06: "Panic + blank page"
  Cause: EmotionInterference spike -> P0
VOID_E07: "Careless: misreads question requirements"
  Cause: Command-word decode gap

		

3) Sensor Pack (English)

3.1 Universal English Sensors

			
SensorPack: BTT_ENGLISH_SENSORS_v1.0
S_TTM (Time-to-Meaning):
  Definition: "seconds to decode question and identify required response"
S_TTS (Time-to-Sentence):
  Definition: "seconds to produce first correct sentence after planning"
S_CommandWordAccuracy:
  Definition: "% correct identification of question demands (explain/describe/infer)"
S_InferenceAccuracy:
  Definition: "% correct for inference questions"
S_EvidenceLink:
  Definition: "can point to text evidence (0/1)"
S_SentenceControl:
  Definition: "grammar + punctuation accuracy under time"
S_CompositionDepth:
  Definition: "scene details + inner thoughts + sensory + motivation"
S_VocabActivation:
  Definition: "uses appropriate vocab/phrases naturally"
S_EmotionInterference:
  Definition: "freeze/avoidance/tears/anger + performance drop"
S_TransferWriting:
  Definition: "can apply technique to new prompt without prompts"

		

3.2 Phase Classifier (English)

			
Classifier: ENGLISH_PHASE_v1.0
Rules:
  P0:
    - Blank page OR panic freeze OR TTS > 8 min
    - OR Comprehension accuracy < 40%
  P1:
    - Can write but shallow OR inconsistent
    - TTM slow OR command words misread
  P2:
    - Stable writing with structure + moderate depth
    - Comprehension accuracy > 65%
  P3:
    - Robust under time, strong depth, high control
    - Comprehension accuracy > 80% with evidence linking

		

4) Repair Protocols (Truncation + Stitching)

4.1 Truncation (Stop the spiral)

			
Truncation: ENGLISH_TRUNCATION_v1.0
Trigger:
  - P0 signs (blank, panic, shutdown)
Actions:
  - Reduce task: 1 paragraph only
  - Provide scaffold: 5-box plan OR sentence stems
  - Force micro-win: 3 correct sentences
  - EmotionOS stabilizer:
      - 30s reset + identity-safe script
Goal:
  - Prevent bind deletion (shame -> avoidance -> writing collapse)

		

4.2 Stitching (Build binds)

			
Stitching: ENGLISH_STITCHING_v1.0
Recipe:
  1) Input (short model paragraph)
  2) Extract (underline 5 techniques)
  3) Imitate (write one paragraph using 2 techniques)
  4) Expand (add 3 sensory + 1 inner thought)
  5) Stress (timed rewrite of weakest paragraph)
PromotionRule:
  - Increase load only when:
      SentenceControl stable AND Depth score rising AND TTS improving

		

5) PSLE Composition Engine (Canonical BTT Version)

This is compatible with your EduKateSG canonical protocol.

			
PSLE_Compo_Engine: BTT_PSLE_COMPO_v1.0
PhasePlan (12–16 weeks):
  Phase1_DepthBuilding:
    - reading input + vocab/phrase bank
    - scene detail drills
  Phase2_StructurePlanning:
    - 5-Box Story Plan (hook, build, twist, climax, resolve)
  Phase3_LoadTraining:
    - timed writing + checklist
    - rewrite weakest paragraph
  Phase4_TransferExam:
    - situational + continuous writing
    - monthly Paper 1 simulation
Diagnostics:
  - DepthLeak
  - StructureLeak
  - GrammarLeak
  - EmotionLeak

		

5-Box Story Plan (Spec)

			
StoryPlan_5Box_v1.0
Box1: Setup (where/when/who + mood)
Box2: Trigger (problem appears)
Box3: Escalation (complication)
Box4: Climax (decision/action)
Box5: Resolution (lesson/change)
RequiredDepthTokens:
  - sensory x3
  - inner thought x2
  - dialogue x1
  - specific action sequence x1

		

6) Comprehension Engine (PSLE + Secondary)

			
ComprehensionEngine: BTT_COMPREHENSION_v1.0
Skills:
  C1: Literal retrieval
  C2: Paraphrase mapping
  C3: Inference
  C4: Author’s purpose/tone (sec)
  C5: Evidence linking
Sensors:
  - TTM (decode speed)
  - InferenceAccuracy
  - EvidenceLink
Repairs:
  - Command word drills
  - Evidence sentence frames:
      "I know this because the text says..."
StressTest:
  - timed mini passage weekly

		

7) VocabularyOS Link (Words → Emotions → Actions)

This is the bridge you asked for earlier: language creates emotion, emotion drives action, action changes outcomes.

			
VocabEmotionAction_Link: BTT_VEA_BRIDGE_v1.0
Rule:
  Weak vocab -> weak ideas -> shallow writing -> shame -> avoidance -> P0 drift
Sensors:
  - VocabActivation low + EmotionInterference high = collapse risk
Repair:
  - PhraseBoostPack (10 phrases/week)
  - 3-sentence daily micro-write
  - 1 paragraph weekly polish

		

8) Lesson SOPs (Z1)

8.1 Writing Lesson SOP

			
LessonSOP_Writing: BTT_ENG_LESSON_WRITE_v1.0
Duration: 60–90 min
Flow:
  - 5 min: micro-diagnose (sentence + 1 question decode)
  - 10 min: 5-box plan
  - 20 min: write 1 paragraph
  - 10 min: add depth tokens
  - 10 min: timed rewrite (weakest paragraph)
  - 5 min: checklist + 1 vocab insertion
Exit:
  - improved TTS or Depth score or SentenceControl

		

8.2 Comprehension Lesson SOP

			
LessonSOP_Compre: BTT_ENG_LESSON_COMP_v1.0
Flow:
  - 5 min: command words drill
  - 15 min: short passage timed
  - 15 min: inference training + evidence linking
  - 10 min: error compression (rewrite answers)
  - 5 min: retest 2 questions

		

9) Parent Panel (English)

			
ParentPanel_English: BTT_PARENT_PANEL_ENG_v1.0
Fields:
  - CurrentPhase
  - MainVoid
  - TTS / TTM
  - ThisWeekPlan (3 actions)
  - WhatToSay (script)
Example:
  CurrentPhase: P1
  MainVoid: VOID_E03 (shallow writing)
  Plan:
    - 10-min daily 3-sentence micro-write
    - 1 paragraph depth upgrade
    - 1 timed rewrite per week
  Script:
    - "We are training depth and control, not chasing perfect."

		

10) Case Template (English)

			
CaseTemplate_English: BTT_CASE_ENG_v1.0
CaseID:
Level:
EntryPhase:
Baseline:
  TTS:
  CompreAcc:
  DepthScore:
  EmotionInterference:
MainVoid:
RepairPlan:
Outcome:
  TTS:
  CompreAcc:
  DepthScore:
  Phase:
FailureTrace:
RepairTrace:

		

Z3 Bukit Timah English Pages (Install Pack)

Create these supporting Z3 dominance pages:

/bukit-timah-english-tuition-composition-repair/
/bukit-timah-psle-english-composition-5-box-plan/
/bukit-timah-english-comprehension-inference-training/
/bukit-timah-exam-blank-page-writing-help/
/bukit-timah-vocabulary-phrase-boost-pack/

Each page includes:

1 Negative Void block
1 Sensor block
1 Case block
Internal links to Student Runtime + EnglishOS

BukitTimahTutor.com · Parent Control Tower v1.0

“What’s going on with my child, and what do we do next?” (Z2 Parent Interface Layer)

Slug: /parent-control-tower-v1-0-student-phase-panel/
Version: BTT_PARENT_TOWER_01
Compatibility: Student Runtime v1.0 + MathOS + EnglishOS + EmotionOS + ERCO

META (Machine-Readable)

			
PageID: BTT_PARENT_TOWER_01
Place:
  CountryISO3: SGP
  Z3: BukitTimah
Audience:
  - Parents (primary)
  - Students (secondary)
LaneSet: [MATH, ENGLISH]
ZoomRange: Z2 (parent dashboard) with Z0–Z1 readouts
Goal:
  - Make the invisible visible (why results drop)
  - Give a simple weekly plan
  - Prevent panic-driven collapse (P0)

		

1) The One Sentence Truth

Most students don’t fail because they’re not smart.

They fail because under exam pressure:

“`yaml id=”btt_parent_truth_01″
CoreFailure:
Speed (TTC) drops + Errors rise + Emotion spikes
=> the system collapses (P0) or drifts (P1)

			
We fix the structure.
---
# 2) What Phase Is Your Child In? (P0–P3)
Use this as a simple checklist.
## P0 — Collapse Risk
Signs:
* blanks / “I don’t know” instantly
* panic, tears, shutdown
* cannot start the question
* writing: blank page
* math: cannot choose method

		

yaml
Phase: P0
Meaning: “Stability is broken under load”
ImmediateAction:

Truncation (reduce load)
Emotion stabilise
rebuild micro wins

			
## P1 — Drift
Signs:
* can do homework but fails tests
* inconsistent results week to week
* “careless mistakes”
* slow, runs out of time
* writing shallow or messy

		

yaml
Phase: P1
Meaning: “Weak binds + slow retrieval”
Action:

Stitch binds
train speed (TTC)
add transfer practice

			
## P2 — Stable
Signs:
* steady grades
* can handle minor surprises
* mistakes decreasing

		

yaml
Phase: P2
Meaning: “Stable under normal variation”
Action:

maintain + targeted upgrades

			
## P3 — Robust
Signs:
* fast, calm, transferable
* can solve unseen variants
* can write clearly under time

		

yaml
Phase: P3
Meaning: “Strong under stress”
Action:

stretch goals + enrichment safely

			
---
# 3) The 6 Most Common Hidden Leaks (Negative Voids)
Parents often see the symptom (bad result), not the cause.
Here are the causes we measure:

yaml
VoidAtlas_Parents: BTT_PARENT_VOID_01
VOID_P01: “Too slow (runs out of time)” -> TTC drift
VOID_P02: “Careless mistakes” -> checking bind weak
VOID_P03: “Understands but cannot do” -> concept->procedure bind weak
VOID_P04: “Cannot transfer to tests” -> transfer bind missing
VOID_P05: “Misreads questions” -> command-word decode weak
VOID_P06: “Panic/blank page” -> emotion interference spike

			
---
# 4) Parent Panel (What You Receive)
This is the simple output we give parents.

yaml
ParentPanel: BTT_PARENT_PANEL_v1.0
Fields:

Phase (P0–P3)
TTC (speed)
MainLeak (VOID code)
WeeklyPlan (3 actions)
NextTestDate
WhatToSay (1 sentence)

### Example (Math)

yaml
ExamplePanel_Math:
Phase: P1
TTC: 34s
MainLeak: VOID_P01 (Too slow)
WeeklyPlan:
– 10-min TTC sprint x4
– 1 drill pack (algebra)
– 1 timed mini set
NextTestDate: Weekly Friday
WhatToSay: “We are training speed and calm, not proving anything.”

### Example (English)

yaml
ExamplePanel_English:
Phase: P1
TTS: 6 min to first paragraph
MainLeak: VOID_P04 (Transfer weak)
WeeklyPlan:
– 5-box plan x3 prompts
– 1 paragraph depth upgrade
– 1 timed rewrite
WhatToSay: “We are training control and depth, not chasing perfection.”

			
---
# 5) Weekly Home Plan (10 Minutes a Day)
Parents need low friction.
## Maths: 10-minute plan

yaml
HomePlan_Math_10min:
Day1: 12 micro-items (one skill)
Day2: 8 mixed-items
Day3: 4 timed items
Day4: error rewrite (correct method + steps)
Day5: mini retest (5 questions)
Rule:

stop if panic spikes
switch to easier micro-items (Truncation)

## English: 10-minute plan

yaml
HomePlan_English_10min:
Daily:
– 3 sentences:
1) action
2) sensory detail
3) inner thought
Weekly:
– 1 paragraph rewrite under time (7 min)
Rule:

technique > length

			
---
# 6) EmotionOS Parent Scripts (Important)
Bad scripts increase collapse.
Good scripts reduce EmotionInterference.

yaml
ParentScripts: BTT_PARENT_SCRIPTS_v1.0
Avoid:

“Why are you so careless?”
“You already learnt this!”
Use:
“We’re training speed, not identity.”
“Let’s do one small step first.”
“We measure progress by TTC and fewer leaks.”
EmergencyReset:
30-second pause
water
one guaranteed-correct question

			
---
# 7) ERCO Scheduling (Why We Don’t Overload)
Parents often want “more worksheets”.
That can worsen P0.
We use ERCO to schedule:

		

yaml
ERCO_ParentView: BTT_PARENT_ERCO_v1.0
FreezeWindow:

exam week
heavy school workload week
SandboxWindow:
lighter weeks
transfer training
Rule:
Operator stability first, Architect exploration second

			
---
# 8) What To Do If Your Child Is P0 (Emergency Protocol)

yaml
P0_EmergencyProtocol: BTT_P0_PARENT_01
Stop:

timed papers immediately
Do:
1-step micro items
3 guaranteed wins
short session (15–20 min)
Then:
tutor rebuild plan
Goal:
return to P1 within 1–2 weeks

			
---
# 9) FAQ Pack (Google Friendly, Parent Friendly)

yaml
FAQ_Blocks: BTT_PARENT_FAQ_v1.0
Q1: “My child understands but fails tests”
A1: “Transfer bind missing + TTC drift. We train variants + speed.”
Q2: “My child is careless”
A2: “Error-monitor bind weak under load. We install check routines.”
Q3: “My child panics”
A3: “Emotion interference triggers P0 collapse. We truncate and rebuild stability.”
Q4: “How fast will results improve?”
A4: “Often 3–8 weeks: TTC drops first, then grades stabilize.”

			
---
# 10) Installation Links (Internal)

yaml
InternalLinks:

/student-runtime-v1-0-z0-z2-cognitive-repair-engine/
/mathematicsos-amath-execution-lattice-v1-0/
/englishos-execution-pack-v1-0-psle-secondary/
/bukit-timah-maths-tuition-lattice-system/
/bukit-timah-a-math-tuition-exam-repair-engine/
“`

BukitTimahTutor.com · Evidence / Case Library v1.0

“Proof Stack” that scales forever (Google-proof, non-cannibalising)

Slug: /case-library-v1-0-proof-stack/
Version: BTT_CASELIB_01
Compatibility: Student Runtime v1.0 + MathOS + EnglishOS + EmotionOS + ERCO + CivOS v1.2

META (Machine-Readable)

			
ModuleID: BTT_CASELIB_01
Place:
  CountryISO3: SGP
  Z3: BukitTimah
LaneSet: [MATH, ENGLISH]
ZoomRange: Z2 (library) with Z0 evidence fields
Goal:
  - Publish repeatable proof without revealing identities
  - Create compounding authority (cases index -> case pages -> method pages)
NonCannibaliseRule:
  - Never edit old cases (append only)
  - Cases reference runtime modules, not replace them

		

1) Case System Architecture (How to publish without breaking anything)

You will have:

			
Architecture: BTT_PROOF_STACK_v1.0
Pages:
  A) Case Library Hub (index)
  B) Case Category Pages (Math / A-Math / English / Comprehension / Panic)
  C) Individual Case Pages (CaseID)
Links:
  - Each case links back to:
      Student Runtime + relevant OS module + relevant Z3 service page
  - Service pages link back to:
      Case Library + 3–6 representative cases

		

This creates a compounding loop.

2) CaseID Standard (Anonymous + structured)

			
CaseID_Standard: BTT_CASEID_v1.0
Format:
  BTT_{LANE}_{LEVEL}_{YYYY}_{NNN}
Examples:
  BTT_MATH_P6_2026_001
  BTT_AMATH_S3_2026_004
  BTT_ENG_P5_2026_002
  BTT_COMP_S2_2026_007

		

No names. No schools. Safe.

3) Required Fields (What every case must contain)

This is the “minimum proof kernel”.

			
CaseSchema: BTT_CASE_SCHEMA_v1.0
Required:
  - CaseID
  - Lane
  - LevelBand
  - EntryPhase (P0–P3)
  - MainVoid (Negative Void code)
  - BaselineSensors (TTC/TTS + ErrorRate + ErrorTypeVector + EmotionInterference)
  - RepairPlan (weeks + packs used)
  - RetestCadence
  - OutcomeSensors
  - PhaseExit
  - FailureModeTrace
  - RepairTrace
Optional:
  - GradeDelta (banded, not exact if you prefer)
  - ParentPanel snapshot (example)

		

4) Case Template (Copy-Paste)

4.1 Universal Template

			
Case:
  CaseID:
  Lane: [MATH|ENGLISH]
  LevelBand: [P4|P5|P6|S1|S2|S3|S4]
  EntryPhase: [P0|P1|P2|P3]
  MainVoid: [VOID_xx]
  Baseline:
    Sensors:
      TTC_or_TTS:
      ErrorRate:
      ErrorTypeVector:
      Transfer:
      EmotionInterference:
    Notes:
      - "Symptom parents saw"
  RepairPlan:
    DurationWeeks:
    TruncationUsed: [Y|N]
    StitchingUsed: [Y|N]
    Packs:
      - PackID:
      - PackID:
    ERCO:
      FreezeWindow:
      SandboxWindow:
  RetestCadence:
    WeeklyMicroTest: Y
    MonthlySimulation: Y
  Outcome:
    Sensors:
      TTC_or_TTS:
      ErrorRate:
      Transfer:
      EmotionInterference:
    PhaseExit: [P1|P2|P3]
    GradeDelta: [optional/banded]
  FailureModeTrace:
    - Z0 leak -> Z1 instability -> Z2 drift -> exam risk
  RepairTrace:
    - Truncation -> Stitching -> Retest -> Phase recovery

		

5) Category Pages (Scaling Index)

Create category pages so the library stays navigable.

			
Categories: BTT_CASE_CATS_v1.0
CAT_01: "Math Speed (TTC) Fix"
CAT_02: "Careless Mistakes Repair"
CAT_03: "Method Confusion / Transfer Repair"
CAT_04: "A-Math Quadratics Recovery"
CAT_05: "A-Math Differentiation Recovery"
CAT_06: "English Composition Depth Upgrade"
CAT_07: "English Comprehension Inference Fix"
CAT_08: "Exam Panic / Blank Page Recovery"

		

Each category page includes:

definition of the void
sensor signature
3–10 linked cases

6) “Proof Without Cannibalising” Rule (Critical)

			
ProofGovernance: BTT_PROOF_GOV_v1.0
Rules:
  - Do not rewrite old cases
  - Add new cases as new pages only
  - Case pages never contain full teaching method (avoid cannibalising OS pages)
  - Cases reference:
      Student Runtime + relevant module + relevant service page
  - Keep each case compact (skimmable)

		

This makes Google treat the site as a living evidence system.

7) Example Cases (Ready to publish)

7.1 Maths Case Example (Speed + Careless)

			
Case:
  CaseID: BTT_MATH_P6_2026_001
  Lane: MATH
  LevelBand: P6
  EntryPhase: P1
  MainVoid: VOID_P01 (TTC drift) + VOID_P02 (Careless)
  Baseline:
    Sensors:
      TTC_or_TTS: "TTC 41s (method selection + 2 steps)"
      ErrorRate: "28%"
      ErrorTypeVector: [ProcedureSlip, Careless, Misread]
      Transfer: "0 (variant breaks)"
      EmotionInterference: "0.2 (low)"
    Notes:
      - "Understands at home, fails timed practice"
  RepairPlan:
    DurationWeeks: 5
    TruncationUsed: N
    StitchingUsed: Y
    Packs:
      - BTT_MATH_T01_ALGEBRA_CORE
      - BTT_MATH_TTC_SPRINT_10MIN
      - BTT_MATH_TRANSFERPACK_VARIANTS_01
    ERCO:
      FreezeWindow: "School exam week"
      SandboxWindow: "Week 3 (transfer)"
  RetestCadence:
    WeeklyMicroTest: Y
    MonthlySimulation: Y
  Outcome:
    Sensors:
      TTC_or_TTS: "TTC 16s"
      ErrorRate: "9%"
      Transfer: "1 (solves variants)"
      EmotionInterference: "0.1"
    PhaseExit: P2
    GradeDelta: "Improved by ~2 bands"
  FailureModeTrace:
    - "Slow retrieval (Z0) -> timed instability (Z1) -> inconsistent results (Z2) -> exam drift"
  RepairTrace:
    - "Stitch core binds -> TTC sprints -> variant training -> retest -> stable P2"

		

7.2 A-Math Case Example (Quadratics Method Confusion)

			
Case:
  CaseID: BTT_AMATH_S3_2026_004
  Lane: MATH
  LevelBand: S3
  EntryPhase: P0
  MainVoid: C01 (Method confusion) + C02 (Algebra shear)
  Baseline:
    Sensors:
      TTC_or_TTS: "TTC 58s on quadratics"
      ErrorRate: "47%"
      ErrorTypeVector: [WrongMethod, ProcedureSlip, SignError]
      Transfer: "0"
      EmotionInterference: "0.55 (moderate)"
    Notes:
      - "Freezes on unfamiliar wordings"
  RepairPlan:
    DurationWeeks: 6
    TruncationUsed: Y
    StitchingUsed: Y
    Packs:
      - BTT_AMATH_T01_ALGEBRA_CORE
      - BTT_AMATH_T07_METHOD_SELECT_PACK
      - BTT_AMATH_TRANSFERPACK_Q_VARIANTS
    ERCO:
      FreezeWindow: "Week 1 (stability)"
      SandboxWindow: "Weeks 3–4 (variants)"
  Outcome:
    Sensors:
      TTC_or_TTS: "TTC 18s"
      ErrorRate: "11%"
      Transfer: "1"
      EmotionInterference: "0.25"
    PhaseExit: P2
  FailureModeTrace:
    - "Pattern brittle (Z0) -> wrong method (Z1) -> panic + avoidance (Z2) -> P0 collapse"
  RepairTrace:
    - "Truncate load -> rebuild core algebra -> stitch method selection -> sandbox variants -> retest -> P2"

		

7.3 English Case Example (Blank Page → Depth)

			
Case:
  CaseID: BTT_ENG_P5_2026_002
  Lane: ENGLISH
  LevelBand: P5
  EntryPhase: P0
  MainVoid: VOID_E06 (panic blank) + VOID_E03 (shallow)
  Baseline:
    Sensors:
      TTC_or_TTS: "TTS 9 min (cannot start)"
      ErrorRate: "NA (no output)"
      Transfer: "0"
      EmotionInterference: "0.8 (high)"
    Notes:
      - "Cries when asked to write"
  RepairPlan:
    DurationWeeks: 8
    TruncationUsed: Y
    StitchingUsed: Y
    Packs:
      - BTT_ENG_5BOX_PLAN_CORE
      - BTT_ENG_3SENTENCE_DAILY
      - BTT_ENG_DEPTH_TOKENS_PACK
      - BTT_ENG_TIMED_REWRITE_PACK
    ERCO:
      FreezeWindow: "Weeks 1–2 (stability)"
      SandboxWindow: "Weeks 5–6 (transfer prompts)"
  Outcome:
    Sensors:
      TTC_or_TTS: "TTS 2.5 min"
      Transfer: "1 (new prompt with plan)"
      EmotionInterference: "0.35"
    PhaseExit: P2
  FailureModeTrace:
    - "Emotion spike (Z0) -> no start (Z1) -> avoidance (Z2) -> P0"
  RepairTrace:
    - "Truncate to 1 paragraph -> micro wins -> 5-box plan -> depth tokens -> timed rewrite -> P2"

		

8) Case Library Hub Layout (Ready-to-publish outline)

			
HubLayout: BTT_CASELIB_HUB_LAYOUT_v1.0
Sections:
  - How to read a case (Phase + Void + Sensors)
  - Categories (CAT_01..CAT_08)
  - Latest cases (10)
  - Representative proofs (top 6)
  - Links to:
      Student Runtime + MathOS + EnglishOS + Parent Control Tower

		

9) Privacy + Ethics Block (Important)

			
PrivacyBlock: BTT_CASELIB_PRIVACY_v1.0
Policy:
  - All cases are anonymised
  - No names, no schools, no identifying details
  - Sensor values shown are representative educational measurements
Purpose:
  - Show method effectiveness without compromising privacy

		

BukitTimahTutor.com · Evidence / Case Library v1.0

“Proof Stack” that scales forever (Google-proof, non-cannibalising)

Slug: /case-library-v1-0-proof-stack/
Version: BTT_CASELIB_01
Compatibility: Student Runtime v1.0 + MathOS + EnglishOS + EmotionOS + ERCO + CivOS v1.2

META (Machine-Readable)

			
ModuleID: BTT_CASELIB_01
Place:
  CountryISO3: SGP
  Z3: BukitTimah
LaneSet: [MATH, ENGLISH]
ZoomRange: Z2 (library) with Z0 evidence fields
Goal:
  - Publish repeatable proof without revealing identities
  - Create compounding authority (cases index -> case pages -> method pages)
NonCannibaliseRule:
  - Never edit old cases (append only)
  - Cases reference runtime modules, not replace them

		

1) Case System Architecture (How to publish without breaking anything)

You will have:

			
Architecture: BTT_PROOF_STACK_v1.0
Pages:
  A) Case Library Hub (index)
  B) Case Category Pages (Math / A-Math / English / Comprehension / Panic)
  C) Individual Case Pages (CaseID)
Links:
  - Each case links back to:
      Student Runtime + relevant OS module + relevant Z3 service page
  - Service pages link back to:
      Case Library + 3–6 representative cases

		

This creates a compounding loop.

2) CaseID Standard (Anonymous + structured)

			
CaseID_Standard: BTT_CASEID_v1.0
Format:
  BTT_{LANE}_{LEVEL}_{YYYY}_{NNN}
Examples:
  BTT_MATH_P6_2026_001
  BTT_AMATH_S3_2026_004
  BTT_ENG_P5_2026_002
  BTT_COMP_S2_2026_007

		

No names. No schools. Safe.

3) Required Fields (What every case must contain)

This is the “minimum proof kernel”.

			
CaseSchema: BTT_CASE_SCHEMA_v1.0
Required:
  - CaseID
  - Lane
  - LevelBand
  - EntryPhase (P0–P3)
  - MainVoid (Negative Void code)
  - BaselineSensors (TTC/TTS + ErrorRate + ErrorTypeVector + EmotionInterference)
  - RepairPlan (weeks + packs used)
  - RetestCadence
  - OutcomeSensors
  - PhaseExit
  - FailureModeTrace
  - RepairTrace
Optional:
  - GradeDelta (banded, not exact if you prefer)
  - ParentPanel snapshot (example)

		

4) Case Template (Copy-Paste)

4.1 Universal Template

			
Case:
  CaseID:
  Lane: [MATH|ENGLISH]
  LevelBand: [P4|P5|P6|S1|S2|S3|S4]
  EntryPhase: [P0|P1|P2|P3]
  MainVoid: [VOID_xx]
  Baseline:
    Sensors:
      TTC_or_TTS:
      ErrorRate:
      ErrorTypeVector:
      Transfer:
      EmotionInterference:
    Notes:
      - "Symptom parents saw"
  RepairPlan:
    DurationWeeks:
    TruncationUsed: [Y|N]
    StitchingUsed: [Y|N]
    Packs:
      - PackID:
      - PackID:
    ERCO:
      FreezeWindow:
      SandboxWindow:
  RetestCadence:
    WeeklyMicroTest: Y
    MonthlySimulation: Y
  Outcome:
    Sensors:
      TTC_or_TTS:
      ErrorRate:
      Transfer:
      EmotionInterference:
    PhaseExit: [P1|P2|P3]
    GradeDelta: [optional/banded]
  FailureModeTrace:
    - Z0 leak -> Z1 instability -> Z2 drift -> exam risk
  RepairTrace:
    - Truncation -> Stitching -> Retest -> Phase recovery

		

5) Category Pages (Scaling Index)

Create category pages so the library stays navigable.

			
Categories: BTT_CASE_CATS_v1.0
CAT_01: "Math Speed (TTC) Fix"
CAT_02: "Careless Mistakes Repair"
CAT_03: "Method Confusion / Transfer Repair"
CAT_04: "A-Math Quadratics Recovery"
CAT_05: "A-Math Differentiation Recovery"
CAT_06: "English Composition Depth Upgrade"
CAT_07: "English Comprehension Inference Fix"
CAT_08: "Exam Panic / Blank Page Recovery"

		

Each category page includes:

definition of the void
sensor signature
3–10 linked cases

6) “Proof Without Cannibalising” Rule (Critical)

			
ProofGovernance: BTT_PROOF_GOV_v1.0
Rules:
  - Do not rewrite old cases
  - Add new cases as new pages only
  - Case pages never contain full teaching method (avoid cannibalising OS pages)
  - Cases reference:
      Student Runtime + relevant module + relevant service page
  - Keep each case compact (skimmable)

		

This makes Google treat the site as a living evidence system.

7) Example Cases (Ready to publish)

7.1 Maths Case Example (Speed + Careless)

			
Case:
  CaseID: BTT_MATH_P6_2026_001
  Lane: MATH
  LevelBand: P6
  EntryPhase: P1
  MainVoid: VOID_P01 (TTC drift) + VOID_P02 (Careless)
  Baseline:
    Sensors:
      TTC_or_TTS: "TTC 41s (method selection + 2 steps)"
      ErrorRate: "28%"
      ErrorTypeVector: [ProcedureSlip, Careless, Misread]
      Transfer: "0 (variant breaks)"
      EmotionInterference: "0.2 (low)"
    Notes:
      - "Understands at home, fails timed practice"
  RepairPlan:
    DurationWeeks: 5
    TruncationUsed: N
    StitchingUsed: Y
    Packs:
      - BTT_MATH_T01_ALGEBRA_CORE
      - BTT_MATH_TTC_SPRINT_10MIN
      - BTT_MATH_TRANSFERPACK_VARIANTS_01
    ERCO:
      FreezeWindow: "School exam week"
      SandboxWindow: "Week 3 (transfer)"
  RetestCadence:
    WeeklyMicroTest: Y
    MonthlySimulation: Y
  Outcome:
    Sensors:
      TTC_or_TTS: "TTC 16s"
      ErrorRate: "9%"
      Transfer: "1 (solves variants)"
      EmotionInterference: "0.1"
    PhaseExit: P2
    GradeDelta: "Improved by ~2 bands"
  FailureModeTrace:
    - "Slow retrieval (Z0) -> timed instability (Z1) -> inconsistent results (Z2) -> exam drift"
  RepairTrace:
    - "Stitch core binds -> TTC sprints -> variant training -> retest -> stable P2"

		

7.2 A-Math Case Example (Quadratics Method Confusion)

			
Case:
  CaseID: BTT_AMATH_S3_2026_004
  Lane: MATH
  LevelBand: S3
  EntryPhase: P0
  MainVoid: C01 (Method confusion) + C02 (Algebra shear)
  Baseline:
    Sensors:
      TTC_or_TTS: "TTC 58s on quadratics"
      ErrorRate: "47%"
      ErrorTypeVector: [WrongMethod, ProcedureSlip, SignError]
      Transfer: "0"
      EmotionInterference: "0.55 (moderate)"
    Notes:
      - "Freezes on unfamiliar wordings"
  RepairPlan:
    DurationWeeks: 6
    TruncationUsed: Y
    StitchingUsed: Y
    Packs:
      - BTT_AMATH_T01_ALGEBRA_CORE
      - BTT_AMATH_T07_METHOD_SELECT_PACK
      - BTT_AMATH_TRANSFERPACK_Q_VARIANTS
    ERCO:
      FreezeWindow: "Week 1 (stability)"
      SandboxWindow: "Weeks 3–4 (variants)"
  Outcome:
    Sensors:
      TTC_or_TTS: "TTC 18s"
      ErrorRate: "11%"
      Transfer: "1"
      EmotionInterference: "0.25"
    PhaseExit: P2
  FailureModeTrace:
    - "Pattern brittle (Z0) -> wrong method (Z1) -> panic + avoidance (Z2) -> P0 collapse"
  RepairTrace:
    - "Truncate load -> rebuild core algebra -> stitch method selection -> sandbox variants -> retest -> P2"

		

7.3 English Case Example (Blank Page → Depth)

			
Case:
  CaseID: BTT_ENG_P5_2026_002
  Lane: ENGLISH
  LevelBand: P5
  EntryPhase: P0
  MainVoid: VOID_E06 (panic blank) + VOID_E03 (shallow)
  Baseline:
    Sensors:
      TTC_or_TTS: "TTS 9 min (cannot start)"
      ErrorRate: "NA (no output)"
      Transfer: "0"
      EmotionInterference: "0.8 (high)"
    Notes:
      - "Cries when asked to write"
  RepairPlan:
    DurationWeeks: 8
    TruncationUsed: Y
    StitchingUsed: Y
    Packs:
      - BTT_ENG_5BOX_PLAN_CORE
      - BTT_ENG_3SENTENCE_DAILY
      - BTT_ENG_DEPTH_TOKENS_PACK
      - BTT_ENG_TIMED_REWRITE_PACK
    ERCO:
      FreezeWindow: "Weeks 1–2 (stability)"
      SandboxWindow: "Weeks 5–6 (transfer prompts)"
  Outcome:
    Sensors:
      TTC_or_TTS: "TTS 2.5 min"
      Transfer: "1 (new prompt with plan)"
      EmotionInterference: "0.35"
    PhaseExit: P2
  FailureModeTrace:
    - "Emotion spike (Z0) -> no start (Z1) -> avoidance (Z2) -> P0"
  RepairTrace:
    - "Truncate to 1 paragraph -> micro wins -> 5-box plan -> depth tokens -> timed rewrite -> P2"

		

8) Case Library Hub Layout (Ready-to-publish outline)

			
HubLayout: BTT_CASELIB_HUB_LAYOUT_v1.0
Sections:
  - How to read a case (Phase + Void + Sensors)
  - Categories (CAT_01..CAT_08)
  - Latest cases (10)
  - Representative proofs (top 6)
  - Links to:
      Student Runtime + MathOS + EnglishOS + Parent Control Tower

		

9) Privacy + Ethics Block (Important)

			
PrivacyBlock: BTT_CASELIB_PRIVACY_v1.0
Policy:
  - All cases are anonymised
  - No names, no schools, no identifying details
  - Sensor values shown are representative educational measurements
Purpose:
  - Show method effectiveness without compromising privacy

		

BukitTimahTutor.com · Service Menu + Intake Protocol v1.0

“Choose the right programme in 2 minutes” (Parent-friendly, System-backed)

Slug: /services-intake-protocol-v1-0/
Version: BTT_SERVICES_INTAKE_01
Compatibility: Student Runtime v1.0 + Parent Control Tower + MathOS + EnglishOS + EmotionOS + ERCO

META (Machine-Readable)

			
PageID: BTT_SERVICES_INTAKE_01
Place:
  CountryISO3: SGP
  Z3: BukitTimah
Audience: Parents + Students
LaneSet: [MATH, ENGLISH]
Goal:
  - Route families to the correct programme quickly
  - Reduce wrong-fit enrolments
  - Convert “symptoms” into a measurable plan (Phase + Void)
Output:
  - Recommended track + next steps

		

1) The Simple Promise

We don’t guess.

We use a short baseline + a clear report:

Phase (P0–P3)
Main leak (Void)
Weekly plan

So you know exactly what is happening and what to do next.

2) Choose Your Track (Service Menu)

A) Primary Maths (P3–P6)

Best for students who:

are slow
make careless mistakes
cannot handle word problems
panic in timed practice

			
Service: BTT_PRIMARY_MATH_v1.0
Includes:
  - baseline timed micro-test
  - TTC training + error-type repair
  - weekly micro-tests
Outcome:
  - faster method selection + fewer mistakes under time

		

B) PSLE English (Composition + Comprehension)

Best for students who:

write shallow stories
cannot start writing (blank page)
grammar collapses under time
comprehension inference is weak

			
Service: BTT_PSLE_ENGLISH_v1.0
Includes:
  - 5-Box Story Plan training
  - depth tokens + phrase activation
  - comprehension inference + evidence linking
Outcome:
  - stable writing under time + higher comprehension accuracy

		

C) Lower Secondary Maths (Sec 1–2)

Best for students who:

“understand in class but fail tests”
are inconsistent week to week
struggle with algebra basics

			
Service: BTT_LOWSEC_MATH_v1.0
Includes:
  - algebra core bind repair
  - transfer training (variants)
  - test simulation cadence
Outcome:
  - stable fundamentals before upper sec jump

		

D) O-Level A-Math (Sec 3–4)

Best for students who:

freeze on unfamiliar questions
cannot choose methods fast enough
lose marks to algebra slips
run out of time in Paper 1 / Paper 2

			
Service: BTT_AMATH_OLEVEL_v1.0
Includes:
  - A-Math Topic Phase Map
  - TTC sprints + method selection training
  - algebra stability repair
  - timed mini-sets + full simulations
Outcome:
  - reliable method selection + speed + transfer

		

E) Exam Panic / Blank Page Recovery (Any level)

Best for students who:

cry, freeze, or shut down during tests
avoid homework
say “I don’t know” immediately

			
Service: BTT_PANIC_RECOVERY_v1.0
Includes:
  - Truncation protocol
  - EmotionOS stabilisers
  - micro-win ladder + confidence rebuild
Outcome:
  - return from P0 to P1/P2 safely

		

3) Intake Protocol (2 Steps)

Step 1 — Baseline (10–20 minutes)

We run a short timed set and record:

speed (TTC / TTS)
error pattern
transfer ability
emotion interference signals

			
Baseline: BTT_BASELINE_v1.0
Outputs:
  - Phase (P0–P3)
  - Main leak (Void code)
  - next-step plan

		

Step 2 — Parent Report (Simple + actionable)

You receive a one-page summary:

			
ParentReport: BTT_PARENT_REPORT_v1.0
Fields:
  - CurrentPhase
  - MainLeak
  - WeeklyPlan (3 actions)
  - RetestDate
  - Expected trajectory (4–8 weeks typical)

		

4) Quick Self-Check (For parents before contacting)

Pick the closest description.

If your child is slow / always runs out of time

→ likely VOID_P01 (TTC drift)

If your child is “careless”

→ likely VOID_P02 (checking bind weak)

If your child understands but fails tests

→ likely VOID_P04 (transfer weak) or VOID_P03 (concept->procedure bind weak)

If your child panics or blanks

→ likely P0 + VOID_P06 (emotion interference)

If your child writes shallow compositions

→ likely VOID_E03 (depth bind missing)

If comprehension inference is weak

→ likely VOID_E04 (inference bind weak)

5) Programme Options (Parent-friendly, system-backed)

			
ProgrammeOptions: BTT_PROGRAMMES_v1.0
Option_01:
  Name: "Stabilise (P0 → P1)"
  Duration: 2–4 weeks
  For: panic, blanking, shutdown
Option_02:
  Name: "Repair (P1 → P2)"
  Duration: 4–8 weeks
  For: slow, careless, inconsistent
Option_03:
  Name: "Upgrade (P2 → P3)"
  Duration: 8–12 weeks
  For: aiming for top performance + robustness

		

6) What You Should Expect (No hype)

Progress is usually:

speed improves (TTC/TTS down)
errors become predictable (same few leaks)
transfer improves (variants stop breaking them)
grades stabilise

			
Trajectory: BTT_EXPECTED_TRAJECTORY_v1.0
Week2: less panic + clearer method selection
Week4: TTC down + fewer slips
Week8: stable test performance (P2)

7) Call-to-Action Blocks (Copy-Paste)

Block A (Short)

We’ll run a short baseline test and give you a clear plan:

Phase (P0–P3)
Main leak
Weekly actions

Block B (For A-Math)

If your child freezes on A-Math, runs out of time, or loses marks to slips, we repair:

method selection speed
algebra stability
transfer under variation

Block C (For English)

If your child writes shallow stories or blanks, we rebuild:

structure (5-box plan)
depth (sensory + inner thought)
control (timed rewrite)

8) Internal Links (Wiring)

			
Links:
  - /parent-control-tower-v1-0-student-phase-panel/
  - /student-runtime-v1-0-z0-z2-cognitive-repair-engine/
  - /case-library-v1-0-proof-stack/
  - /bukit-timah-maths-tuition-lattice-system/
  - /bukit-timah-a-math-tuition-exam-repair-engine/
  - /englishos-execution-pack-v1-0-psle-secondary/
  - /bukit-timah-tuition-system-why-it-works-moat/

		

BukitTimahTutor.com · Homepage Wiring + Site Map v1.0

Authority Flow + Internal Link Architecture (Non-Cannibalising, Compounding)

Version: BTT_SITEMAP_WIRING_01
Goal: make BukitTimahTutor.com a running Education hub where every page strengthens every other page.

0) META (Machine-Readable)

			
ModuleID: BTT_SITEMAP_WIRING_01
Place:
  CountryISO3: SGP
  Z3: BukitTimah
CorePillars:
  - Student Runtime (Z0–Z2 engine)
  - Parent Control Tower (parent interface)
  - Service Pages (Z3 dominance)
  - OS Modules (MathOS / EnglishOS)
  - Proof Stack (Case Library)
Rule:
  - No page is “standalone”
  - Every page links into the loop:
      Method -> Service -> Proof -> Parent -> Method

		

			
This loop is what makes the site *compound*.
---
# 2) Homepage (What it must contain)
Homepage slug: `/`
Homepage job: route visitors to the correct track **without explaining everything**.
## Required Homepage Blocks (in this order)
### Block 1 — Identity (Z3 authority)
* “Bukit Timah Maths & English Tuition”
* short line: “We stabilise exam performance under pressure.”
### Block 2 — Choose Your Track (fast routing)
Buttons:
* Primary Maths
* PSLE English
* Lower Sec Maths
* O-Level A-Math
* Exam Panic / Blank Page Recovery
Link to: **Services + Intake Protocol**
### Block 3 — How it works (3 lines)
* Baseline (10–20 min)
* Report (Phase + main leak)
* 4–8 week repair plan
Link to: **Student Runtime** + **Parent Control Tower**
### Block 4 — Proof (trust)
* 3 anonymised micro case cards
Link to: **Case Library Hub**
### Block 5 — Why it works (moat)
Link to: **Moat Page**
### Block 6 — Contact / booking
Link to your preferred CTA page / WhatsApp / form
---
## Homepage Wiring (Exact link set)

		

yaml id=”home_wiring_v1″
HomepageLinks:
PrimaryCTA:
– /services-intake-protocol-v1-0/
Engines:
– /student-runtime-v1-0-z0-z2-cognitive-repair-engine/
– /parent-control-tower-v1-0-student-phase-panel/
Proof:
– /case-library-v1-0-proof-stack/
Moat:
– /bukit-timah-tuition-system-why-it-works-moat/
Services (Z3):
– /bukit-timah-maths-tuition-lattice-system/
– /bukit-timah-a-math-tuition-exam-repair-engine/
– (add your Bukit Timah English service page when published)

			
---
# 3) Core Navigation Menu (Top bar)
Keep it minimal. 5 items.

yaml id=”nav_v1″
NavMenu:

Services -> /services-intake-protocol-v1-0/
How It Works -> /student-runtime-v1-0-z0-z2-cognitive-repair-engine/
Parents -> /parent-control-tower-v1-0-student-phase-panel/
Proof -> /case-library-v1-0-proof-stack/
About/Contact -> (your existing page)

			
---
# 4) Site Map (Canonical Page List)
## Tier A — Conversion (Z3 local intent)
These are your “money pages”.

yaml id=”tier_a”
TierA_ServicePages:

/bukit-timah-maths-tuition-lattice-system/
/bukit-timah-a-math-tuition-exam-repair-engine/
/bukit-timah-english-tuition-composition-repair/ (publish next)
/services-intake-protocol-v1-0/

## Tier B — Engine (explains mechanism)

yaml id=”tier_b”
TierB_EnginePages:

/student-runtime-v1-0-z0-z2-cognitive-repair-engine/
/parent-control-tower-v1-0-student-phase-panel/
/bukit-timah-tuition-system-why-it-works-moat/

## Tier C — OS Modules (depth authority)

yaml id=”tier_c”
TierC_OSModules:

/mathematicsos-amath-execution-lattice-v1-0/
/englishos-execution-pack-v1-0-psle-secondary/

## Tier D — Proof Stack (compounding trust)

yaml id=”tier_d”
TierD_ProofStack:

/case-library-v1-0-proof-stack/
/case-library-math-speed-fix/ (category)
/case-library-a-math-quadratics-recovery/ (category)
/case-library-english-blank-page-recovery/ (category)
/case/BTT_MATH_P6_2026_001/ (case pages)
/case/BTT_AMATH_S3_2026_004/
/case/BTT_ENG_P5_2026_002/

			
---
# 5) Internal Linking Rules (So pages don’t cannibalise)

yaml id=”link_rules_v1″
LinkRules:
ServicePages:
must_link_to:
– Student Runtime
– Parent Control Tower
– Case Library Hub
should_link_to:
– relevant OS module
OSModules:
must_link_to:
– Student Runtime
– Case Library Hub
should_link_to:
– 1–2 service pages
CasePages:
must_link_to:
– Student Runtime
– relevant OS module
– relevant service page
must_NOT:
– teach full method (avoid cannibalising OS pages)
Parent Control Tower:
must_link_to:
– Services
– Student Runtime
– Proof

			
---
# 6) Footer Wiring (Silent authority)
Footer should include:

yaml id=”footer_v1″
FooterLinks:

Student Runtime
Parent Control Tower
Case Library
Maths Tuition (Bukit Timah)
A-Math Tuition (Bukit Timah)
English Tuition (Bukit Timah)
Services + Intake

			
This quietly increases crawl depth + authority flow.
---
# 7) Publishing Order (Do this sequence)
No need to redo old pages.

yaml id=”publish_order_v1″
PublishOrder:
1) Student Runtime v1.0
2) Parent Control Tower v1.0
3) Services + Intake Protocol v1.0
4) Z3 Service pages (Math, A-Math, English)
5) OS Modules (MathOS, EnglishOS)
6) Case Library Hub
7) 3 Case pages + 3 Category pages
8) Moat page
9) Homepage wiring update

			
---
# 8) The Only Missing Page Now (Critical)
You still need one Z3 conversion page for English:

yaml id=”missing_english_z3″
Missing:

/bukit-timah-english-tuition-composition-repair/
“`

Everything else is already generated.

BukitTimahTutor.com · Bukit Timah English Tuition (Z3 Dominance Page) v1.0

Composition + Comprehension + Exam Stability (Parent-friendly, System-backed)

Slug: /bukit-timah-english-tuition-composition-repair/
Version: BTT_Z3_ENG_01
Compatibility: Student Runtime v1.0 + EnglishOS v1.0 + EmotionOS + Parent Control Tower + ERCO

META (Machine-Readable)

“`yaml id=”btt_z3_eng_meta_01″
PageID: BTT_Z3_ENG_01
Place:
CountryISO3: SGP
Z3: BukitTimah
Lane: ENGLISH
Tracks:

Primary (P3–P6, PSLE focus)
Secondary (Sec 1–4)
PrimaryOutcomes:
Write clearly under time (no blank page)
Stronger composition depth + structure
Higher comprehension accuracy (inference + evidence)
CoreMethod:
Diagnose -> Phase -> Repair -> Stress-Test -> Retest

			
---
# 1) What We Do (Simple)
If your child:
* writes shallow compositions
* struggles to start writing (blank page)
* has weak grammar under time
* comprehension inference is weak
* panics during exams
We don’t guess.
We run a short baseline, identify the main leak, and repair it with a structured plan.
---
# 2) Why English Results Drop (Negative Void Framing)
Parents often see “poor English”.
But there are **specific failure patterns**.

		

yaml id=”btt_z3_eng_voids_01″
CommonVoids:
VOID_E01: “Understands story but cannot write”
VOID_E03: “Writes long but shallow”
VOID_E04: “Comprehension inference weak”
VOID_E05: “Grammar collapses under time”
VOID_E06: “Panic / blank page”
VOID_E07: “Misreads question requirements”

			
Different voids need different repairs.
---
# 3) The Student Runtime for English (Z0–Z2)

yaml id=”btt_z3_eng_flow_01″
Flow:
Z0 (Brain):
– Time-to-Meaning (TTM): how fast they decode the question
– Time-to-Sentence (TTS): how fast they begin writing correctly
– Vocab activation: can they use words naturally
– Emotion interference: panic/shame/freeze
Z1 (Lesson):
– plan -> write -> upgrade depth -> timed rewrite -> retest
Z2 (Program):
– weekly micro-tests
– monthly full simulation
– parent panel report

			
This is how writing becomes stable.
---
# 4) “What Phase Is My Child In?” (P0–P3 for English)

yaml id=”btt_z3_eng_phase_01″
PhaseGuide:
P0 (Collapse risk):
– blank page, shutdown, panic
– cannot start, avoids writing
P1 (Drift):
– inconsistent performance
– shallow writing, weak inference
– grammar errors increase under time
P2 (Stable):
– consistent structure + improving depth
– comprehension accuracy steady
P3 (Robust):
– strong control under time, good transfer to new prompts

			
---
# 5) Composition Tuition (PSLE + Primary)
## The most common PSLE composition problem
Students write… but the story feels empty.
That’s `VOID_E03 (depth bind missing)`.
We fix this systematically.
### Our core engine: 5-Box Story Plan + Depth Tokens

		

yaml id=”btt_z3_eng_compo_engine_01″
CompositionEngine:
Planning:
– 5-Box Story Plan (Setup, Trigger, Escalation, Climax, Resolution)
DepthTokens:
– sensory details x3
– inner thought x2
– dialogue x1
– action sequence x1
LoadTraining:
– timed rewrite of weakest paragraph every week
Outcome:

students can start faster and write deeper with control

			
---
# 6) Comprehension Tuition (Primary + Secondary)
Many students read the passage but still answer wrongly.
That’s not “careless”.
It’s usually:
* weak inference bind
* weak evidence linking
* misread command words

		

yaml id=”btt_z3_eng_comp_engine_01″
ComprehensionEngine:
Skills:
– command-word decode
– inference training
– evidence linking (“text says -> therefore”)
Weekly:
– timed mini passage
– error rewrite (better answers, not just corrections)
Outcome:

higher accuracy + better consistency under time

			
---
# 7) Vocabulary That Actually Transfers (Not Word Lists)
Many students “know” words but never use them.
That is `VOID_E02 (vocab exists but never activates)`.
We solve it via **phrase activation**, not memorisation.

		

yaml id=”btt_z3_eng_vocab_01″
VocabActivationSystem:
Weekly:
– 10 phrase boosts
Daily (10 min):
– 3-sentence micro-write:
1) action
2) sensory detail
3) inner thought
Rule:

vocabulary must appear inside real sentences
Outcome:
words become usable under exam pressure

			
---
# 8) Exam Panic / Blank Page Recovery (English)
If your child shuts down when writing starts, we treat that as P0 stability loss.
We do not push more writing.
We **truncate**, stabilise, then rebuild.

		

yaml id=”btt_z3_eng_panic_01″
PanicProtocol_English:
Trigger:
– blank page, tears, avoidance, freeze
Truncation:
– write 3 correct sentences only
– then 1 paragraph only
Stitching:
– rebuild plan -> paragraph -> timed rewrite
Outcome:

child regains the ability to start and continue

			
---
# 9) What Parents Receive (Simple Report)

yaml id=”btt_z3_eng_parent_panel_01″
ParentPanel_English:

Phase: P?
TTS / TTM numbers
Main leak (Void)
This week plan (3 actions)
Next retest date
What to say (support script)

### Example

yaml id=”btt_z3_eng_parent_example_01″
Example:
Phase: P1
MainLeak: VOID_E03 (shallow writing)
TTS: 5.5 min
Plan:
– 5-box plan x3 prompts
– 1 paragraph depth upgrade
– 1 timed rewrite
Script:
– “We’re training control and depth, not chasing perfect.”

			
---
# 10) Proof (Anonymised Case Example)

yaml id=”btt_z3_eng_case_01″
Case:
CaseID: BTT_ENG_P5_2026_002
EntryPhase: P0
MainVoid: VOID_E06 (blank page) + VOID_E03 (shallow)
Baseline:
TTS: 9 min (cannot start)
EmotionInterference: 0.8
RepairPlan:
8 weeks (truncate -> stitch -> timed rewrite)
Outcome:
TTS: 2.5 min
EmotionInterference: 0.35
PhaseExit: P2

			
More cases live in the Case Library.
---
# 11) Who This Is For (Clear routing)

yaml id=”btt_z3_eng_forwho_01″
BestFor:

PSLE students needing composition + comprehension improvement
Primary students who write shallow or messy
Students who panic / blank page
Secondary students needing inference + evidence skills
NotIdealIf:
student is already stable P3 and wants only enrichment (we can still do upgrade track)

			
---
# 12) Next Step (Intake)

yaml id=”btt_z3_eng_intake_01″
Intake:
Step1: Short baseline (10–20 min)
Step2: Parent report (Phase + main leak + weekly plan)
Step3: 4–8 week repair cycle + retests

			
---
# 13) Internal Links (Wiring)

yaml id=”btt_z3_eng_links_01″
InternalLinks:

/services-intake-protocol-v1-0/
/parent-control-tower-v1-0-student-phase-panel/
/student-runtime-v1-0-z0-z2-cognitive-repair-engine/
/englishos-execution-pack-v1-0-psle-secondary/
/case-library-v1-0-proof-stack/
/bukit-timah-tuition-system-why-it-works-moat/
/bukit-timah-maths-tuition-lattice-system/
/bukit-timah-a-math-tuition-exam-repair-engine/
“`

BukitTimahTutor.com · English Z3 Support Cluster v1.0

4 Local Authority Pages (non-cannibalising, compounding)

Compatibility: BTT_Z3_ENG_01 + EnglishOS v1.0 + Student Runtime v1.0 + Parent Tower + Case Library

Below are four complete publish-ready pages (each can be pasted as its own article).
Each page contains: Negative Void → Sensors → Repair loop → Proof link wiring.

PAGE 1 — PSLE Composition 5-Box Plan (Bukit Timah)

Slug: /bukit-timah-psle-english-composition-5-box-plan/
Version: BTT_Z3_ENG_SUPPORT_5BOX_01

BukitTimahTutor.com · Math Z3 Support Cluster v1.0

4 Local Authority Pages (compounding, non-cannibalising)

Compatibility: MathOS v1.0 + Student Runtime v1.0 + Parent Tower + Case Library + Moat

Each page = Negative Void → Sensors → Repair loop → Proof wiring.

PAGE 1 — “Careless Mistakes” Maths Fix (Bukit Timah)

Slug: /bukit-timah-maths-careless-mistakes-fix/
Version: BTT_Z3_MATH_SUPPORT_CARELESS_01

BukitTimahTutor.com · Z0 Student Diagnostic Form + Scoring Rubric v1.0

Baseline → Phase → Void → RepairPlan (Standardised, repeatable)

Slug: /student-diagnostic-form-scoring-rubric-v1-0/
Version: BTT_DIAG_RUBRIC_01
Compatibility: Student Runtime v1.0 + Parent Tower + MathOS + EnglishOS + EmotionOS + ERCO

META (Machine-Readable)

“`yaml id=”btt_diag_meta_01″
ModuleID: BTT_DIAG_RUBRIC_01
Place: {CountryISO3: SGP, Z3: BukitTimah}
ZoomRange: Z0-Z2
LaneSet: [MATH, ENGLISH]
Purpose:

Standardise diagnosis across tutors/sessions
Turn baseline into a measurable plan in 10–20 minutes
Outputs:
Phase classification (P0–P3)
MainVoid selection
Sensor scores
Recommended track + 4–8 week repair plan

			
---
# 1) Diagnostic Intake Form (Parent + Student)
Use this as the intake questionnaire (copy into your form / WhatsApp template).

yaml id=”btt_diag_intake_01″
IntakeForm:
Student:
LevelBand: [P3|P4|P5|P6|S1|S2|S3|S4]
LaneConcern: [MATH|ENGLISH|BOTH]
UpcomingExamDate: (optional)
ParentObservedSymptoms (tick):
– RunsOutOfTime
– CarelessMistakes
– UnderstandsButFails
– PanicsOrBlanks
– AvoidsHomework
– EnglishShallowWriting
– EnglishCannotStart
– ComprehensionInferenceWeak
– MisreadsQuestions
StudentSelfReport (tick):
– “I get stuck starting”
– “I forget steps”
– “I panic in tests”
– “I don’t know what method to use”
– “I read but don’t understand questions”
LoadContext:
SleepLowRecent: [Y|N]
MultipleTuition: [Y|N]
RecentSchoolStress: [Low|Mid|High]

			
---
# 2) Baseline Test Pack (10–20 minutes)
## 2.1 Maths Baseline (choose by level)

yaml id=”btt_diag_math_baseline_01″
MathBaseline:
Duration: 12-15 min
Sections:
A) MethodSelect Sprint (4 items, timed)
B) Execution Set (4 items, timed)
C) Transfer Variant (2 items, untimed)
Record:
– time to choose method
– first 2 steps correctness
– slip type

### Scoring capture sheet (Math)

## 2.2 English Baseline (PSLE/Secondary)

yaml id=”btt_diag_eng_baseline_01″
EnglishBaseline:
Duration: 15-20 min
Sections:
A) Question Decode (command words) 3 items
B) Mini Comprehension (short passage) 5 questions timed
C) Micro Writing:
– 5-box plan (2 min)
– write 1 paragraph (8 min)
Record:
– TTM (decode speed)
– inference accuracy
– TTS (time to first paragraph)
– depth tokens count

### Scoring capture sheet (English)

			
---
# 3) Sensor Scoring Rubric (Convert to numbers)
## 3.1 Maths Scoring

yaml id=”btt_diag_math_rubric_01″
MathRubric:
S_TTC:
3: < 12s 2: 12-25s 1: 25-60s 0: > 60s
S_MethodSelect:
3: 90-100%
2: 75-89%
1: 50-74%
0: < 50% S_SlipRate: 3: < 10% 2: 10-20% 1: 20-35% 0: > 35%
S_Transfer:
3: solves variant independently
2: solves with light hint
1: needs heavy prompting
0: cannot solve
S_EmotionInterference:
3: none
2: mild hesitation
1: moderate freeze/avoidance
0: panic/blank

## 3.2 English Scoring

yaml id=”btt_diag_eng_rubric_01″
EnglishRubric:
S_TTM:
3: < 20s 2: 20-45s 1: 45-90s 0: > 90s
S_CompreAcc:
3: 80-100% (4-5/5)
2: 60-79% (3/5)
1: 40-59% (2/5)
0: < 40% (0-1/5) S_TTS: 3: < 2 min 2: 2-4 min 1: 4-8 min 0: > 8 min / blank
S_StructureControl:
3: clear plan + coherent paragraph
2: plan exists, paragraph partially coherent
1: weak/no plan, rambling
0: cannot start
S_Depth:
3: 5-7 tokens
2: 3-4 tokens
1: 1-2 tokens
0: 0 tokens
S_EmotionInterference:
3: none
2: mild
1: moderate
0: high (shutdown)

			
---
# 4) Phase Classification (Automatic)
## 4.1 Maths Phase

yaml id=”btt_diag_math_phase_01″
MathPhaseRules:
P0:
– S_EmotionInterference=0 OR PanicBlank occurs
– OR S_MethodSelect=0 with high TTC
P1:
– S_TTC in {0,1} OR S_SlipRate in {0,1} OR S_Transfer in {0,1}
P2:
– S_TTC>=2 AND S_MethodSelect>=2 AND S_SlipRate>=2
P3:
– S_TTC=3 AND S_MethodSelect=3 AND S_Transfer>=2 AND S_SlipRate=3

## 4.2 English Phase

yaml id=”btt_diag_eng_phase_01″
EnglishPhaseRules:
P0:
– S_TTS=0 OR S_EmotionInterference=0
– OR S_CompreAcc=0 with shutdown
P1:
– S_TTS in {1} OR S_Depth in {0,1} OR S_CompreAcc in {1}
P2:
– S_TTS>=2 AND S_StructureControl>=2 AND S_CompreAcc>=2
P3:
– S_TTS=3 AND S_Depth=3 AND S_CompreAcc=3 AND S_TransferWriting strong

			
---
# 5) Main Void Selector (Pick the dominant leak)
## Maths Main Void

yaml id=”btt_diag_void_math_01″
MathVoidSelector:
If S_TTC<=1 -> VOID_P01 (TTC drift / slow)
ElseIf S_SlipRate<=1 -> VOID_P02 (careless / check bind weak)
ElseIf S_MethodSelect<=1 -> C01 (method confusion)
ElseIf S_Transfer<=1 -> VOID_P04 (transfer weak)
Else -> “Upgrade track (P2->P3)”

## English Main Void

yaml id=”btt_diag_void_eng_01″
EnglishVoidSelector:
If S_TTS<=1 AND EmotionInterference<=1 -> VOID_E06 (panic/blank)
ElseIf S_Depth<=1 -> VOID_E03 (shallow writing)
ElseIf CompreAcc<=1 -> VOID_E04 (inference weak)
ElseIf CommandWordAccuracy low -> VOID_E07 (misread requirements)
Else -> “Upgrade track (P2->P3)”

			
---
# 6) Auto-Generate Repair Plan (4–8 weeks)
## Plan Generator (Math)

yaml id=”btt_diag_plan_math_01″
MathPlanGenerator:
If Phase=P0:
Track: Stabilise (2-4 weeks)
Actions:
– Truncation protocol
– micro-items only
– rebuild TTC gradually
If Phase=P1 and MainVoid=VOID_P01:
Track: Repair TTC (4-6 weeks)
Actions:
– TTC sprint 10 min x4/week
– 1 drill pack/week
– 1 timed mini set/week
If Phase=P1 and MainVoid=VOID_P02:
Track: Careless Repair (4-6 weeks)
Actions:
– check routine mandatory
– error rewrite 2 items/session
– fatigue-aware timed sets
If Phase>=P2:
Track: Upgrade (8-12 weeks)
Actions:
– transfer packs + mixed papers + speed polishing

## Plan Generator (English)

yaml id=”btt_diag_plan_eng_01″
EnglishPlanGenerator:
If Phase=P0:
Track: Stabilise Writing (2-4 weeks)
Actions:
– 3-sentence daily micro-write
– 1 paragraph only
– EmotionOS reset scripts
If Phase=P1 and MainVoid=VOID_E03:
Track: Depth Upgrade (6-8 weeks)
Actions:
– 5-box plan x3/week
– depth tokens drill
– weekly timed rewrite
If Phase=P1 and MainVoid=VOID_E04:
Track: Inference Repair (4-6 weeks)
Actions:
– command words drill
– evidence linking frame
– weekly timed mini passage
If Phase>=P2:
Track: Upgrade (8-12 weeks)
Actions:
– transfer prompts + full Paper 1/Paper 2 simulations

			
---
# 7) Parent Report Output (One-page script)
This is the exact template you send.

yaml id=”btt_diag_parent_report_01″
ParentReportTemplate:
StudentLevel:
Lane:
CurrentPhase:
MainLeak:
BaselineNumbers:
– TTC/TTS:
– Accuracy:
– MainErrorTypes:
– EmotionInterference:
Plan_ThisWeek:
– Action1
– Action2
– Action3
RetestDate:
WhatToSay:
– “We’re training speed and stability, not identity.”

			
---
# 8) Case Logging Hook (Proof Stack integration)
Every diagnosis can become a case later.

yaml id=”btt_diag_case_hook_01″
CaseHook:
CreateCaseID:
Save:
– EntryPhase
– MainVoid
– BaselineSensors
After 4-8 weeks:
– log outcomes
– publish anonymised case page
“`

BukitTimahTutor.com · STUDENT RUNTIME v1.0 Pack

META (Machine-Readable)

0) Definition Lock

1) Contract (What this runtime guarantees)

2) Data Model (Nodes, Binds, Weights)

2.1 Student Z0 Graph

2.2 Lesson Z1 Graph

2.3 Program Z2 Graph

3) Sensor Panel (Core)

3.1 Universal Sensors

3.2 Phase Classifier (P0–P3)

4) Negative Void Pack (What we detect + repair)

5) Repair Engine (Truncation + Stitching)

5.1 Truncation (Stop loss)

5.2 Stitching (Regenerate binds)

6) EmotionOS Integration (Z0)

7) MindOS / AVOO Integration (Roles in class)

8) ERCO Integration (Repair Scheduling)

9) Parent Panel (Z2 conversion layer)

10) Minimal Operating Procedure (1 lesson)

11) Failure Mode Trace (Required for every case)

12) Publishable Case Template (for Google + proof)

BukitTimahTutor.com · MathematicsOS

A-Math Execution Lattice v1.0 (Z0–Z2 Repair Engine)

META (Machine-Readable)

0) Definition Lock

1) A-Math Topic Graph (Z2)

2) Z0 Micro-Skill Packs (Per Topic)

2.1 Example: Quadratics (T07)

2.2 Example: Differentiation (T12)

3) Topic Sensor Pack (Per Topic)

Phase Classifier (Topic Level)

4) Collapse Atlas (Negative Void → Repair)

5) Repair Protocols (Topic-Specific)

5.1 Universal Truncation (Exam-Safety)

5.2 Universal Stitching (Bind Regeneration)

6) Drill Packs (Operator) and Transfer Packs (Architect)

6.1 Drill Pack Template (Operator)

6.2 Transfer Pack Template (Architect)

7) Topic Packs (Ready-to-Run)

7.1 T01 Algebra Manipulation Core (Most important)

7.2 T07 Quadratics Full (High mark weight)

7.3 T12 Differentiation Core (Gateway to Applications)

8) Weekly Control Loop (Z2)

9) Parent Panel (A-Math Version)

10) Case Template (A-Math)

11) Publishing Hooks (BTT SEO / Moat)

BukitTimahTutor.com · Z3 Dominance Pack v1.0

Bukit Timah Maths Tuition & A-Math Tuition (Lattice-Structured Local Authority)

PART I — Bukit Timah Maths Tuition (Structured Page)

META (Machine-Readable)

1) What Makes This Different (Structural, Not Marketing)

2) How Students Actually Fail (Negative Void Framing)

Common Collapse Patterns in Bukit Timah Students

3) Student Runtime in Action (Z0–Z2 Flow)

4) Sensor Panel (Parent-Readable Version)

5) Local Proof Layer (Case Format)

6) Why Location Matters (Z3 Authority)

PART II — Bukit Timah A-Math Tuition (Execution Engine Page)

META

1) The Real Reason A-Math Students Collapse

2) A-Math Control Loop (Simple View)

3) Topic Phase Map (Parent Friendly)

4) What Students Experience in Class

5) Competitive Differential (Explicit)

6) Parent Conversion Block (Readable)

PART III — Authority Amplifiers

IV. Installation Map

Strategic Result

BukitTimahTutor.com · EnglishOS Execution Pack v1.0

PSLE + Secondary English (Z0–Z2 Repair Engine)

META (Machine-Readable)

0) Definition Lock (EnglishOS)

1) English Z0 Graph (Cognitive Lattice)

2) English Negative Void Atlas (What Students Lack)

3) Sensor Pack (English)

3.1 Universal English Sensors

3.2 Phase Classifier (English)

4) Repair Protocols (Truncation + Stitching)

4.1 Truncation (Stop the spiral)