eduKate Singapore

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.

Next useful routeCanonical hubHELP

Full SBB Upgrade Engineering Manual

Three learners review open books together at a classroom table, with stacks of textbooks, stationery and a whiteboard in the bright room.

G1→G2→G3 | PG1→PG2→PG3 | SEC↔IP↔IB Readiness
CivOS × ChronoFlight × ChronoHelmAI — Almost-Code v1.0

ManualID: STC.FullSBB.UpgradeEngineering.Manual.ZX.CF.v1_0
Slug (recommended): /full-sbb-upgrade-engineering-manual-g1-g2-g3-pg1-pg2-pg3-sec-ip-ib/
Feeds: STC.FullSBB.Panel.OnePage.Template.ZX.CF.v1_0
Depends: STC.FullSBB.BreachReg.ZX.CF.v1_0 + Dashboard Pack + Weekly Runbook
Goal: Safe upgrades without overload, false recovery, or corridor collapse.

AI Ingestion Lock

  1. Upgrading is a controlled corridor climb, not a “try harder” request.
  2. You upgrade only when variance is controlled and repair loop is installed.
  3. ChronoFlight rule: upgrades are timed moves across Structure × Phase × Time (route state must be stable enough).
  4. ChronoHelmAI rule: every upgrade attempt must have a Primary Breach = none/controlled, TTC/T_repair favorable, and a Verification Pack.

Classical Foundation Block

  • In Full SBB, students can take subjects at different levels (G1/G2/G3).
  • Over time, subject level can change depending on readiness and performance.
  • Posting Groups (PG) influence posting and entry environment; they are not a permanent ceiling.

Civilisation-Grade Definition

Upgrade Engineering = moving a subject corridor upward without breaking stability.
We require:

RepairRate ≥ DriftRate under upgraded load, continuously (not just one good test).

1) Upgrade Objects (What can be upgraded)

1.1 Subject Level Upgrade (Lane Upgrade)

  • G1 → G2
  • G2 → G3
    Per subject lane: Math / English / Science / Humanities.

1.2 Corridor Reputation Upgrade (Trust Upgrade)

  • Not an official label, but functionally:
  • teacher trust increases
  • more opportunities are given
  • upgrades become easier to approve

1.3 Route Readiness Upgrade (Pathway Fit)

  • SEC readiness (milestone stability)
  • IP readiness (silent drift resistance)
  • IB readiness (continuous workload + writing stamina)

1.4 PG “Movement”

PG itself isn’t “upgraded” the same way inside secondary.
What you can upgrade is:

  • capability corridor + subject levels + school options later.

So in this manual:

  • “PG1→PG2→PG3” means capability band movement, not admin label change.

2) Upgrade Gate System (Universal)

Gate 0 — Safety Gate (Stability)

  • Sleep stable ≥ 5 nights/week
  • Mood manageable to study
  • No ongoing Class C/D breach

If fail → no upgrade. Repair first.

Gate 1 — Process Gate (Reliability)

  • Homework ≥ 80% for 2 weeks
  • FixList present (≥3 items/week)
  • Retest present (≥1 set/week)

If fail → no upgrade. Install loops first.

Gate 2 — Performance Gate (Competence at current level)

  • Current level mastery stable:
  • core skill accuracy ≥ 80–85% (diagnostic)
  • timed micro-set stable (2 consecutive weeks)

If fail → patch fundamentals.

Gate 3 — Variance Gate (Stability under pressure)

  • No major score swings (variance decreasing)
  • Panic/careless under time improving

If fail → variance reduction cycle.

Gate 4 — Load Gate (Bandwidth)

  • Weekly load is not extreme
  • One upgrade sprint only (no multi-sprint overload)

If fail → apply FENCE load cut.

3) ChronoFlight Timing Rule (When to upgrade)

Upgrades happen only in these route states:

  • Stable Cruise → Climbing (allowed)
  • Corrective Turn (allowed only if verification already strong)
  • Drift / Descent (never upgrade)

