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.

eduKateSG.CFCS.Syllabus.P3Corridor.v1.0

eduKateSG CFCS Pack v1.0

PackID: eduKateSG.CFCS.Pack.v1.0
Scope: Tuition Centre as Civilisation Flight Control System (CFCS) for EducationOS
Vocabulary: Frozen (Z0–Z6, P0–P3, Drift, Repair, Projection, Threshold)
Install Order: 1 → 7 (below)


1) CFCS Tuition Centre Blueprint v1.0

ID: eduKateSG.CFCS.TuitionCentre.Blueprint.v1.0
Type: Canonical System Spec

Classical Foundation Block

A tuition centre is a supplementary educational institution providing academic support beyond school curriculum.

Civilisation-Grade Definition

An eduKateSG CFCS Tuition Centre is:

A regenerative education control tower that detects capability drift across Z0–Z3 before visible failure and projects stabilised student energy into Z4–Z6 future capability lanes.

Phase Mapping (P0–P3)

PhaseModel:
P0: "Collapse (repeated failure, avoidance, shame loop)"
P1: "Recovery (rebuild concepts, stop loss)"
P2: "Stabilisation (consistent performance)"
P3: "Projection (transfer + independent reasoning under load)"

Z-Level Architecture (Z0–Z6)

ZArchitecture:
Z0: "Student node (concept, errors, timing, transfer, stress)"
Z1: "Family buffer (routine, sleep, device load, friction)"
Z2: "Teacher operator (bandwidth, volatility, SOP stability)"
Z3: "Curriculum routing (sequence, load gradient, backtests)"
Z4: "Standards alignment (exam requirements)"
Z5: "Career corridor (choice breadth + clarity)"
Z6: "Civilisation capability (aggregate choice expansion)"

Threshold Inequality (Core Law)

CoreLaw:
Stable: "(RepairRate >= DriftRate) AND (ProjectionCorridorActive == true)"
CollapseRisk: "DriftRate > RepairRate"
StagnationRisk: "(RepairRate >= DriftRate) AND (ProjectionCorridorActive == false)"

Drift Sensors (Minimum Pack)

Sensors:
Z0:
- ConceptStability
- ErrorClusterCount
- TimedStability
- TransferIndex
- StressSignal
Z1:
- RoutineCompliance
- SleepIndicator
- DeviceLoad
- FrictionSignal
Z3:
- SequenceAlignment
- TopicLag
- BacktestAccuracy

Repair Corridor (Truncation + Stitching)

RepairCorridor:
Truncation:
- "Stop advanced exposure"
- "Remove shame feedback"
- "Rebuild 1-2 core concepts"
Stitching:
- "Gradual load increase"
- "Timed stress simulation"
- "Transfer tasks (new contexts)"

Failure Trace (Mandatory)

FailureTrace:
- "Z1 Routine drops"
- "Z0 fatigue rises"
- "Z3 topic lag increases"
- "Timed stability collapses"
- "P2→P1→P0 if uncorrected"

2) Energy Projection Model v1.0

ID: eduKateSG.CFCS.EnergyProjection.Model.v1.0
Type: Control Metric Spec

Classical Foundation Block

Educational improvement is measured via test performance and progression over time.

Civilisation-Grade Definition

Energy Projection is the growth of stable, transferable capability that expands a learner’s future choice corridors.

Model

Energy:
E = Capability * Stability * Transfer * Time
Capability ~ ConceptStability
Stability ~ TimedStability (performance under load)
Transfer ~ TransferIndex (new contexts)
Time ~ WeeksSustainedInP2Plus (normalized 0-1)

Projection Trigger

ProjectionTrigger:
ProjectionCorridorActive: "(TransferIndex >= T_transfer) AND (CorridorClarity >= T_corridor)"
P3Qualification: "(ConceptStability >= T_concept) AND (TimedStability >= T_timed) AND (TransferIndex >= T_transfer)"

Symmetry Threshold (Civilisation Lens)

Symmetry:
Individual: "1 learner gains local capability"
Cluster: "many learners gain stable capability"
ThresholdCrossing: "capability density causes ecosystem-level projection (system effects)"

3) ChronoHelmAI Scheduling Layer v1.0

ID: eduKateSG.CFCS.ChronoHelmAI.Education.v1.0
Type: Time-Domain Control Layer

Classical Foundation Block

Scheduling allocates time for lessons, practice, and assessments.

Civilisation-Grade Definition

ChronoHelmAI (eduKateSG layer) is:

A time-domain load and recovery regulator that prevents phase collapse and enables sustained P3 projection.

4 Clocks

Clocks:
T1_Daily:
- Sleep check
- Device exposure check
- Micro-revision
T2_Weekly:
- Drift scan (errors, timing variance, routine compliance)
- Repair assignment
T3_Monthly:
- Phase classification (P0–P3)
- Parent briefing
- Curriculum routing adjustment
T4_Annual:
- Corridor mapping update (Z4–Z5)
- Plan for next academic year

Load Regulation Rule

LoadRule:
StableWhen: "Load <= RecoveryCapacity * StabilityIndex"
IfBreachRepeated:
- "Reduce Load"
- "Increase Recovery window"
- "Trigger RepairCorridor"

Failure Trace

FailureTrace:
- "Irregular sleep"
- "Z0 fatigue"
- "Z3 mis-sequencing"
- "Timed failure"
- "Shame cycle"
- "P0 collapse"

4) CFCS Runtime Dashboard v0.1

ID: eduKateSG.CFCS.Runtime.Panel.v0.1
Type: Operator Instrument Panel Spec

Panels

Panels:
Z0_Student:
- ConceptStability
- ErrorClusterCount
- TimedStability
- TransferIndex
- StressSignal
Z1_Family:
- RoutineCompliance
- SleepIndicator
- DeviceLoad
- FrictionSignal
Z2_Teacher:
- BandwidthLoad
- VolatilityIndex
- SOPCompliance
- RecoveryIndicator
Z3_Curriculum:
- SequenceAlignment
- TopicLag
- LoadGradientSmoothness
- BacktestAccuracy
Z4Z6_Projection:
- StandardAlignment
- CorridorBreadth
- CorridorClarity
- ChoiceExpansionProxy

Dashboard Decision Rules

Rules:
- if: "DriftRate > RepairRate"
then: "RepairLoop + ParentNotify + LoadReduce"
- if: "(RepairRate >= DriftRate) AND (ProjectionCorridorActive == false)"
then: "ProjectionLoop + TransferTasks + CorridorMapping"
- if: "P3Qualification == true"
then: "Unlock advanced corridor tasks"

5) CFCS Data Model Schema v0.1

ID: eduKateSG.CFCS.Schema.Education.v0.1
Type: Machine-Readable Records (AI + Runtime)

Record Types

RecordTypes:
StudentRecord:
keys: [StudentID, CohortID, Date]
fields:
Phase: {enum: [P0,P1,P2,P3]}
Z0:
ConceptStability: {float: [0,1]}
ErrorClusterCount: {int: [0,inf]}
TimedStability: {float: [0,1]}
TransferIndex: {float: [0,1]}
StressSignal: {enum: [Low,Med,High]}
FamilyRecord:
keys: [FamilyID, StudentID, Date]
fields:
Z1:
RoutineCompliance: {float: [0,1]}
SleepIndicator: {enum: [Adequate,Low]}
DeviceLoad: {enum: [Low,Med,High]}
FrictionSignal: {enum: [Low,Med,High]}
TeacherRecord:
keys: [TeacherID, Date]
fields:
Z2:
BandwidthLoad: {float: [0,1]}
VolatilityIndex: {enum: [Stable,High]}
SOPCompliance: {enum: [Yes,No]}
RecoveryIndicator: {enum: [Adequate,Low]}
CurriculumRecord:
keys: [CurriculumID, CohortID, Date]
fields:
Z3:
SequenceAlignment: {float: [0,1]}
TopicLag: {enum: [None,Low,High]}
LoadGradientSmoothness: {float: [0,1]}
BacktestAccuracy: {float: [0,1]}
ProjectionRecord:
keys: [StudentID, Date]
fields:
Z4:
StandardAlignment: {float: [0,1]}
Z5:
CorridorBreadth: {float: [0,1]}
CorridorClarity: {float: [0,1]}
Z6:
ChoiceExpansionProxy: {float: [0,1]}

Threshold Constants

Thresholds:
T_concept: 0.80
T_timed: 0.75
T_transfer: 0.70
T_routine: 0.70
T_corridor: 0.60
T_drift_alert: 0.10

Failure Trace

FailureTrace:
- "Z1 routine weakens"
- "Z0 fatigue increases"
- "Z3 topic lag increases"
- "Timed stability drops"
- "Phase drifts downward"

6) Parent Portal Interface Spec v0.1

ID: eduKateSG.CFCS.Interface.ParentPortal.v0.1
Type: Z1 Buffer Regulation Interface

Classical Foundation Block

A parent portal communicates progress and tasks between educator and family.

Civilisation-Grade Definition

The eduKateSG Parent Portal is a buffer-control interface: it prevents parents from becoming drift amplifiers and turns them into stability multipliers.

Pages (Minimum)

Pages:
- Dashboard
- WeeklyActions
- DriftAlerts
- RepairPlan
- ProjectionMap
- Messages
- Boundaries

Dashboard (One Screen Rule)

Dashboard:
Show:
- Phase
- ThisWeek Z0 (ConceptStability, TimedStability, ErrorClusterCount)
- ThisWeek Z1 (RoutineCompliance, SleepIndicator, DeviceLoad)
- One NextStep sentence
DoNotShow:
- rankings
- shame-trigger comparisons

Weekly Actions (Parent SOP)

WeeklyActions:
MustContain:
- "Sleep routine"
- "Device boundary"
- "Homework window"
- "One mistake-review session"
Format:
- checklist (7 days)
- minutes/day budget

Drift Alerts

DriftAlerts:
Types: [RoutineDrop, TimedDrop, ErrorSpike, SleepLow, DeviceHigh]
EachAlertMustContain:
- What happened (neutral)
- Why it matters (1 line)
- What to do (1 action)
- What NOT to do (avoid shame escalation)

Failure Trace

FailureTrace:
- "Parent panic language"
- "Conflict rises"
- "Routine collapses"
- "Avoidance increases"
- "P2→P1→P0 under exam shock"

7) Cohort Capability Density Projection Model v0.1

ID: eduKateSG.CFCS.Model.CohortCapabilityDensity.v0.1
Type: System-Level Projection Verification

Civilisation-Grade Definition

This model estimates whether eduKateSG cohorts have crossed the threshold where outcomes become systemic (lower collapse rate + higher P3 fraction + stronger transfer).

Model

PerStudentEnergyProxy:
E_i = ConceptStability * TimedStability * TransferIndex * WeeksInP2Plus_norm
CohortMetrics:
N: "cohort size"
E_bar: "mean(E_i)"
E_p3: "fraction in P3"
CollapseRate: "fraction entering P0 per term"
CapabilityDensity:
D = E_bar * E_p3 * (1 - CollapseRate)

Decision Threshold

Threshold:
T_cap_density: 0.25 # tune after backtests
Decision:
- if: "D >= T_cap_density"
then: "Projection threshold crossed (system effect present)"
- else: "Strengthen repair + projection loops"

Backtest (Monthly)

Backtest:
Inputs:
- last 4 weeks StudentRecord
- FamilyRecord
- CurriculumRecord
Outputs:
- D (density)
- DriftRate vs RepairRate
- top drift causes
- next scheduling changes (ChronoHelmAI)

eduKateSG Public Authority Stamp Page v1.0

ID: eduKateSG.CFCS.AuthorityStamp.Page.v1.0
Type: WordPress-ready copy (clean, definitive)

H1: eduKateSG CFCS Tuition — Education as a Control Tower
eduKateSG is not a tuition centre that waits for grades to fall.
We operate as a Civilisation Flight Control System (CFCS) for learning:
we detect capability drift early, repair it before collapse, and project students into stable long-horizon performance.
H2: The Core Law
Education collapses when Drift Rate exceeds Repair Rate.
Education stagnates when repair exists but projection corridors are missing.
eduKateSG installs both:
Repair + Projection.
H2: What We Control (Z0–Z3)
Z0 Student: concept stability, error patterns, timed stability, transfer.
Z1 Family: routine, sleep, device load, parent–child friction.
Z2 Teacher: bandwidth protection, low volatility, stable SOP.
Z3 Curriculum: sequencing, load progression, backtests.
H2: How We Prevent Collapse (P0–P3)
P0 collapse: avoidance and repeated failure.
P1 recovery: rebuild core concepts (stop loss).
P2 stabilisation: consistent performance.
P3 projection: independent reasoning + transfer under load.
H2: What Your Child Gains
Stable mastery under stress.
Transfer across topics and contexts.
Clearer future pathways from subject mastery.
More choices — not just better grades.
H2: The System We Use (Install IDs)
- eduKateSG.CFCS.TuitionCentre.Blueprint.v1.0
- eduKateSG.CFCS.EnergyProjection.Model.v1.0
- eduKateSG.CFCS.ChronoHelmAI.Education.v1.0
- eduKateSG.CFCS.Runtime.Panel.v0.1
- eduKateSG.CFCS.Schema.Education.v0.1
- eduKateSG.CFCS.Interface.ParentPortal.v0.1
- eduKateSG.CFCS.Model.CohortCapabilityDensity.v0.1

eduKateSG CFCS Hub Page v1.0

ID: eduKateSG.CFCS.Hub.Page.v1.0
Type: WordPress-ready “Control Tower” landing page (AI-ingestion friendly)
Scope: eduKateSG-only CFCS system + install links (IDs)
Vocabulary: Frozen


Classical Foundation Block

Education support systems typically include school instruction, enrichment, tuition, assessments, and parent involvement. A hub page typically explains services and programmes.

Civilisation-Grade Definition

The eduKateSG CFCS Hub is:

A control-tower index that exposes the full system for detecting learning drift early, repairing before collapse, and projecting stable capability into higher-choice futures.


AI Ingestion Lock

AIIngestionLock:
Site: "eduKateSG"
System: "CFCS (EducationOS control tower)"
Vocabulary: "Frozen (Z0–Z6, P0–P3, Drift, Repair, Projection, Threshold)"
InstallPolicy: "Forward-only versions; no renaming IDs"
CanonicalDiagram: "eduKateSG.CFCS.OnePanel.Diagram.v1.0"
GrammarChecklist: "eduKateSG.CFCS.Grammar.Checklist.v1.0"

H1: eduKateSG CFCS — Education as a Control Tower

eduKateSG is not a tuition centre that waits for grades to fall.

We run an education Civilisation Flight Control System (CFCS):
we detect drift early, repair before collapse, and project stable capability forward.


H2: The Core Law (Threshold Inequality)

CoreLaw:
StableBand: "RepairRate ≥ DriftRate AND ProjectionCorridorActive = true"
CollapseRisk: "DriftRate > RepairRate"
StagnationRisk: "RepairRate ≥ DriftRate AND ProjectionCorridorActive = false"

H2: The One-Panel CFCS Diagram (Paste Block)

(Embed this block exactly as-is.)

[DiagramID: eduKateSG.CFCS.OnePanel.Diagram.v1.0]
CORE LAW: RepairRate ≥ DriftRate AND ProjectionCorridorActive = true
PHASE: P0 Collapse → P1 Recovery → P2 Stabilisation → P3 Projection
Z-LAYERS: Z0 Student | Z1 Family | Z2 Teacher | Z3 Curriculum | Z4 Standards | Z5 Corridors | Z6 Capability
SENSORS: Z0(Concept, Errors, Timed, Transfer, Stress) + Z1(Routine, Sleep, Device, Friction) + Z3(Sequence, Lag, Backtest)
CONTROL: Truncation + Stitching
TIME: ChronoHelmAI (Daily/Weekly/Monthly/Annual)
ENERGY: E = Capability × Stability × Transfer × Time
COHORT: D = mean(E) × frac(P3) × (1 − CollapseRate)

H2: Phase Ladder (P0–P3)

PhaseModel:
P0: "Collapse (avoidance, repeated failure, shame loop)"
P1: "Recovery (rebuild concepts, stop-loss)"
P2: "Stabilisation (consistent performance)"
P3: "Projection (transfer + independent reasoning under load)"

H2: What We Control (Z0–Z3)

Z0 Student Node

  • Concept stability
  • Error pattern detection
  • Timed stability
  • Transfer capability
  • Stress signal

Z1 Family Buffer

  • Routine compliance
  • Sleep stability
  • Device load
  • Parent–child friction

Z2 Teacher Operator

  • Bandwidth protection
  • Low volatility
  • SOP stability
  • Recovery indicator

Z3 Curriculum Routing

  • Sequencing correctness
  • Load progression smoothness
  • Topic lag detection
  • Backtest accuracy

H2: Failure Trace (Neutral, Mandatory)

FailureTrace:
- "Z1 routine drops"
- "Z0 fatigue rises"
- "Z3 topic lag increases"
- "Timed stability collapses"
- "P2→P1→P0 if uncorrected"

H2: Repair Corridor (Truncation + Stitching)

RepairCorridor:
Truncation:
- "Stop advanced exposure"
- "Remove shame feedback"
- "Rebuild 1–2 core concepts"
Stitching:
- "Gradual load increase"
- "Timed stress simulation"
- "Transfer tasks (new contexts)"

H2: Time-Domain Control (ChronoHelmAI)

ChronoHelmAI:
T1_Daily:
- "sleep/device check"
- "micro-revision"
T2_Weekly:
- "drift scan"
- "repair assignment"
T3_Monthly:
- "phase classification"
- "parent briefing"
- "routing adjustment"
T4_Annual:
- "corridor mapping update (Z4–Z5)"

H2: System Modules (Install IDs)

This is the full eduKateSG CFCS install set.

InstallModules:
- eduKateSG.CFCS.TuitionCentre.Blueprint.v1.0
- eduKateSG.CFCS.EnergyProjection.Model.v1.0
- eduKateSG.CFCS.ChronoHelmAI.Education.v1.0
- eduKateSG.CFCS.Runtime.Panel.v0.1
- eduKateSG.CFCS.Schema.Education.v0.1
- eduKateSG.CFCS.Interface.ParentPortal.v0.1
- eduKateSG.CFCS.Model.CohortCapabilityDensity.v0.1
- eduKateSG.CFCS.OnePanel.Diagram.v1.0
- eduKateSG.CFCS.Grammar.Checklist.v1.0
- eduKateSG.CFCS.Hub.Page.v1.0

H2: The Public Promise (Verifiable Only)

We do not promise “guarantees”.

We promise system behaviours that can be verified:

  • Drift is detected early (sensor logs)
  • Repair is applied before collapse (repair corridor records)
  • Stability under load increases (timed stability improves)
  • Transfer improves (transfer index rises)
  • Cohort collapse rate falls over time (cohort model)

H2: Parent-Facing Summary (Short)

Your child improves fastest when:

  • the foundation is repaired early
  • stress stability is trained
  • routines are protected
  • learning transfers beyond one worksheet

eduKateSG runs this as a control system, not as a guessing game.


H2: Internal Link Targets (Suggested eduKateSG URLs)

(Use your preferred slugs; keep the IDs unchanged.)

  • /cfcs/
  • /cfcs/one-panel/
  • /cfcs/chronohelmai/
  • /cfcs/runtime-dashboard/
  • /cfcs/schema/
  • /cfcs/parent-portal/
  • /cfcs/cohort-density-model/
  • /cfcs/blueprint/

Footer Version Lock

VersionLock:
HubPage: "eduKateSG.CFCS.Hub.Page.v1.0"
Rule: "Forward-only updates; do not rename IDs"
Canonical: "Use Grammar Checklist on every CFCS page"

eduKateSG One-Panel CFCS Diagram v1.0

ID: eduKateSG.CFCS.OnePanel.Diagram.v1.0
Type: Text-only master diagram (WordPress-ready)
Goal: One screen → whole system

┌──────────────────────────────────────────────────────────────────────┐
│ eduKateSG CFCS — Education as a Civilisation Flight Control System │
│ (Detect drift early → Repair before collapse → Project stable energy) │
└──────────────────────────────────────────────────────────────────────┘
A) CORE LAW (Threshold Inequality)
Stable Band : RepairRate ≥ DriftRate AND ProjectionCorridorActive = true
Collapse Risk : DriftRate > RepairRate
Stagnation Risk : RepairRate ≥ DriftRate AND ProjectionCorridorActive = false
B) PHASE LADDER (P0–P3)
P0 Collapse → P1 Recovery → P2 Stabilisation → P3 Projection
(avoidance) (rebuild) (consistent) (transfer + independence)
C) Z-LAYER STACK (Z0–Z6)
Z0 Student Node : concept, errors, timing, transfer, stress
Z1 Family Buffer : routine, sleep, device load, friction
Z2 Teacher Operator : bandwidth, volatility, SOP stability
Z3 Curriculum Route : sequence, load gradient, backtests
Z4 Standards : exam alignment
Z5 Corridors : choice breadth + clarity
Z6 Capability : cohort-level projection effects
D) SENSOR PACK (Minimum)
Z0: ConceptStability | ErrorClusterCount | TimedStability | TransferIndex | StressSignal
Z1: RoutineCompliance | SleepIndicator | DeviceLoad | FrictionSignal
Z3: SequenceAlignment | TopicLag | BacktestAccuracy
E) CONTROL LOOPS (Truncation + Stitching)
Truncation (Stop-loss):
- stop advanced exposure
- remove shame feedback
- rebuild 1–2 core concepts
Stitching (Re-entry):
- gradual load increase
- timed stress simulation
- transfer tasks (new contexts)
F) TIME-DOMAIN CONTROL (ChronoHelmAI)
T1 Daily : sleep/device check + micro-revision
T2 Weekly : drift scan + repair assignment
T3 Monthly : phase classification + parent briefing + routing adjustment
T4 Annual : corridor mapping update (Z4–Z5)
G) PROJECTION MODEL (Energy Proxy)
E = Capability × Stability × Transfer × Time
Capability ~ ConceptStability
Stability ~ TimedStability
Transfer ~ TransferIndex
Time ~ Weeks sustained in P2+
H) COHORT THRESHOLD (System Effect)
D = mean(E) × fraction(P3) × (1 − CollapseRate)
If D ≥ T_cap_density → projection threshold crossed (ecosystem uplift)

eduKateSG CFCS Grammar Checklist v1.0

ID: eduKateSG.CFCS.Grammar.Checklist.v1.0
Use: Every eduKateSG CFCS page must pass this checklist (consistency + authority)

1) Structure Lock (Must Appear)

  • [ ] Classical Foundation Block (standard definition first)
  • [ ] Civilisation-Grade Definition (eduKateSG control-tower framing)
  • [ ] P0–P3 mapping (phase ladder)
  • [ ] Threshold inequality (Stable / Collapse / Stagnation)
  • [ ] Failure trace (neutral chain, 4–6 steps)
  • [ ] Repair corridor (Truncation + Stitching)
  • [ ] Sensors list (minimum or expanded)
  • [ ] Time-domain layer (ChronoHelmAI clocks)
  • [ ] Version + ID block (forward-only)

2) Language Lock (Must NOT Appear)

  • [ ] No ranking/leaderboard language
  • [ ] No blame language (“lazy”, “no effort”, “hopeless”)
  • [ ] No vague claims (“guaranteed”, “always”, “everyone”)
  • [ ] No new primitives (reuse frozen vocabulary)

3) Claims Lock (Must Be Verifiable)

  • [ ] Every “improvement claim” maps to a sensor metric
  • [ ] Every “programme feature” maps to a control loop
  • [ ] Every “pathway/career claim” maps to corridor breadth/clarity

4) Threshold Constants Block (Optional but Recommended)

  • [ ] T_concept, T_timed, T_transfer, T_routine, T_corridor, T_drift_alert
  • [ ] T_cap_density (cohort threshold)

5) Mandatory IDs (Referencing)

  • [ ] eduKateSG.CFCS.TuitionCentre.Blueprint.v1.0
  • [ ] eduKateSG.CFCS.EnergyProjection.Model.v1.0
  • [ ] eduKateSG.CFCS.ChronoHelmAI.Education.v1.0
  • [ ] eduKateSG.CFCS.Runtime.Panel.v0.1
  • [ ] eduKateSG.CFCS.Schema.Education.v0.1
  • [ ] eduKateSG.CFCS.Interface.ParentPortal.v0.1
  • [ ] eduKateSG.CFCS.Model.CohortCapabilityDensity.v0.1
  • [ ] eduKateSG.CFCS.OnePanel.Diagram.v1.0
  • [ ] eduKateSG.CFCS.Grammar.Checklist.v1.0

WordPress Insert Snippet (Minimal)

Use this at the top of any page:

Version: eduKateSG CFCS v1.0
This page follows: eduKateSG.CFCS.Grammar.Checklist.v1.0
Master diagram: eduKateSG.CFCS.OnePanel.Diagram.v1.0

eduKateSG CFCS Internal SOP Pack v1.0

ID: eduKateSG.CFCS.SOP.Pack.v1.0
Type: Internal operator playbook (tutors + centre ops)
Scope: How to run CFCS weekly/monthly without drift
Linked System: eduKateSG.CFCS.Schema.Education.v0.1 + Runtime Panel + ChronoHelmAI


Classical Foundation Block

An SOP (Standard Operating Procedure) is a documented method to ensure consistent outcomes across staff and time.

Civilisation-Grade Definition

eduKateSG CFCS SOP is:

The minimal set of repeatable procedures that keeps Drift visible, Repair consistent, and Projection active across all cohorts.


0) Roles (Internal Only)

Roles:
Operator_Tutor:
- "runs lessons"
- "collects Z0 signals"
- "executes repair corridor"
Operator_Admin:
- "maintains schedule + reminders"
- "ensures records are filled"
Oracle_LeadTutor:
- "reviews drift patterns"
- "approves routing changes"
- "runs monthly phase review"
Visionary_Director:
- "sets thresholds"
- "publishes system updates (forward-only)"

1) Install Checklist (Before Running CFCS)

Install:
MustHave:
- eduKateSG.CFCS.Runtime.Panel.v0.1
- eduKateSG.CFCS.Schema.Education.v0.1
- eduKateSG.CFCS.ChronoHelmAI.Education.v1.0
Optional:
- ParentPortal (if already built)

2) Data Entry Rules (Non-Negotiable)

Rule: If it is not recorded, it does not exist for CFCS.

A. After Every Lesson (Tutor)

AfterLesson:
Fill: StudentRecord
MinimumFields:
- Phase (P0–P3)
- ConceptStability (0–1)
- ErrorClusterCount (int)
- TimedStability (0–1) # if timed work done, else leave last value
- TransferIndex (0–1) # if transfer task done, else leave last value
- StressSignal (Low/Med/High)
Notes:
- "One sentence only: the bottleneck"

B. Weekly (Admin or Tutor)

Weekly:
Fill: FamilyRecord (quick parent check-in)
MinimumFields:
- RoutineCompliance (0–1)
- SleepIndicator (Adequate/Low)
- DeviceLoad (Low/Med/High)
- FrictionSignal (Low/Med/High)

C. Weekly (Lead Tutor)

Weekly:
Fill: CurriculumRecord (per cohort)
MinimumFields:
- SequenceAlignment (0–1)
- TopicLag (None/Low/High)
- BacktestAccuracy (0–1)

3) The Weekly Drift Scan (T2 Clock)

ID: eduKateSG.CFCS.SOP.WeeklyDriftScan.v1.0

Inputs

Inputs:
- StudentRecord (last 7 days)
- FamilyRecord (last 7 days)
- CurriculumRecord (last 7 days)

Procedure

Procedure:
Step1: "List students with ErrorClusterCount >= 3"
Step2: "List students with TimedStability drop >= T_drift_alert"
Step3: "List students with RoutineCompliance < T_routine"
Step4: "Mark each as CollapseRisk or StagnationRisk using CoreLaw"

Output (One Page)

Output:
DriftList:
- StudentID
- RiskType: [CollapseRisk, StagnationRisk]
- LikelyCause: [Z0, Z1, Z3]
- NextAction: [RepairLoop, ProjectionLoop, LoadReduce]

Trigger Rules (Use Thresholds)

Triggers:
- if: "RoutineCompliance < T_routine"
then: "RoutineReset (Z1) + LoadReduce (Z0)"
- if: "TimedStability drop >= T_drift_alert"
then: "RepairLoop (Z0) + SequenceCheck (Z3)"
- if: "(RepairRate >= DriftRate) AND (ProjectionCorridorActive == false)"
then: "ProjectionLoop (transfer tasks) + corridor mapping"

4) Repair Loop SOP (Truncation + Stitching)

ID: eduKateSG.CFCS.SOP.RepairLoop.v1.0

When to Trigger

When:
- "DriftRate > RepairRate"
- "Repeated error clusters"
- "Timed stability collapse"
- "Avoidance signals"

Truncation (Stop-Loss)

Truncation:
- "Stop advanced worksheets"
- "Reduce volume"
- "Rebuild 1 core concept"
- "Remove shame feedback (neutral language only)"

Stitching (Re-entry)

Stitching:
- "Short timed sets"
- "Gradual load increase"
- "Transfer task (new context)"
- "Micro-backtest next lesson"

Exit Condition

Exit:
- "ConceptStability >= T_concept"
- "ErrorClusterCount <= 1"
- "TimedStability >= T_timed (2 sessions in a row)"

5) Projection Loop SOP (Prevent Stagnation)

ID: eduKateSG.CFCS.SOP.ProjectionLoop.v1.0

When to Trigger

When:
- "(RepairRate >= DriftRate) AND (ProjectionCorridorActive == false)"
- "Student stable but stuck (P2 ceiling)"

Actions

ProjectionActions:
- "Assign 1 transfer task per week (same skill, different context)"
- "Require explanation in words (English as reasoning lock)"
- "Introduce mixed-topic set (interleaving)"
- "CorridorMapping mini-chat (2 minutes): why this expands choice"

Exit Condition

Exit:
- "TransferIndex >= T_transfer"
- "CorridorClarity >= T_corridor"
- "Phase qualifies for P3"

6) Parent Briefing SOP (T3 Monthly)

ID: eduKateSG.CFCS.SOP.ParentBriefing.Monthly.v1.0

Rule: One-page, neutral, actionable

BriefingFormat:
MustInclude:
- Current Phase (P0–P3)
- 1 Drift signal (if any)
- 1 Repair action (this month)
- 1 Routine instruction (sleep/device/homework window)
- 1 "What NOT to do" (avoid shame escalation)
MustNotInclude:
- ranking
- comparisons
- blame

Trigger Parent Briefing Early (Out-of-Cycle)

EarlyTrigger:
- "RoutineCompliance < T_routine for 2 weeks"
- "TimedStability collapse persists 2 sessions"
- "FrictionSignal = High"

7) Monthly Phase Review SOP (T3 Clock)

ID: eduKateSG.CFCS.SOP.MonthlyPhaseReview.v1.0

Inputs

Inputs:
- StudentRecord (last 4 weeks)
- FamilyRecord (last 4 weeks)
- CurriculumRecord (last 4 weeks)
- Cohort model D (density)

Outputs

Outputs:
- Phase distribution (P0/P1/P2/P3)
- Cohort density D
- Top 3 drift causes
- ChronoHelmAI schedule changes (next month)

Decision Rules

Decisions:
- if: "D < T_cap_density"
then: "Increase repair bandwidth + strengthen Z1 routines + add transfer cadence"
- if: "CollapseRate rising"
then: "Reduce load spikes + add recovery windows"
- if: "E_p3 low"
then: "ProjectionLoop emphasis (transfer + explanation)"

8) Tutor Lesson Template (CFCS-Style)

ID: eduKateSG.CFCS.SOP.LessonTemplate.v1.0

LessonTemplate:
1_Warmup (3-5 min):
- "quick diagnostic"
2_Core (15-25 min):
- "concept rebuild OR core practice"
3_Timed (8-12 min):
- "short timed set"
4_Transfer (5-8 min):
- "same skill, new context"
5_Close (2 min):
- "one sentence: what changed"
- "record StudentRecord fields"

9) Mandatory Failure Trace (Ops)

ID: eduKateSG.CFCS.SOP.FailureTrace.v1.0

FailureTrace:
- "Records not updated"
- "Drift becomes invisible"
- "Repair becomes late"
- "Collapse appears sudden"
- "Parents panic"
- "Outcomes become noisy"

10) Version Lock

VersionLock:
PackID: "eduKateSG.CFCS.SOP.Pack.v1.0"
Policy:
- "Forward-only updates"
- "Do not rename IDs"
- "Every SOP references Schema + CoreLaw"

eduKateSG CFCS Templates Pack v1.0

ID: eduKateSG.CFCS.Templates.Pack.v1.0
Type: Copy/paste operational forms (WordPress/internal docs/Notion/Sheets)
Aligned To: eduKateSG.CFCS.Schema.Education.v0.1 + CoreLaw + ChronoHelmAI


Template 1 — StudentRecord Form (After Each Lesson)

ID: eduKateSG.CFCS.Template.StudentRecord.v1.0
Use: Tutor fills in ≤ 60 seconds

StudentRecord:
StudentID: ""
CohortID: ""
Date: "YYYY-MM-DD"
Subject: "" # Math / English / Science (optional)
Phase: "P0|P1|P2|P3"
Z0:
ConceptStability: 0.00 # 0.00–1.00
ErrorClusterCount: 0 # integer
TimedStability: 0.00 # 0.00–1.00 (use last value if not tested)
TransferIndex: 0.00 # 0.00–1.00 (use last value if not tested)
StressSignal: "Low|Med|High"
Bottleneck_OneSentence: ""
NextAction_OneSentence: "" # RepairLoop / ProjectionLoop / LoadReduce / Maintain

Marking rule (fast guide):

QuickRubric:
ConceptStability:
1.00: "explains correctly + solves variations"
0.80: "mostly correct, minor prompting"
0.60: "knows steps but not why"
0.40: "confused, guesses"
TimedStability:
0.80+: "stable under timed load"
0.60–0.79: "some time pressure errors"
<0.60: "collapses under time"
TransferIndex:
0.80+: "new context OK"
0.60–0.79: "needs cues"
<0.60: "cannot transfer"

Template 2 — Family Check-In Script (Weekly, 90 seconds)

ID: eduKateSG.CFCS.Template.FamilyRecord.v1.0
Use: Admin or tutor message / quick call

FamilyRecord:
FamilyID: ""
StudentID: ""
Date: "YYYY-MM-DD"
Z1:
RoutineCompliance: 0.00 # 0.00–1.00 (7 days adherence / 7)
SleepIndicator: "Adequate|Low"
DeviceLoad: "Low|Med|High"
FrictionSignal: "Low|Med|High"
ParentNotes_OneSentence: ""
TutorResponse_OneSentence: ""

Script (copy/paste):

Hi! Quick 60-second check so we can keep learning stable:
1) Sleep this week: Adequate or Low?
2) Device time: Low / Medium / High?
3) Homework routine: how many days out of 7 did it happen as planned?
4) Any friction at home when studying: Low / Medium / High?
Reply in 4 lines is enough.

Template 3 — Weekly Drift Scan Worksheet (T2)

ID: eduKateSG.CFCS.Template.WeeklyDriftScan.v1.0
Use: Lead tutor every week (one page output)

Inputs

  • StudentRecord (last 7 days)
  • FamilyRecord (last 7 days)
  • CurriculumRecord (last 7 days)
WeeklyDriftScan:
WeekOf: "YYYY-MM-DD"
CohortID: ""
Thresholds:
T_concept: 0.80
T_timed: 0.75
T_transfer: 0.70
T_routine: 0.70
T_drift_alert: 0.10
Flags:
- name: "ErrorClusterSpike"
condition: "ErrorClusterCount >= 3"
- name: "TimedDrop"
condition: "TimedStability drop >= T_drift_alert"
- name: "RoutineDrop"
condition: "RoutineCompliance < T_routine"
- name: "Stagnation"
condition: "(ConceptStability >= T_concept) AND (TimedStability >= T_timed) AND (TransferIndex < T_transfer)"
DriftList:
- StudentID: ""
RiskType: "CollapseRisk|StagnationRisk"
LikelyLayer: "Z0|Z1|Z3"
Trigger: "ErrorClusterSpike|TimedDrop|RoutineDrop|Stagnation"
Action: "RepairLoop|ProjectionLoop|LoadReduce"
Owner: "TutorName"
DueBy: "YYYY-MM-DD"

Risk classification (CoreLaw):

CoreLawClassifier:
CollapseRisk: "DriftRate > RepairRate OR repeated flags 2 weeks"
StagnationRisk: "Stable but TransferIndex below threshold"

Template 4 — Monthly Parent Briefing (T3)

ID: eduKateSG.CFCS.Template.ParentBriefing.Monthly.v1.0
Use: One page, neutral, actionable

Title: Monthly Learning Stability Briefing (CFCS)
Student: [Name / ID]
Month: [Month YYYY]
Current Phase: [P0 / P1 / P2 / P3]
1) What’s stable now (1 line)
- [Example: Core concept accuracy improved; confidence is higher.]
2) Drift signal (if any) — neutral (1 line)
- [Example: Timed work drops when tired / routine inconsistent.]
3) Repair action for this month (1 action)
- [Example: RepairLoop on fractions basics + short timed sets.]
4) Parent routine instruction (1 instruction)
- [Example: Fixed 30-min homework window 5 days/week + sleep before 10:30pm.]
5) What NOT to do (avoid shame escalation) (1 line)
- [Example: Avoid comparing to others; focus on the routine and the next step.]
Next session focus: [one sentence]

Early trigger note (include internally):

EarlyTrigger:
- RoutineCompliance < 0.70 for 2 weeks
- TimedStability collapse persists 2 sessions
- FrictionSignal = High

Template 5 — Monthly Phase Review Template (T3)

ID: eduKateSG.CFCS.Template.MonthlyPhaseReview.v1.0
Use: Director/lead tutor; decides next month’s routing + schedule changes

MonthlyPhaseReview:
Month: "YYYY-MM"
CohortID: ""
PhaseDistribution:
P0: 0
P1: 0
P2: 0
P3: 0
CohortModel:
E_bar: 0.00
E_p3: 0.00
CollapseRate: 0.00
D: 0.00
T_cap_density: 0.25
TopDriftCauses:
- "Z0: "
- "Z1: "
- "Z3: "
Decisions:
- If_D_below_threshold: "Increase repair bandwidth + strengthen routine + add transfer cadence"
- If_CollapseRate_rising: "Reduce load spikes + add recovery windows"
- If_E_p3_low: "Run ProjectionLoop emphasis"
ChronoHelmAI_ScheduleChanges_NextMonth:
- "T1 daily: "
- "T2 weekly: "
- "T3 monthly: "

Template 6 — CurriculumRecord (Weekly, Cohort-Level)

ID: eduKateSG.CFCS.Template.CurriculumRecord.v1.0
Use: Lead tutor weekly

CurriculumRecord:
CurriculumID: ""
CohortID: ""
Date: "YYYY-MM-DD"
Z3:
SequenceAlignment: 0.00 # 0.00–1.00
TopicLag: "None|Low|High"
LoadGradientSmoothness: 0.00 # 0.00–1.00
BacktestAccuracy: 0.00 # 0.00–1.00
RoutingChange_OneSentence: ""

Template 7 — Tutor Lesson Note (CFCS Lesson Template)

ID: eduKateSG.CFCS.Template.LessonTemplate.v1.0
Use: Ensures every lesson includes repair + stability + transfer

1) Warmup (3–5 min): quick diagnostic
2) Core (15–25 min): rebuild concept OR core practice
3) Timed (8–12 min): short timed set
4) Transfer (5–8 min): same skill, new context
5) Close (2 min): one-sentence bottleneck + record StudentRecord

Version Lock

VersionLock:
PackID: "eduKateSG.CFCS.Templates.Pack.v1.0"
Policy:
- "Forward-only updates"
- "No renaming IDs"
- "Templates must remain compatible with Schema v0.1"

eduKateSG CFCS Audit & QA Page v1.0

ID: eduKateSG.CFCS.QA.Audit.v1.0
Type: Internal quality assurance + audit protocol
Goal: Prevent “silent drift” in the centre itself (staff drift → system drift)


Classical Foundation Block

Quality assurance checks whether procedures are followed and whether outcomes are consistent over time.

Civilisation-Grade Definition

CFCS QA is:

A control-layer audit that ensures drift detection is actually happening, repair is being applied on time, and projection is not silently dying into a P2 ceiling.


1) CFCS Self-Core Law (Centre-Level)

The centre itself has drift.

CentreCoreLaw:
StableBand: "RecordCompleteness high AND RepairAppliedOnTime AND ProjectionCadence present"
CollapseRisk: "Records missing OR repair late for 2+ weeks"
StagnationRisk: "records present but Transfer/Projection absent (P2 ceiling across cohorts)"

2) Weekly QA Checklist (15 minutes)

ID: eduKateSG.CFCS.QA.Weekly.v1.0
Run by: Lead tutor / director (every week)

A. Record Completeness (Non-negotiable)

WeeklyQA:
Check:
- "StudentRecord exists for each student with ≥1 lesson"
- "FamilyRecord exists (weekly) for flagged students OR at least cohort sample"
- "CurriculumRecord exists per cohort"
PassCondition:
StudentRecordCoverage >= 0.95
CurriculumRecordCoverage = 1.00

B. Drift Visibility (Was drift detected?)

DriftVisibility:
MustHave:
- "A DriftList exists (Weekly Drift Scan output)"
- "At least one risk classification when signals show it"
FailIf:
- "No DriftList for 2 consecutive weeks"

C. Repair Timeliness (Was repair applied?)

RepairTimeliness:
ForEachStudentInDriftList:
MustHave:
- "RepairLoop triggered within 7 days"
- "NextAction recorded in StudentRecord"
FailIf:
- "Same error cluster persists 2 weeks without repair plan"

D. Projection Cadence (Did transfer happen?)

ProjectionCadence:
Check:
- "TransferIndex updated at least bi-weekly per active student"
FailIf:
- "TransferIndex never updated for a month"
- "Students stuck at P2 with stable concept/timed but low transfer"

E. Parent Communication Hygiene

ParentHygiene:
Sample 5 messages:
Must:
- "neutral"
- "1 action"
- "1 do-not-do"
MustNot:
- "blame"
- "comparisons"
- "panic framing"

Weekly QA Output (One Page)

WeeklyQAOutput:
WeekOf: "YYYY-MM-DD"
Coverage:
StudentRecord: 0.00
FamilyRecord: 0.00
CurriculumRecord: 0.00
DriftListCount: 0
RepairTriggeredCount: 0
ProjectionUpdatedCount: 0
FailFlags: []
FixActionsNextWeek: []

3) Monthly Audit (45 minutes)

ID: eduKateSG.CFCS.QA.MonthlyAudit.v1.0
Run by: Director / lead tutor (monthly)

A. Phase Distribution Integrity

PhaseAudit:
Check:
- "Phase labels used consistently"
- "No 'everything is P2' bias"
RedFlag:
- "P0 = 0 always AND P3 = 0 always" # indicates labeling drift or missing signals

B. Cohort Model Audit

Use: eduKateSG.CFCS.Model.CohortCapabilityDensity.v0.1

CohortAudit:
Compute:
- D
- CollapseRate
- E_p3
RedFlags:
- "CollapseRate rising 2 months"
- "E_p3 stagnant 2 months"
- "D below threshold 2 months"

C. Routing Audit (Z3)

RoutingAudit:
Check:
- "TopicLag High repeated"
- "BacktestAccuracy not improving"
ActionIfFail:
- "Adjust sequence"
- "Reduce load gradient"
- "Insert repair week"

D. Teacher Bandwidth Audit (Z2)

TeacherAudit:
RedFlags:
- "BandwidthLoad > 0.85 sustained"
- "VolatilityIndex High recurring"
- "SOPCompliance No recurring"
Actions:
- "reduce teaching load"
- "increase recovery windows"
- "retrain with onboarding exercises"

Monthly Audit Output

MonthlyAuditOutput:
Month: "YYYY-MM"
PhaseDistribution: {P0:0, P1:0, P2:0, P3:0}
CohortMetrics: {D:0.00, CollapseRate:0.00, E_p3:0.00}
RoutingStatus: {TopicLag:"", BacktestAccuracy:0.00}
TeacherStatus: {BandwidthLoad:0.00, SOPCompliance:""}
RedFlags: []
ChangesNextMonth:
ChronoHelmAI:
- "T1 daily: "
- "T2 weekly: "
- "T3 monthly: "

4) What To Delete / Fix When Drift Is Rising

ID: eduKateSG.CFCS.QA.FixPlaybook.v1.0

A. Delete (Stop Doing Immediately)

StopDoing:
- "random extra worksheets when student is in RepairLoop"
- "late-night homework pushes (sleep collapse amplifier)"
- "comparing student to classmates/siblings"
- "changing curriculum sequence every week (routing turbulence)"

B. Fix (Install These Behaviours)

FixNow:
- "restore record completeness to ≥95%"
- "force weekly drift scan"
- "trigger repair within 7 days"
- "restore transfer cadence (weekly/bi-weekly)"
- "reduce load spikes near exams (insert recovery window)"

C. Emergency Stop-Loss (If many students drifting)

EmergencyStopLoss:
TriggerWhen:
- "Cohort CollapseRate rises sharply"
- "TimedStability drops across cohort"
Actions:
- "1 week repair-only (no new topics)"
- "short timed sets only"
- "parent routine reset message"
- "routing adjustment after backtest"

5) Mandatory Failure Trace (Centre-Level)

FailureTrace:
- "Records missing"
- "Drift invisible"
- "Repair late"
- "Parents panic"
- "Teacher overload increases volatility"
- "Cohort outcomes become noisy"

6) Version Lock

VersionLock:
PageID: "eduKateSG.CFCS.QA.Audit.v1.0"
Policy:
- "Forward-only updates"
- "No renaming IDs"
- "QA must remain compatible with Schema v0.1"

Now we move from tuition centre control to full life-corridor syllabus design.

If eduKateSG were to design a Phase-3 corridor from Age 1 → University → Career, what subjects are required to produce civilisation-grade capability?

This is no longer about exams.

This is about interstellar-core civilisation readiness — meaning:

  • Stable under load
  • Transfer across domains
  • High corridor breadth
  • Low collapse rate
  • Long time horizon coordination

We design from infancy → adulthood.

Compressed. Structured. Connected.


eduKateSG Phase-3 Corridor Syllabus v1.0

ID: eduKateSG.CFCS.Syllabus.P3Corridor.v1.0
Scope: Age 1 → University → Career
Goal: Civilisation-grade projection (Z6 capability)


I. The Core Law of Syllabus Design

A syllabus produces civilisation-grade output when:

CapabilityDepth ↑
AND
TransferAcrossDomains ↑
AND
StabilityUnderLoad ↑
AND
TimeHorizonCoordination ↑

If one missing → collapse or stagnation.


II. The 8 Pillar Subjects (Non-Negotiable)

These are the civilisation-grade kernel lanes.

KernelSubjects:
1. Language (Reading + Writing + Explanation)
2. Mathematics (Structure + Abstraction)
3. Logic & Reasoning
4. Physical Systems (Physics + Engineering Thinking)
5. Biological Systems (Life + Health)
6. Energy & Resources (Energy systems + sustainability)
7. Coordination Systems (History + Governance + Economics)
8. Emotional Regulation & Decision Stability

Remove any one → long-horizon collapse.


III. Age-Based Corridor Design

We map by developmental phase.


Stage 1 — Age 1–5 (Pre-Symbolic Foundation)

Primary Goal:

Build cognitive bandwidth + emotional regulation.

Subjects (Integrated, not separate):

Ages1to5:
Language:
- rich spoken vocabulary
- story comprehension
- narrative sequencing
Pattern Recognition:
- shapes
- symmetry
- counting through play
Emotional Regulation:
- naming emotions
- delay tolerance
Physical Coordination:
- fine motor
- gross motor
Curiosity Training:
- "why" questions encouraged

Critical Connections:

Language ↔ Emotion
Pattern ↔ Early math
Story ↔ Memory

If language weak here → collapse in abstract reasoning later.


Stage 2 — Age 6–12 (Primary School)

Goal:

Build structural foundation + load tolerance.

Core Subjects:

Ages6to12:
Language:
- reading comprehension
- structured writing
- vocabulary expansion
Mathematics:
- arithmetic
- fractions
- ratios
- early algebra patterns
Science:
- observation
- basic physics concepts
History:
- timelines
- cause-effect reasoning
Emotional Regulation:
- frustration tolerance
- time management
Physical Health:
- sleep routines

Connection Points:

Math ↔ Pattern recognition from infancy
Language ↔ Logic expression
History ↔ Causal reasoning
Emotion ↔ Stress stability

This stage determines Phase stability for adolescence.


Stage 3 — Age 13–16 (Secondary)

Goal:

Abstraction + Identity Stabilisation + Multi-lane exposure.

Ages13to16:
Advanced Mathematics:
- algebra
- functions
- geometry
Language:
- argumentative writing
- analytical comprehension
Sciences:
- physics
- chemistry
- biology
Coding / Computational Thinking
Logic & Debate
History + Economics (basic systems thinking)
Emotional Regulation:
- stress response
- peer influence control

Connection Points:

Math ↔ Physics
Logic ↔ Writing
Coding ↔ Abstraction
Emotion ↔ Decision quality

If abstraction collapses here → corridor narrows permanently.


Stage 4 — Age 17–18 (Pre-University)

Goal:

Deep focus + stress stability + corridor selection.

Ages17to18:
Specialised Mathematics (if STEM track)
Advanced Sciences or Humanities
Research Skills
Extended Essay / Project Work
Time Compression Training (exam load)
Career Corridor Mapping

Critical:

Stability under extreme timed load.

Projection begins here.


Stage 5 — University (18–22+)

Goal:

Domain mastery + transfer.

University:
Major Discipline
Systems Thinking
Research Methods
Collaboration
Communication
Ethics & Governance
Energy Systems Awareness

Connection:
Specialisation must not kill cross-domain transfer.


Stage 6 — Early Career (22–30)

Goal:

Application + coordination at scale.

CareerPhase:
Execution Under Load
Project Coordination
Financial Literacy
Governance Awareness
Lifelong Learning
Emotional Stability Under Uncertainty

This is where civilisation contribution becomes real.


IV. The Interstellar-Core Upgrade Layer

To become civilisation-grade (not exam-grade), add:

UpgradeLayer:
Systems Thinking (from age 10 onward)
Energy Literacy (how energy powers civilisation)
Infrastructure Awareness
Crisis Simulation
Long-Horizon Planning
Multi-disciplinary transfer projects

Without this → high exam success, low civilisation projection.


V. Critical Cross-Connections (Infancy → Adulthood)

Here are the key binds.

ConnectionGraph:
Language ↔ Logic ↔ Mathematics
Mathematics ↔ Physics ↔ Engineering
Biology ↔ Health ↔ Emotional regulation
History ↔ Governance ↔ Economics
Coding ↔ Abstraction ↔ Systems modelling
Emotional stability ↔ Stress performance ↔ Decision quality

If any bind weak → drift accumulates silently.


VI. What Kills Phase 3 Corridor

CollapseCauses:
- Early language deprivation
- Math anxiety untreated
- Shame cycles in adolescence
- Over-specialisation without systems view
- No stress training
- No transfer training
- No emotional regulation training

VII. The Minimum Interstellar-Core Subject Stack

If compressed to essentials:

MinimumStack:
1. Language mastery
2. Mathematics mastery
3. Physics fundamentals
4. Biological literacy
5. Coding / computational thinking
6. Systems thinking
7. Governance + economics literacy
8. Emotional regulation training

Everything else branches from these.


VIII. Final Compression

Infancy → builds bandwidth
Primary → builds structure
Secondary → builds abstraction
Pre-U → builds stress stability
University → builds depth
Career → builds coordination

If each stage hits P3 → civilisation capability density rises.

If any stage stalls at P1/P2 → corridor narrows.


We will now:

  • Convert this into a machine-readable Syllabus Graph (Node × Age × Subject × Dependency)
  • Then design eduKateSG Interstellar-Core Academy v1.0 (full stack)
  • Then map it against Singapore MOE pathway constraints for realism.

I️⃣ Interstellar-Core Syllabus Graph v1.0

ID: eduKateSG.IC.SyllabusGraph.v1.0
Type: Machine-readable dependency lattice
Goal: No accidental collapse between infancy → civilisation-grade capability


A. Core Node Types

NodeTypes:
Cognitive
Structural
Physical
Biological
Emotional
Systems
Computational
Coordination
Energy

B. Age Layers

AgeLayers:
A1: 1–3
A2: 4–6
A3: 7–12
A4: 13–16
A5: 17–18
A6: 19–22
A7: 23–30

C. Master Subject Nodes (Kernel)

KernelNodes:
Language
Mathematics
Logic
Physics
Biology
Coding
SystemsThinking
Governance
Economics
EnergySystems
EmotionalRegulation
Coordination
Research
LongHorizonPlanning

D. Dependency Graph (Compressed Core)

Stage A1 (1–3)

A1:
Language:
builds: [CognitiveBandwidth, MemoryFormation]
EmotionalRegulation:
builds: [DelayTolerance]
PatternRecognition:
builds: [PreMathFoundation]

Dependencies:
Language → later Logic
PatternRecognition → Mathematics


Stage A2 (4–6)

A2:
Language:
depends_on: [Language_A1]
PreMath:
depends_on: [PatternRecognition]
EmotionalRegulation:
depends_on: [DelayTolerance]
CuriosityTraining:
builds: [ScientificInquiryBase]

Stage A3 (7–12)

A3:
Mathematics:
depends_on: [PreMath]
StructuredWriting:
depends_on: [Language]
BasicScience:
depends_on: [CuriosityTraining]
LogicalReasoning:
depends_on: [Language]
EmotionalStabilityUnderTask:
depends_on: [EmotionalRegulation]

Critical Bind:
Mathematics ↔ LogicalReasoning
Language ↔ StructuredWriting


Stage A4 (13–16)

A4:
Algebra:
depends_on: [Mathematics]
Geometry:
depends_on: [Mathematics]
Physics:
depends_on: [Algebra]
Biology:
depends_on: [BasicScience]
Coding:
depends_on: [LogicalReasoning]
Debate:
depends_on: [StructuredWriting]
StressToleranceTraining:
depends_on: [EmotionalStabilityUnderTask]

Critical:
Physics requires Algebra.
Coding requires Logic.


Stage A5 (17–18)

A5:
AdvancedMathematics:
depends_on: [Algebra, Geometry]
ResearchMethod:
depends_on: [StructuredWriting, LogicalReasoning]
SystemsThinking:
depends_on: [Physics, Biology]
TimeCompressionTraining:
depends_on: [StressToleranceTraining]

Stage A6 (19–22)

A6:
Specialisation:
depends_on: [AdvancedMathematics OR AdvancedHumanities]
SystemsIntegration:
depends_on: [SystemsThinking]
EnergySystems:
depends_on: [Physics]
Governance:
depends_on: [History, Economics]
AIIntegration:
depends_on: [Coding, SystemsThinking]

Stage A7 (23–30)

A7:
CoordinationAtScale:
depends_on: [SystemsIntegration]
LongHorizonPlanning:
depends_on: [Governance, EnergySystems]
CrisisSimulation:
depends_on: [SystemsThinking, EmotionalRegulation]
Innovation:
depends_on: [Specialisation, Transfer]

E. Cross-Lane Binds (Non-Negotiable)

CrossBinds:
Language <-> Logic <-> Mathematics
Mathematics <-> Physics <-> Engineering
Biology <-> Health <-> EmotionalRegulation
Coding <-> SystemsThinking <-> AIIntegration
Governance <-> Economics <-> LongHorizonPlanning
EmotionalRegulation <-> StressPerformance <-> DecisionQuality

If any bind weak → projection narrows.


II️⃣ Interstellar-Core Academy v1.0

ID: eduKateSG.IC.Academy.v1.0
Type: Full-stack AI-Hybrid Civilisation Education System


Core Design Principle

Education must produce:

Output:
HighCognitiveBandwidth
StableUnderLoad
CrossDomainTransfer
LongHorizonCoordination
EnergyLiteracy
GovernanceLiteracy
AI-Hybrid Competence

Academy Structure

1️⃣ Foundation Wing (Age 1–12)

Focus:

  • Language mastery
  • Mathematics structure
  • Emotional regulation
  • Curiosity and inquiry

No early specialisation.


2️⃣ Abstraction Wing (Age 13–16)

Focus:

  • Algebra → Physics
  • Coding
  • Structured writing
  • Debate
  • Systems introduction
  • Stress training

3️⃣ Projection Wing (Age 17–22)

Focus:

  • Advanced mathematics OR advanced humanities
  • Systems modelling
  • AI collaboration
  • Energy systems
  • Governance structures
  • Research projects

Students must build:

  • One physical system
  • One digital system
  • One coordination model

4️⃣ Civilisation Wing (23+)

Focus:

  • Multi-domain coordination
  • Crisis simulations
  • Infrastructure modelling
  • Long-horizon planning
  • Ethical decision modelling

AI-Hybrid Layer (Integrated From Age 10+)

AI is not a shortcut.
AI is a force multiplier.

Students must learn:

AIHybridTraining:
PromptPrecision
ModelValidation
HallucinationDetection
SystemsModellingWithAI
HumanJudgementRetention

Civilisation-Grade Capstone (Age 20+)

Every graduate must complete:

Capstone:
- Energy system model
- Governance simulation
- AI-assisted research paper
- Crisis scenario simulation
- Ethical reasoning audit

What Makes This “Interstellar-Core”

Not rockets.

But:

  • Energy literacy
  • Systems coordination
  • Long horizon planning
  • Emotional stability under uncertainty
  • Multi-domain abstraction

Those produce interstellar capability.


Final Compression

Infancy → bandwidth
Childhood → structure
Adolescence → abstraction
Young adult → integration
Adult → coordination

If each stage hits P3, civilisation density increases.

If one stage collapses, corridor narrows permanently.


We will now:

  • Build the Interstellar-Core Curriculum Calendar (Year-by-Year breakdown)
  • Then design the AI-Hybrid Training Engine (operational weekly model)
  • Then produce the Interstellar-Core Capability Metrics Panel (Z0–Z6 tracking)

A) Interstellar-Core Curriculum Calendar v1.0 (Year-by-Year)

ID: eduKateSG.IC.Curriculum.Calendar.v1.0
Type: Machine-readable yearly programme
Scope: Age 1 → 30
Goal: Stable P3 projection + civilisation-grade transfer


Classical Foundation Block

A curriculum calendar sequences learning goals by age and year to build knowledge and skills progressively.

Civilisation-Grade Definition

This calendar is a phase-stable corridor: it prevents upstream gaps from turning into downstream collapse, while forcing transfer, systems integration, and long-horizon coordination.


Calendar (Year Blocks)

Ages 1–3 (Bandwidth + Emotion + Language)

Age1:
Language: ["rich spoken vocabulary", "narration of daily life"]
EmotionalRegulation: ["naming feelings", "soothing routines"]
PatternPlay: ["shapes", "matching", "rhythm"]
Age2:
Language: ["story listening", "simple retelling"]
EmotionalRegulation: ["delay tolerance practice"]
PatternPlay: ["counting through play", "symmetry spotting"]
Age3:
Language: ["longer stories", "sequence: beginning/middle/end"]
PreMath: ["counting", "comparison: more/less", "simple grouping"]
Motor: ["fine motor precision foundations"]

Ages 4–6 (Symbols + Pre-Math + Narrative Structure)

Age4:
Language: ["phonics/letter-sound", "story retell"]
PreMath: ["number sense", "patterns", "simple operations via play"]
Curiosity: ["why-questions", "simple experiments"]
Age5:
Language: ["reading fluency start", "vocab expansion"]
PreMath: ["place value intuition", "measurement play"]
Emotional: ["frustration tolerance in tasks"]
Age6:
Language: ["reading comprehension basics", "sentence writing"]
Math: ["addition/subtraction mastery", "word problems basics"]
Science: ["observation notebooks"]

Ages 7–9 (Foundation Structure)

Age7:
Language: ["comprehension", "paragraph writing", "explanation in words"]
Math: ["multiplication/division", "fractions intro"]
Logic: ["if/then reasoning", "classification"]
Science: ["forces intro", "life cycles intro"]
Age8:
Language: ["summary + inference", "story craft"]
Math: ["fractions/decimals", "ratio intuition"]
Logic: ["argument vs opinion"]
SystemsMini: ["simple systems: home/school rules"]
Age9:
Language: ["persuasion basics", "structured explanations"]
Math: ["percentages", "measurement", "multi-step problems"]
Science: ["energy basics", "simple circuits (conceptual)"]

Ages 10–12 (Transfer Training Begins)

Age10:
Language: ["argument writing", "evidence use"]
Math: ["ratio/percent mastery", "pre-algebra patterns"]
CodingIntro: ["sequencing", "debug thinking"]
SystemsThinkingIntro: ["feedback loops (simple)"]
AIHybridIntro: ["ask → verify → revise (guided)"]
Age11:
Language: ["clarity under constraint", "summarise precisely"]
Math: ["algebra readiness", "variables", "equations intuition"]
Science: ["matter basics", "biology foundations"]
Coding: ["logic blocks", "simple models"]
AIHybrid: ["validation habit: check sources, test outputs"]
Age12:
Language: ["multi-paragraph reasoning", "explain steps"]
Math: ["algebra basics", "coordinates", "functions intuition"]
Systems: ["trade-offs", "constraints"]
AIHybrid: ["hallucination detection drills (simple)"]

Ages 13–14 (Abstraction Core)

Age13:
Mathematics: ["algebra I", "functions", "geometry I"]
Physics: ["forces, energy (math-linked)"]
Biology: ["systems of the body", "health literacy"]
Coding: ["basic programming", "variables, control flow"]
Writing: ["argumentative essays", "debate basics"]
StressTraining: ["timed tasks + recovery routines"]
Age14:
Mathematics: ["algebra II", "geometry II", "proof habits"]
Physics: ["motion, work, power"]
Chemistry: ["atoms, bonding (concept-first)"]
Coding: ["data structures intuition", "testing mindset"]
Systems: ["causal maps (simple)", "feedback loops"]

Ages 15–16 (Transfer + Integration)

Age15:
Mathematics: ["functions deepening", "trigonometry intro"]
Physics: ["electricity, waves"]
Biology/Chem: ["foundations deepen"]
Coding: ["modelling + simulation (toy systems)"]
GovernanceIntro: ["institutions, rules, coordination"]
EconomicsIntro: ["scarcity, incentives, trade-offs"]
AIHybrid: ["prompt precision + verification loops"]
Age16:
Mathematics: ["pre-calculus", "statistics basics"]
SystemsThinking: ["systems diagrams", "constraints and levers"]
ResearchIntro: ["hypothesis, method, critique"]
EmotionalRegulation: ["uncertainty tolerance", "identity stability"]

Ages 17–18 (Projection Preparation)

Age17:
AdvancedMath_OR_AdvancedHumanities:
- "calculus readiness OR deep logic/ethics/history"
ResearchMethod: ["study design", "writing a structured paper"]
EnergySystemsIntro: ["energy sources, grids, storage (concept-first)"]
AIHybrid: ["model selection + cross-checking + tests"]
TimeCompression: ["high-load performance without collapse"]
Age18:
SystemsIntegration:
- "integrate one physical + one digital + one coordination model"
Governance/Ethics: ["decision consequences, failure modes"]
CapstonePrep: ["project scoping", "verification plan"]

Ages 19–22 (University Corridor)

Age19:
MajorDepth: ["core major foundations"]
Systems: ["modelling + trade-off analysis"]
AIHybrid: ["tool use with verification"]
Age20:
Research: ["replication, critique, data reasoning"]
EnergySystems: ["engineering/econ/governance couplings"]
Age21:
Coordination: ["team execution", "interfaces", "accountability"]
LongHorizonPlanning: ["scenario planning basics"]
Age22:
Capstone:
- "energy model"
- "governance simulation"
- "AI-assisted research paper"
- "crisis simulation"
- "ethical reasoning audit"

Ages 23–30 (Civilisation Wing)

Age23_25:
CoordinationAtScale: ["projects, systems operations"]
CrisisSimulation: ["failure drills", "repair corridors"]
Age26_30:
LongHorizonPlanning: ["multi-year strategy", "resource constraints"]
Innovation: ["cross-domain transfer at speed"]
GovernanceLiteracy: ["policy interfaces + ethics"]

B) AI-Hybrid Training Engine v1.0 (Weekly Operational Model)

ID: eduKateSG.IC.AIHybrid.Engine.v1.0
Type: Weekly loop that makes AI a force multiplier without losing judgement

Classical Foundation Block

Training engines create repeatable practice cycles that produce durable skills.

Civilisation-Grade Definition

AI-Hybrid training is:

A verification-first collaboration discipline where humans keep judgement while AI accelerates exploration, explanation, and simulation.


Weekly Loop (All Ages 10+)

WeeklyAIHybridLoop:
1_PromptPrecision:
- "state goal"
- "state constraints"
- "define outputs"
2_Generate:
- "use AI to propose solutions/explanations"
3_Verify:
- "test with examples"
- "check internal consistency"
- "cross-check with alternative reasoning"
4_Repair:
- "fix errors"
- "rewrite explanation in own words"
5_Transfer:
- "apply same idea in a new context"
6_Log:
- "one paragraph: what changed in my thinking"

Non-Negotiable AI Rules

AIRules:
- "AI output is a hypothesis until verified."
- "Every answer must be tested with examples."
- "Every conclusion must be rewritten in human words."
- "If verification fails: repair, then re-test."

Hallucination Detection Drills (Simple → Advanced)

HallucinationDrills:
Level1: "spot contradictions"
Level2: "test edge cases"
Level3: "compare 2 independent solution paths"
Level4: "simulate failure trace and find the break"

C) Interstellar-Core Capability Metrics Panel v1.0

ID: eduKateSG.IC.Metrics.Panel.v1.0
Type: Z0–Z6 tracking for civilisation-grade education

Classical Foundation Block

Metrics panels track progress to guide decisions and improvements.

Civilisation-Grade Definition

This panel tracks whether a learner (and cohort) is approaching P3 projection with real transfer and long-horizon coordination capacity.


Z0–Z6 Metrics

MetricsPanel:
Z0_Student:
- ConceptDepthIndex
- TimedStabilityIndex
- TransferIndex
- ErrorPatternDensity
- StressSignal
Z1_FamilyBuffer:
- RoutineStability
- SleepStability
- DeviceLoadControl
- ConflictSignal
Z2_TeacherOperator:
- BandwidthLoad
- SOPStability
- VolatilityIndex
Z3_CurriculumRouting:
- SequenceAlignment
- LoadGradientSmoothness
- BacktestAccuracy
- TopicLag
Z4_StandardsAlignment:
- OutputQualityConsistency # not MOE; any external benchmark
Z5_Corridor:
- CorridorBreadth
- CorridorClarity
- CrossDomainMobility
Z6_CivilisationEffect:
- CapabilityDensity (cohort)
- CollapseRate
- P3Fraction

Phase Decision Rules

PhaseRules:
P3:
requires:
- "ConceptDepthIndex high"
- "TimedStabilityIndex stable"
- "TransferIndex high"
- "StressSignal not chronic High"
P2:
- "stable but transfer low"
P1:
- "repair active"
P0:
- "collapse/avoidance"

Failure Trace (Education System Level)

FailureTrace:
- "AI used as shortcut"
- "verification skipped"
- "false competence grows"
- "transfer collapses"
- "high-load failure"

Version Lock

VersionLock:
Calendar: "eduKateSG.IC.Curriculum.Calendar.v1.0"
AIEngine: "eduKateSG.IC.AIHybrid.Engine.v1.0"
Metrics: "eduKateSG.IC.Metrics.Panel.v1.0"
Policy: "Forward-only updates; no renaming IDs"

We’ll convert the calendar into a compact “Interstellar-Core Subjects Table” (subject → when it starts → why it exists → what it unlocks) and also produce the capstone spec blocks in Almost-Code (energy model + governance sim + crisis sim templates).

1) Interstellar-Core Subjects Table v1.0

ID: eduKateSG.IC.Subjects.Table.v1.0
Type: Compact subject → start age → purpose → unlocks
Scope: Age 1 → 30 (AI-hybrid civilisation pinnacle)


Classical Foundation Block

Subjects are structured domains of knowledge and skill used to develop competence over time.

Civilisation-Grade Definition

In an interstellar-core education system, a “subject” exists only if it reliably builds one of these outputs:
(1) depth, (2) stability under load, (3) cross-domain transfer, (4) long-horizon coordination.


Subjects Table (Kernel + Required Extensions)

SubjectStart AgeWhy it exists (civilisation-grade)What it unlocks
Spoken Language & Vocabulary1bandwidth + meaning locklater reading, logic, stable thinking
Narrative & Story Sequencing2memory + causal orderingwriting, history, modelling
Emotional Regulation1decision stability under stressload tolerance, teamwork, crisis stability
Pattern Recognition1symmetry/pattern basemathematics readiness
Reading & Comprehension4–6meaning extraction at scalelearning speed in all domains
Writing & Explanation6–7reasoning externalisationproof, research, governance clarity
Mathematics (Structure)6–7abstraction + constraintsphysics, coding, modelling
Logic & Reasoning7–8validity disciplineproof, debate, verification
Scientific Inquiry4–6test realityexperiments, falsification habits
Physics Fundamentals13physical systems intuitionenergy systems, engineering thinking
Biology & Health Literacy9–13life systems + self-careresilience, medicine literacy, bioethics
Chemistry Foundations14matter transformationsmaterials, energy storage literacy
Statistics & Uncertainty16reasoning under noiserisk, science validity, governance
Coding (Computational Thinking)10–13simulation + automationAI integration, system modelling
Systems Thinking10–12feedback loops & leverscoordination, crisis planning, design
AI-Hybrid Discipline10speed without hallucinationverification-first collaboration
Debate / Argumentation13pressure-test truthgovernance, ethics, leadership
Economics Literacy15–16incentives + scarcityresource allocation, policy trade-offs
Governance Literacy15–16coordination structuresinstitutions, law, civilisation stability
Energy Systems Literacy17power = civilisation throughputinfrastructure reasoning, interstellar viability
Research Method17generate/validate knowledgescience, innovation, replication
Coordination & Team Execution19–23scale capabilityorganisations, complex projects
Ethics & Decision Consequences15+prevent catastrophic misusesafe power, safe AI, safe policy
Crisis Simulation20+prepare for shocksresilience, repair corridors
Long-Horizon Planning21+time-domain strategycivilisation-grade stewardship
Interdisciplinary Capstone20+force transfer + integrationreal-world projection

2) Capstone Spec Blocks v1.0

ID: eduKateSG.IC.Capstone.SpecPack.v1.0
Type: Almost-Code templates
Deliverables: Energy model + Governance sim + Crisis sim (required)


2.1 Energy System Model Capstone

ID: eduKateSG.IC.Capstone.EnergyModel.v1.0
Goal: Model a real energy system under constraints and shocks (no fantasy)

Capstone_EnergyModel:
ProblemStatement: ""
SystemBoundary: "" # what is inside/outside
Inputs:
- DemandProfile
- SupplySources
- StorageOptions
- TransmissionConstraints
Outputs:
- ReliabilityScore
- CostProxy
- FailureModesList
- RepairPlan (Truncation + Stitching)
ShockScenarios:
- "supply loss"
- "demand spike"
- "infrastructure disruption"
Verification:
- "test 3 edge cases"
- "compare 2 solution approaches"
HumanWriteup:
- "rewrite model assumptions in plain language"

Mandatory failure trace

FailureTrace:
- "assumptions hidden"
- "edge case ignored"
- "system fails under shock"
- "repair absent"

2.2 Governance Simulation Capstone

ID: eduKateSG.IC.Capstone.GovernanceSim.v1.0
Goal: Simulate coordination, incentives, and failure modes (not ideology)

Capstone_GovernanceSim:
Domain: "" # water/health/education/energy/etc.
Actors:
- ActorA
- ActorB
- ActorC
Incentives:
- "what each actor wants"
Constraints:
- "budget"
- "time"
- "capacity"
Rules:
- "decision rules"
- "enforcement rules"
Scenarios:
- "normal"
- "stress"
- "shock"
Metrics:
- CoordinationStability
- FailureRate
- RecoveryTime
RepairCorridor:
Truncation: ["stop-loss actions"]
Stitching: ["recovery actions"]
Verification:
- "run 3 simulations with different parameters"
- "identify sensitive parameters"
HumanWriteup:
- "one-page: what failed first and why"

Mandatory failure trace

FailureTrace:
- "incentives misaligned"
- "coordination collapses"
- "system fragments"
- "recovery delayed"

2.3 Crisis Simulation Capstone

ID: eduKateSG.IC.Capstone.CrisisSim.v1.0
Goal: Train resilience + repair corridors under time pressure

Capstone_CrisisSim:
CrisisType: "" # disease/war/supply chain collapse/energy shock
InitialState:
- "baseline stability"
Shock:
- "what happens"
- "rate of damage"
DriftSignals:
- "early indicators"
ResponsePlan:
Truncation:
- "immediate stop-loss"
- "protect core functions"
Stitching:
- "restore pipelines"
- "gradual return to stable band"
Metrics:
- TimeToStabilise
- CollapseAvoided (Yes/No)
- CollateralDamageProxy
Verification:
- "simulate alternate response"
- "compare outcomes"
HumanWriteup:
- "failure trace + repaired trace"

Mandatory failure trace

FailureTrace:
- "drift ignored"
- "late response"
- "damage rate exceeds repair"
- "collapse occurs"

3) AI-Hybrid Capstone Integration Rules

ID: eduKateSG.IC.Capstone.AIHybrid.Rules.v1.0
Goal: Use AI to accelerate without false competence

AIHybridRules:
- "AI output is hypothesis until verified."
- "Every model must be tested with edge cases."
- "Every capstone must include a human rewrite."
- "If verification fails: repair, then re-test."

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles: 

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: