SG Syllabus Master Index Hub v0.1 — Z0–Z6 Control Tower for Primary → Secondary → JC

TITLE: SG Syllabus Master Index Hub v0.1 — Z0–Z6 Control Tower for Primary → Secondary → JC
VERSION: CivOS Unified Spec v1.x
MODE: Almost-Code / LLM-first / WordPress paste-ready
OWNER: eduKateSG Fence Learning Systems
SCOPE: Singapore syllabus as a unified lattice registry (Math, English, Science, Humanities)
GOAL: One hub page that routes learners/parents/tutors/schools using Phase×Zoom + FenceOS + CH/ai
CANONICAL CLAIM:
- A syllabus is not a list. It is a regeneration pipeline.
- This hub is a control tower: it links every subject lattice, the coupling table, the sensor packs,
  and the Fence repair protocols so anyone can detect drift early and recover before collapse.
========================================================
0) HUB IDENTITY (SPEC)
========================================================
System: SG-SYLLABUS-HUB
Alias: SG Syllabus Control Tower
Wrapper: FenceLearningSystems
Primary Spine: EducationOS (Singapore instantiation)
Hub Functions:
- Registry: list all syllabus graphs (subject lattices)
- Router: choose the right repair protocol based on Phase + TTC + Coupling signatures
- Panel: show Z0–Z6 views so users understand “why this matters”
- Standard: enforce stable IDs + versioning across pages
========================================================
1) NAVIGATION: WHAT THIS HUB LINKS TO (v0.1)
========================================================
Core Pages (Graphs):
- SG-MATH Master Graph v0.1 (Primary→Secondary→JC)
- SG-ENGLISH Master Graph v0.1 (Primary→Secondary→JC)
- SG-SCIENCE Master Graph v0.1 (Primary→Secondary→JC)
- SG Cross-Subject Coupling Table v0.1
- (Next) SG-HUMANITIES Master Graph v0.1 (History/Geography/SS)
Core Tool Pages:
- FenceOS (TTC + Buffer + Rate Dominance) — actuation spec
- NIT Sensor v0.1 (English/Humanities) + NIT-S (Science)
- CH/ai Scheduler Hook (weekly routing logic)
- Failure Atlas (common collapse patterns + repair loops)
========================================================
2) Z0–Z6 PANEL (WHY THE SYLLABUS EXISTS AT EACH ZOOM)
========================================================
Z0 (Student):
- Goal: stable output under time pressure (P2/P3)
- Tools: NodeRecords + TransferTests + Fence stop-loss + repair loops
Z1 (Family/Tutor):
- Goal: weekly pipeline stability (buffers, routines, retrieval)
- Tools: low-effort fences + error tagging + CH/ai weekly plan
Z2 (School):
- Goal: cohort progression without silent attrition
- Tools: screening diagnostics + tiered remediation routing + transfer checks
Z3 (Singapore City):
- Goal: pipeline resilience across schools; avoid brittleness pockets
- Tools: subject pipeline health panels + variance monitoring + buffer interventions
Z4 (Nation):
- Goal: preserve HRL regenerative throughput (STEM, governance, economy)
- Tools: education spine reinforcement, role regeneration continuity
Z5 (Civilisation):
- Goal: capability continuity under shocks; maintain RePOC pipelines
- Tools: cross-lane coupling understanding + repair routing
Z6 (Supranational):
- Goal: share coordination standards; reduce global drift cascades
- Tools: stable ontologies + computable syllabus graphs
========================================================
3) P0–P3 ROUTER (WHAT TO DO BASED ON PHASE)
========================================================
Router.Inputs:
- Phase estimate (P0–P3)
- TTC (weeks)
- BN (backlog nodes)
- CouplingRiskScore (from coupling table)
- Key lane sensors (subject-specific)
Router.Outputs:
- RepairRoute (which nodes first)
- TruncationPlan (what to drop now)
- StitchingPlan (what to rebuild first)
- ReTestSchedule (transfer tests)
- Weekly CH/ai plan template
Phase Routing Rules:
If P0:
- Immediate Truncation: reduce scope to survival core
- Rebuild buffer (time + confidence + routine)
- Stitch 1–2 prerequisite nodes only
- Run TT0 (untimed) until stable
If P1:
- Lock meaning layer first (definitions, sentence clarity, mechanism chains)
- Increase variation slowly (TT-V)
- Avoid full-paper overload until stable
If P2:
- Maintain with mixed practice + timed ramps (TT1, TT-M)
- Patch weak nodes quickly (ERC rule)
- Build toward P3 with controlled novelty
If P3:
- High-variation transfer; novel questions; speed+accuracy stability
- Enrichment allowed only if core stability preserved
========================================================
4) CORE SUBJECT REGISTRY (v0.1)
========================================================
Registry.Subjects:
- SG×MATH×Z0×Operator×Graph×SG-MATH-MASTER-v0.1
- SG×ENG×Z0×Operator×Graph×SG-ENG-MASTER-v0.1
- SG×SCI×Z0×Operator×Graph×SG-SCI-MASTER-v0.1
- SG×COUP×Z0×Operator×Graph×SG-COUPLING-v0.1
- SG×HUM×Z0×Operator×Graph×SG-HUM-MASTER-v0.1 (planned)
Per-Subject Default High-Weight Nodes (triage list):
Math Core:
- FRAC-CONCEPT, FRAC-EQUIV, RPP-RATIO, WP-BAR-MODEL, ALG-EXPRESSIONS
English Core:
- READ-COMP-INF, VOC-ACTIVE-100, GRAM-CORE, PARA-CORE, COMP-PLAN-5BOX
Science Core:
- DATA-GRAPHS, PRAC-CORE, PHY-FORCES/MOTION, CHE-PARTICLES/REACTIONS, BIO-CELLS/TRANSPORT
========================================================
5) CROSS-SUBJECT COUPLING ROUTER (v0.1)
========================================================
CouplingRouter.Rule:
- If downstream failure signature matches upstream deficit, repair upstream first.
Examples:
- Physics motion fails + graph meaning wrong → patch MATH GRAPH-LINEAR first
- Math word problems fail + inference weak → patch ENG READ-COMP-INF first
- Science explanations generic + paragraph drift → patch ENG PARA-CORE first
CouplingRouter.Priority:
- Always prioritise VH/H coupling edges when TTC is short.
========================================================
6) UNIVERSAL FENCE RULES (STOP-LOSS) — v0.1
========================================================
Rule-F1 (ERC Stop-Loss):
- If the same error class repeats ≥3 times → isolate and repair immediately.
Rule-F2 (TTC Emergency Mode):
- If TTC < 8 weeks AND BN > 3 nodes → truncate scope to core spines.
Rule-F3 (Transfer Truth):
- If drills succeed but transfer tests fail → treat as false competence (P1 masquerading as P2).
Rule-F4 (NIT Dominance):
- If NIT triggers (English/Humanities/Science explanations) → coherence/mechanism repair before more content.
Rule-F5 (Coupling First):
- Fix upstream lane before blaming downstream subject.
========================================================
7) CH/ai WEEKLY PLAN TEMPLATE (HUB DEFAULT) — v0.1
========================================================
CH/ai.Template.Inputs:
- TTC, HoursPerWeek, Phase, CouplingRiskScore
- Weakest node per subject
- VolatilityIndex (CCA, illness, events)
Default Weekly Allocation (balanced):
- Math: 2 sessions (1 core node repair, 1 mixed/timed transfer)
- English: 2 sessions (1 retrieval+grammar, 1 paragraph/composition)
- Science: 2 sessions (1 mechanism+definitions, 1 data/practical)
- 1 buffer session: catch-up / stitching / re-tests
Emergency TTC Allocation:
- Drop low-weight tasks
- Keep core nodes + one timed transfer test weekly per subject (once stable)
ReTest Schedule:
- Weekly: TT0/TT1 for core nodes
- Biweekly: mixed full-topic tests (only if P2 stable)
- After every repair cycle: re-run transfer test
========================================================
8) FAILURE ATLAS ENTRYPOINTS (HUB)
========================================================
Hub links to:
- “Math: Algebra Brittleness” (Secondary)
- “English: NIT Crossing in Composition”
- “Science: Mechanism Collapse (NIT-S)”
- “Coupling: Repairing the Wrong Subject”
Each atlas entry contains:
- Sensors → Truncation → RepairLoops → StitchPlan → ReTest
========================================================
9) REQUIRED SHORT FAILURE MODE TRACE (CANONICAL)
========================================================
Trace:
Hidden coupling deficits → wrong repairs → backlog grows → TTC shrinks → late fencing →
multi-subject NIT crossings → exam shock → P2→P0 collapse
Fence Repair:
Use hub routing → fix upstream couplings → truncate breadth early → stitch core spines →
timed transfer ramps → stable P2/P3 across subjects
========================================================
END: SG Syllabus Master Index Hub v0.1
========================================================

WORDPRESS PASTE-READY PAGE STRUCTURE
H1: Singapore Syllabus Control Tower (Primary→Secondary→JC) — Fence Learning Systems Hub
H2: What this hub is (registry + router + sensors)
H2: Z0–Z6 Panel: why the syllabus exists beyond exams
H2: P0–P3 Router: what to do at each phase
H2: Subject Lattices (Math / English / Science / Humanities)
H2: Cross-Subject Coupling Table (repair upstream first)
H2: Universal Fence Rules (stop-loss + stitching)
H2: CH/ai Weekly Plan Template (normal + emergency TTC mode)
H2: Failure Atlas entrypoints (common collapse patterns)
H2: Failure Trace + Repair Trace