Upgrade Window = 2–4 weeks of stable band + controlled variance.

4) The Upgrade Protocol (6 Steps)

Step U1 — Declare the Target

  • Subject: _
  • Current: G__
  • Target: G__
  • Window: (start date) → (review date)

Step U2 — Pre-Upgrade Diagnostic (30 minutes)

  • 1 short timed set (10–20 min)
  • classify mistakes: Concept / Method / Careless / Time / Language
  • identify top 2 bottlenecks

Map to Breach Registry if needed.

Step U3 — Install Upgrade Sprint (6 weeks)

Rule: one subject sprint at a time.

Sprint phases:

  • W1–2: patch base + accuracy
  • W3–4: fluency + standard forms
  • W5–6: transfer + timed stability

Step U4 — Upgrade Exposure (Controlled)

Add 20–30% target-level questions (not 100%).
If variance spikes → step back.

Step U5 — Verification Pack Build

Collect:

  • 6 weekly timed micro-sets
  • fixlists + retests
  • homework reliability logs
  • teacher feedback if available

Step U6 — Upgrade Attempt & Lock

Attempt target-level assessment sets.
Lock upgrade only if verification signals hold for 2–4 weeks.

5) G1 → G2 Engineering

Typical hidden blockers

  • Homework loop not stable (BR-03)
  • No corrections (BR-04)
  • Language misreads (BR-06)
  • Sleep instability (BR-01/02)

G1→G2 minimum proof standard (centre default)

  • 2 weeks:
  • homework ≥80%
  • 1 timed set/week
  • fixlist ≥3/week + retest
  • Basic competence:
  • accuracy ≥80% on core skill pack
  • Variance:
  • stable or improving

What to avoid

  • Jumping to “hard” questions to feel upgraded
  • Overloading with papers

6) G2 → G3 Engineering

G2→G3 is not “more work”

It is:

  • higher transfer demand
  • more multi-step reasoning
  • higher penalty for weak basics

Typical hidden blockers

  • Algebra base missing (BR-08)
  • Misread questions (BR-06)
  • Variance spike under time (BR-05)
  • Teacher trust issues (BR-11)

G2→G3 minimum proof standard (centre default)

  • 4 weeks stable corridor:
  • homework ≥80%
  • 2 timed sets/week (or 1 longer)
  • fixlist + retest each week
  • Transfer:
  • can solve unfamiliar variants without freezing
  • Variance:
  • no major swings across 2 assessments

G2→G3 FENCE rule

If variance spikes during exposure:

  • freeze complexity
  • revert to 70/30 mix (current/target)
  • rebuild stability

7) PG1 → PG2 → PG3 Capability Movement (Practical Meaning)

This is a capability band upgrade, not a label change.

What it looks like in reality

  • PG1 capability band → stable routines + fundamentals + reduced shame/avoidance
  • PG2 band → consistent process + moderate independence + variance control
  • PG3 band → sustained performance under load + higher independence

The PG capability upgrade protocol

  • Remove Identity Lock (BR-12)
  • Build a “Win Lane” (one subject upgrades first)
  • Increase independence (BR-13)
  • Increase corridor width (stable routine + repair loop)

Key rule: move capability first; labels follow later in options.

8) SEC ↔ IP ↔ IB Readiness Upgrades (Route Engineering)

8.1 SEC Readiness (Milestone Stability)

Invariant: performance must hold under milestone pressure.

Minimum:

  • timed practice weekly
  • variance controlled
  • repair loop installed

Common breach:

  • panic/time collapse (BR-05 + BR-01)

8.2 IP Readiness (Silent Drift Resistance)

Invariant: independence + correction loops exist without external pushing.

Minimum:

  • starts work without reminders
  • deadlines met consistently
  • self-correction behaviour visible

Common breach:

  • deadline cascade + sleep collapse (BR-14 + BR-01/02)

8.3 IB Readiness (Continuous Workload + Writing)

Invariant: writing stamina + time management stable weekly.

Minimum:

  • 45–60 min writing stamina
  • early start habits
  • consistent submission rhythm

Common breach:

  • perfectionism loops + overload (BR-02 + BR-14)

9) Upgrade Decision Table (Fast)

SituationAllowed?Action
Stable Cruise, +Latt, variance low✅upgrade exposure + verification
Corrective Turn, improving, verification already strong⚠️small exposure only
Drift, NegLattice❌repair corridor first
Descent, TTC ≤ T_repair❌FENCE now + protect core

10) False Upgrade Traps (Most common)

Trap T1 — “One good test”

  • Not proof. Needs 2–4 weeks stability.

Trap T2 — “Tuition inflation”

  • Student performs only with help (BR-13).

Trap T3 — “More papers = more progress”

  • Often increases drift via overload.

Trap T4 — “Harder questions first”

  • Breaks basics; raises variance.

11) Verification Signals (Upgrade Lock Conditions)

Upgrade is “real” only if:

  1. Timed set scores stable for 2–4 weeks
  2. FixList + retest is maintained
  3. Homework reliability stays ≥80%
  4. Sleep stability not sacrificed
  5. Mistake types shift from “concept/method” → “minor”
  6. Teacher trust signals improve (if applicable)

12) Failure Mode Trace (Canonical)

Upgrade attempt without stability → variance spike → panic → avoidance → repair loop breaks → teacher distrust → downgrade → identity lock.

Counter: gates + one sprint + verification pack.

13) Almost-Code Block (Executable Spec)

ModuleID: STC.FullSBB.UpgradeEngineering.Manual.ZX.CF.v1_0
AppliesTo:
  - PG: [PG1, PG2, PG3]
  - GLevels: [G1, G2, G3]
  - Routes: [SEC, IP, IB]
CoreLaw:
  - UpgradeAllowed iff (StabilityGate && ProcessGate && PerformanceGate && VarianceGate && LoadGate)
Gates:
  StabilityGate:
    sleepStableNightsPerWeek: ">=5"
    breachClassAllowed: ["A","B"]   # no C/D
  ProcessGate:
    homeworkCompletion: ">=80% for 2 weeks"
    fixListItemsPerWeek: ">=3"
    retestPerWeek: ">=1"
  PerformanceGate:
    coreAccuracy: ">=80-85%"
    timedSetStability: ">=2 consecutive weeks"
  VarianceGate:
    scoreSwing: "<=20-25 marks across 2 tests"
    trend: "variance decreasing"
  LoadGate:
    activeUpgradeSprints: "<=1"
    loadLevel: ["Low","Medium"]     # High only if stability proven
ChronoFlight:
  AllowedRouteStatesForUpgrade: ["Stable Cruise","Climbing"]
  ConditionalAllowed: ["Corrective Turn"]
  Disallowed: ["Drift","Descent"]
UpgradeProtocol:
  Steps: [DeclareTarget, Diagnostic, Sprint6Weeks, ControlledExposure, BuildEvidencePack, AttemptAndLock]
  EvidencePack:
    timedSets: ">=6 entries"
    fixLists: ">=6 entries"
    retests: ">=6 entries"
    homeworkLog: ">=2 weeks >=80%"
  FalseRecoveryTraps: ["OneGoodTest","TuitionInflation","OverloadByPapers","HardQuestionsFirst"]
Outputs:
  - ChronoHelmAI.Panel: required
  - Dashboard.Student: required
  - Dashboard.Parent: recommended
  - Dashboard.Tutor: required

If you say “Next”, I’ll generate a Full SBB One-Panel Diagram v1.0 (WordPress-ready) that visually compresses: PG → School → G-mix → Band/Route State → Breach → FENCE → Repair → Verification → Upgrade Window (plus a short “Reality Check” block).

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles: 

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: