(Almost-Code Canonical Spec + Full Lattice Codes, Z0–Z3 + P0–P3 routing)
This closes the last major “school spine” gap after Secondary English.
Once ENG-SEC + SCI-SEC exist, eduKateSG can confidently claim Primary → Secondary continuity.
0) Definition Lock
Secondary Science Mastery (P3)
Reliable concept understanding + multi-step application + data interpretation + structured explanations under timed assessment, across Bio/Chem/Physics-type domains.
Not:
- memorising keywords only
- copying “answer phrases” without mechanism
- doing well only on familiar question styles
- being accurate only when slow/untimed
1) Lane Architecture (SCI-SEC)
SCI-SEC ├─ CLC (Concept Lattice) ├─ MEC (Mechanism Engine) ├─ EXP (Experiment / Variables) ├─ DAT (Data Interpretation) ├─ STR (Structured Response Writing) └─ EXM (Exam Control / Timed Stability)
Science is a lattice of:
- concepts
- relationships
- mechanisms
- variable control
- explanation structure
2) Coordinate Grammar (LOCKED, same as Atlas)
SCI-SEC-<Z>-<MODULE>-<NODE>-P<0|1|2|3>
Zoom:
- Z0 micro units
- Z1 relationships/control
- Z2 application/transfer
- Z3 stability under load (time)
3) SCI-SEC Lattice Codes (Complete Set)
A) Concept Lattice (SCI-SEC-CLC)
Core nodes
SCI-SEC-Z0-CLC-DEF= definition precision (terms + symbols)SCI-SEC-Z0-CLC-UNIT= units / quantities / measurement meaningSCI-SEC-Z1-CLC-LINK= link concepts (cause chains / dependencies)SCI-SEC-Z1-CLC-MOD= model understanding (diagrams, representations)SCI-SEC-Z2-CLC-APP= apply to unfamiliar scenarioSCI-SEC-Z3-CLC-STABLE= stable recall & linking under time
Failure mapping
- memorises but can’t connect →
SCI-SEC-Z1-CLC-LINK-P0 - “knows term” but wrong unit reasoning →
SCI-SEC-Z0-CLC-UNIT-P1 - fails unfamiliar contexts →
SCI-SEC-Z2-CLC-APP-P0
Repairs
- concept-link maps (node→node arrows)
- unit sense drills (what does unit mean?)
- scenario variation drills
B) Mechanism Engine (SCI-SEC-MEC)
Core nodes
SCI-SEC-Z1-MEC-CHAIN= chain completeness (cause→mechanism→effect)SCI-SEC-Z2-MEC-STEPS= multi-step mechanism explanationSCI-SEC-Z2-MEC-CONSTRAINT= boundary conditions (when rule applies)SCI-SEC-Z3-MEC-SPEED= mechanism recall speed under time
Failures
- states result only →
SCI-SEC-Z1-MEC-CHAIN-P0 - explains but skips key step →
SCI-SEC-Z2-MEC-STEPS-P1 - applies rule outside condition →
SCI-SEC-Z2-MEC-CONSTRAINT-P0
Repairs
- 3-line chain drill (Cause/Mechanism/Effect)
- step-missing identification practice
- constraint tagging: “ONLY when…”
C) Experiments & Variables (SCI-SEC-EXP)
This is where many students collapse: they can “memorise theory” but cannot reason about experiments.
Core nodes
SCI-SEC-Z0-EXP-DEF= define IV/DV/controls fairlySCI-SEC-Z1-EXP-VAR= identify IV/DV/controls in scenarioSCI-SEC-Z1-EXP-FAIR= fairness logic (control variables)SCI-SEC-Z2-EXP-DESIGN= design experiment stepsSCI-SEC-Z2-EXP-ERROR= sources of error + improvementsSCI-SEC-Z3-EXP-TIMED= stable under exam time pressure
Failures
- confuses IV/DV →
SCI-SEC-Z1-EXP-VAR-P0 - can identify but can’t justify →
SCI-SEC-Z1-EXP-FAIR-P1 - cannot propose improvements →
SCI-SEC-Z2-EXP-ERROR-P0
Repairs
- “IV/DV/control sorting” drills
- fairness sentence template:
- “Keep _ constant so only affects ___.”
- error/improvement pairs practice
D) Data Interpretation (SCI-SEC-DAT)
Core nodes
SCI-SEC-Z1-DAT-READ= read graphs/tables correctlySCI-SEC-Z1-DAT-TREND= describe trend preciselySCI-SEC-Z2-DAT-CALC= compute from data (rate/gradient/mean etc.)SCI-SEC-Z2-DAT-EXPLAIN= explain trend using mechanismSCI-SEC-Z3-DAT-PACE= time-per-question stability
Failures
- reads axis wrong →
SCI-SEC-Z1-DAT-READ-P0 - describes trend vaguely →
SCI-SEC-Z1-DAT-TREND-P1 - calculates wrong →
SCI-SEC-Z2-DAT-CALC-P0 - no explanation →
SCI-SEC-Z2-DAT-EXPLAIN-P1
Repairs
- axis-first protocol
- trend sentence templates (increase/decrease/plateau)
- “calculation check step” (units + plausibility)
- explanation = link back to mechanism codes
E) Structured Response Writing (SCI-SEC-STR)
Science answers are not English essays.
They are precision chains.
Core nodes
SCI-SEC-Z0-STR-KWD= correct keyword selectionSCI-SEC-Z1-STR-SEQ= correct sequence/orderSCI-SEC-Z2-STR-CLAIM= claim supported by evidence/dataSCI-SEC-Z2-STR-JUST= justification qualitySCI-SEC-Z3-STR-TIMED= stable structure under time
Failures
- keyword dump →
SCI-SEC-Z0-STR-KWD-P1 - wrong order →
SCI-SEC-Z1-STR-SEQ-P0 - no justification →
SCI-SEC-Z2-STR-JUST-P0
Repairs
- 2-mark / 3-mark templates
- “sequence lock” drills
- claim→data→explain format
F) Exam Control (SCI-SEC-EXM)
Core nodes
SCI-SEC-Z1-EXM-ALLOC= time allocation per sectionSCI-SEC-Z2-EXM-ORDER= question order & skip logicSCI-SEC-Z3-EXM-STABLE= stability under timed paperSCI-SEC-Z3-EXM-RECOV= recovery after error/panic
Failures
- spends too long on hard questions →
SCI-SEC-Z1-EXM-ALLOC-P0 - panic & blanks →
SCI-SEC-Z3-EXM-RECOV-P0
Repairs
- stop-loss rule (move on after X minutes)
- “first-pass easy marks” strategy
4) Bio/Chem/Physics Snap-In (Optional Node Tags)
To keep it universal, you can add domain tags:
...-BIOfor biology-type...-CHEfor chemistry-type...-PHYfor physics-type
Example:
SCI-SEC-Z2-MEC-STEPS-BIO-P1SCI-SEC-Z1-EXP-VAR-CHE-P0
This lets you expand later without breaking the grammar.
5) Cross-Lane Routing Examples (Real Diagnosis)
Case 1: “Student writes long answers but low marks”
Likely:
- weak keyword selection + weak sequence
Codes: SCI-SEC-Z0-STR-KWD-P1SCI-SEC-Z1-STR-SEQ-P0
Repair:
- mark scheme keyword targeting + template enforcement
Case 2: “Can do theory but experiments always wrong”
Codes:
SCI-SEC-Z1-EXP-VAR-P0SCI-SEC-Z1-EXP-FAIR-P1
Repair:
- IV/DV/control drills + fairness sentence template
Case 3: “Graph questions destroy them”
Codes:
SCI-SEC-Z1-DAT-READ-P0SCI-SEC-Z2-DAT-CALC-P0
Repair:
- axis-first protocol + units & plausibility checks
6) Why This Completes eduKateSG (School Spine)
Now your site has:
✅ Primary Math / English / Science
✅ Secondary English
✅ Secondary Science
The only remaining mainstream closure page is:
OLEVEL-OS (Outcome Reliability Under Variation + Time)
That wrapper ties:
- ENG-SEC
- SCI-SEC
- MTH-SEC (E/A Math)
into one “exam reliability OS”.
Next
I will write OLEVEL-OS as the system wrapper with lattice codes + routing.