VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

SG EducationOS Master Hub v0.2 — Control Tower (Runnable, Not an Essay)

Version: CivOS Unified Spec v1.x
Scope: Singapore (Z0→Z6) + World-instantiable template


1) One-Screen Mission

Input: Student state (Stage × Phase × TTC × Backlog × Goals)
Output: Exact next actions (Weekly Plan) + Simulation schedule + 4w/12w forecast + repair routing
Loop: Run → Measure → Calibrate → Repeat


2) Master Hub Navigation (Zero Dead Ends)

Use this as the top page structure:

2.1 Start Here (Z0)

  • [A] Student Intake (5 min)
  • [B] Output: One-Page Plan (instant)
  • [C] Weekly Check (3 min)
  • [D] Timed Simulation (ExamSim)
  • [E] HGW Forecast (4w / 12w)
  • [F] Backtest / Calibration (rolling)

2.2 Lane Hubs (Z2→Z3)

  • SG-ENGLISH Master Graph
  • SG-MATH Master Graph
  • SG-SCIENCE Master Graph
  • SG-HUMANITIES Master Graph
  • SG-Admissions Directory (all routes/gates)

2.3 Control Panels (Z1→Z4)

  • Tutor/School Operations Panel (Z1–Z2)
  • Singapore City Panel (Z3)
  • Nation Stability Panel (Z4)
  • Futures Map (2026–2036)

2.4 Registry Layer (Z6)

  • Glossary + ID Registry
  • Node Library
  • Registry Packs + Digital Coordination Spec

2.5 Comparative Engine (Z5↔Z5)

  • SG ↔ NYC / LON / TYO / BJS / SEL comparisons

3) Canonical Intake Block (Copy-Paste, Public-Facing)

Paste this block into your “Start Here” page. This is your universal prompt entry gate.

SG-EDU Intake v0.1 (Student / Parent)

Fill in plainly:

Student

  • Age / Level: (K1/K2/P1–P6/S1–S4/JC1–JC2/ITE/Poly)
  • School type: (Mainstream / IP / IB / International / Private)
  • Subject focus: (Eng/Math/Sci/Hum — pick 1–2 priorities)
  • Current results: (grades or last test score)
  • Exam horizon: (PSLE / O-Level / N-Level / A-Level / None yet)
  • Time available: (hrs/week)
  • Tuition: (Yes/No; how many hrs)
  • Parent support: (Low/Med/High)

State Sensors

  • Phase (pick): P0 / P1 / P2 / P3
  • TTC (time-to-core test): 1–2w / 4–6w / 8–12w / 12w+
  • Backlog load: Low / Med / High
  • Stability under timed work: Stable / Shaky / Collapse

Goal

  • Target (optional): e.g., “A1 English”, “IP track stability”, “JC readiness”
  • Career direction (optional): Doctor/Lawyer/Engineer/Designer/Unknown

4) Canonical Output Block (What the system must return)

Every run must return exactly these sections:

Output v0.1

  1. State Summary (Stage×Phase×TTC×Backlog)
  2. Primary Failure Mode (1) + Secondary (optional)
  3. This Week Plan (3–5 actions only)
  4. 4-Week Plan (milestones)
  5. Simulation Schedule (timed tests + thresholds)
  6. HGW Forecast (4w & 12w)
  7. Risk Flags (collapse signatures)
  8. Repair Routing (which node packs to use)

5) Routing Algorithm v0.1 (Deterministic Rules)

5.1 Phase-first gating

  • If P0: stop expanding. Repair foundations only. Reduce scope.
  • If P1: controlled rebuild + short loops + frequent measurement.
  • If P2: scale volume + timed load training + widen topics.
  • If P3: optimise + stretch goals + competition/excellence.

5.2 TTC rule (time-to-core)

  • TTC 1–2w: emergency triage; only highest-leverage nodes.
  • TTC 4–6w: repair + timed load entry.
  • TTC 8–12w: rebuild + transfer training + full simulations.
  • TTC 12w+: deep capacity build; widen lanes safely.

5.3 Backlog rule

  • High backlog: cut new content; clear core nodes first (minimum viable).
  • Low backlog: allow breadth expansion.

5.4 Timed-load rule

  • If timed work collapses: route to ExamSim micro-steps + checklist + rewrite loop.

6) Failure Mode Trace v0.1 (required in every run)

Non-emotive schematic trace:

Example template:

Z0: weak retrieval under time
→ Z1: weekly plan not enforced
→ Z2: timed-load collapse (ExamSim fail)
→ Z3: lane instability (English writing unreliable)
→ Outcome: grade volatility + exam risk
Repair:
Z1 routing + Z2 simulation ladder + fenced fix pack
→ regain P2 stability within TTC window

7) The “3-Minute Weekly Check” (Control Loop)

Run every week, same day:

Inputs

  • What was planned? (3–5 actions)
  • What executed? (%)
  • Timed micro-test result
  • Biggest failure mode observed
  • Next week capacity (hrs)

Outputs

  • Keep / Cut / Replace actions
  • Add one repair node
  • Schedule one simulation

This keeps Phase from drifting.


Start Here:

Start here if you want the full sequence:

Vocabulary OS Series Index:
https://edukatesg.com/vocabulary-os-series-index/

Fence English Learning System: 

eduKateSG Learning Systems: 

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors


Start Here:

Start here if you want the full sequence:

Vocabulary OS Series Index:
https://edukatesg.com/vocabulary-os-series-index/

Fence English Learning System: 

eduKateSG Learning Systems: 

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors