Technical Documentation of IGCSE Mathematics Tutorial by eduKateSG v4.0

Full Packet Documentation in Almost Code

Official anchor first.
For Cambridge IGCSE Mathematics 0580, the current official syllabus window is 2025–2027. Cambridge treats it as a tiered qualification with Core and Extended routes. Core candidates take Paper 1 and Paper 3; Extended candidates take Paper 2 and Paper 4. Papers 1 and 2 are non-calculator, while Papers 3 and 4 require a scientific calculator. Cambridge also defines two assessment objectives: AO1 Knowledge and understanding of mathematical techniques and AO2 Analyse, interpret and communicate mathematically. (cambridgeinternational.org)

For Pearson Edexcel International GCSE Mathematics A (4MA1), the official structure is different: it is a linear qualification, available at Foundation and Higher tier, with two examinations taken in the same series. Pearson’s specification also includes formula sheets and allows calculator use in the examinations. The subject code is 4MA1, with paper codes 4MA1/1F, 4MA1/2F, 4MA1/1H, 4MA1/2H. (qualifications.pearson.com)

Everything below the official anchor is the eduKateSG runtime layer. It is a teaching and diagnostic system built on top of the official exam structures, not official board wording. Its purpose is to convert the syllabus into packetized tutorial operations: diagnose, route, repair, condition, and retest.

---

0. Meta Lock

DOC.NAME = “Technical Documentation of IGCSE Mathematics Tutorial by eduKateSG v4.0”
DOC.TYPE = “Full Packet Documentation”
DOC.MODE = “Almost Code”
DOC.DEFAULT_BINDING = “Cambridge IGCSE Mathematics 0580”
DOC.COMPATIBILITY = [“Cambridge 0980”, “Pearson Edexcel 4MA1”]
DOC.PURPOSE = “Convert IGCSE Mathematics into packetized lesson operations”
DOC.BOUNDARY = “Official board layer must remain separate from eduKateSG packet layer”
DOC.PRIMARY_USE = “Tutor diagnostics, lesson routing, homework assignment, review control, mock conditioning”

---

1. Packet System Philosophy

EDUKATESG.PACKET_SYSTEM.THESIS = “Students do not improve just because they attend tuition. They improve when the right packet is assigned to the right failure state at the right time.”

EDUKATESG.PACKET_SYSTEM.PRINCIPLES = {
 P1: “Packets are not worksheets only”,
 P2: “Packets are state-targeted interventions”,
 P3: “Each packet must have entry trigger and exit rule”,
 P4: “A packet without a diagnostic trigger is noise”,
 P5: “A packet without a mastery exit becomes repetition without repair”
}

---

2. Packet Namespace

PACKET.NAMESPACE = {
 ROOT: “IGCSE.PKT”,
 FAMILY_PREFIX: {
  ENTRY: “E”,
  REPAIR: “R”,
  TRANSFER: “T”,
  PAPERMODE: “P”,
  MARKCAPTURE: “M”,
  MOCK: “X”,
  MEMORY: “Y”
 },
 ENGINE_CODE: {
  NUMBER: “NUM”,
  ALGEBRA: “ALG”,
  GRAPHS: “GRF”,
  GEOMETRY: “GEO”,
  MEASURE_TRIG: “MTR”,
  DATA: “DAT”,
  MIXED: “MIX”,
  NONCALC: “NC”,
  CALC: “CC”,
  PRESENTATION: “PR”,
  ENDURANCE: “EN”,
  RECALL: “RC”
 }
}

PACKET.ID.FORM = “IGCSE.PKT….”

EXAMPLES = [
 ”IGCSE.PKT.E.NUM.00.01″,
 ”IGCSE.PKT.R.ALG.01.03″,
 ”IGCSE.PKT.P.NC.02.01″,
 ”IGCSE.PKT.M.PR.01.02″,
 ”IGCSE.PKT.X.EN.03.01″
]

---

3. Packet Object Schema

PACKET.OBJECT = {
 id: “”,
 title: “”,
 board_binding: “”,
 tier_binding: “”,
 family: “”,
 engine: “”,
 level: “”,
 purpose: “”,
 entry_trigger: [],
 prerequisites: [],
 materials: [],
 lesson_runtime: [],
 homework_runtime: [],
 diagnostic_sensors: [],
 common_errors: [],
 success_criteria: [],
 exit_rule: “”,
 follow_on_packet: []
}

---

4. Global Diagnostic Form Template

FORM.DIAGNOSTIC.IGCSE.V1 = {
 student_name: “”,
 date: “”,
 board: “”,
 tier: “”,
 school_level: “”,
 recent_exam_score: “”,
 target_grade: “”,
 phase_estimate: “”,
 paper_mode_risk: {
  noncalc: 0,
  calc: 0
 },
 engine_scores: {
  number: 0,
  algebra: 0,
  graphs: 0,
  geometry: 0,
  measure_trig: 0,
  data: 0,
  mark_capture: 0,
  endurance: 0
 },
 sensor_scores: {
  fraction_stability: 0,
  sign_discipline: 0,
  formula_retrieval: 0,
  graph_translation: 0,
  diagram_reading: 0,
  method_choice_speed: 0,
  working_visibility: 0,
  time_endurance: 0,
  error_recovery: 0
 },
 dominant_error_codes: [],
 secondary_error_codes: [],
 assigned_packets: [],
 next_4_week_route: “”
}

SCORE.SCALE = {
 0: “Absent”,
 1: “Very weak”,
 2: “Weak”,
 3: “Usable”,
 4: “Stable”,
 5: “Strong”
}

---

5. Error Code Registry

ERROR.CODE.REGISTRY = {
 ER01: “Fraction instability”,
 ER02: “Decimal-percentage confusion”,
 ER03: “Ratio/proportion mismatch”,
 ER04: “Negative sign drift”,
 ER05: “Bracket expansion corruption”,
 ER06: “Equation rearrangement failure”,
 ER07: “Graph feature blindness”,
 ER08: “Gradient/intercept confusion”,
 ER09: “Angle property misread”,
 ER10: “Diagram panic”,
 ER11: “Formula retrieval failure”,
 ER12: “Unit loss”,
 ER13: “Wrong method chosen”,
 ER14: “Premature rounding”,
 ER15: “No visible working”,
 ER16: “Calculator setup error”,
 ER17: “Late-paper fatigue”,
 ER18: “Confidence collapse after one mistake”
}

---

6. Entry Packet Family

6.1 Baseline Scan

IGCSE.PKT.E.MIX.00.01 = {
 id: “IGCSE.PKT.E.MIX.00.01”,
 title: “Entry Baseline Scan”,
 board_binding: “All”,
 tier_binding: “All”,
 family: “ENTRY”,
 engine: “MIXED”,
 level: “L0”,
 purpose: “Find board-fit, tier-fit, engine heat, and paper-mode risk”,
 entry_trigger: [“new_student”, “route_reset”, “post-exam collapse”],
 prerequisites: [],
 materials: [“short mixed test”, “timing sheet”, “working visibility sheet”],
 lesson_runtime: [
  ”10 min mixed arithmetic/algebra”,
  ”10 min graph/geometry/data sample”,
  ”10 min paper-mode probe”,
  ”10 min script review”,
  ”10 min state read”
 ],
 diagnostic_sensors: [“fraction_stability”, “sign_discipline”, “graph_translation”, “diagram_reading”, “working_visibility”],
 common_errors: [“ER01”, “ER04”, “ER07”, “ER10”, “ER15”],
 success_criteria: [“dominant failure cluster identified”, “starting route chosen”],
 exit_rule: “At least one dominant packet family assigned”,
 follow_on_packet: [“IGCSE.PKT.E.RC.00.02”, “IGCSE.PKT.R.NUM.01.01”, “IGCSE.PKT.R.ALG.01.01”]
}

6.2 Recall Scan

IGCSE.PKT.E.RC.00.02 = {
 id: “IGCSE.PKT.E.RC.00.02”,
 title: “Recall Speed Scan”,
 board_binding: “All”,
 tier_binding: “All”,
 family: “ENTRY”,
 engine: “RECALL”,
 level: “L0”,
 purpose: “Measure how quickly the student retrieves core relations under mild pressure”,
 entry_trigger: [“student says ‘I know this but forget during exam'”],
 materials: [“flash strip”, “mini non-calc strip”, “formula recall strip”],
 diagnostic_sensors: [“method_choice_speed”, “formula_retrieval”, “error_recovery”],
 common_errors: [“ER11”, “ER13”, “ER18”],
 success_criteria: [“retrieval latency profile known”],
 exit_rule: “Tutor can distinguish weak knowledge from weak retrieval”
}

---

7. Number Repair Packets

7.1 Fractions and Arithmetic Floor

IGCSE.PKT.R.NUM.01.01 = {
 id: “IGCSE.PKT.R.NUM.01.01”,
 title: “Number Floor Repair A”,
 board_binding: “All”,
 tier_binding: “All”,
 family: “REPAIR”,
 engine: “NUMBER”,
 level: “L1”,
 purpose: “Repair arithmetic leakage before it contaminates algebra and paper flow”,
 entry_trigger: [“fraction_stability <= 2”, “ER01 active”, “ER02 active”],
 prerequisites: [“IGCSE.PKT.E.MIX.00.01”],
 materials: [“fraction strip”, “decimal-percent conversions”, “ratio ladder”],
 lesson_runtime: [
  ”teacher models exact method”,
  ”student executes slowly with line control”,
  ”timed micro-drill”,
  ”mixed recap”
 ],
 homework_runtime: [“10 fraction items”, “10 decimal-percent items”, “5 ratio applications”],
 diagnostic_sensors: [“fraction_stability”, “working_visibility”],
 common_errors: [“ER01”, “ER02”, “ER03”],
 success_criteria: [“80% clean arithmetic in controlled set”, “student shows full steps”],
 exit_rule: “Two consecutive clean sets above threshold”,
 follow_on_packet: [“IGCSE.PKT.R.NUM.01.02”, “IGCSE.PKT.P.NC.01.01”]
}

7.2 Indices, Standard Form, Bounds

IGCSE.PKT.R.NUM.01.02 = {
 id: “IGCSE.PKT.R.NUM.01.02”,
 title: “Number Floor Repair B”,
 purpose: “Stabilise higher-order number control needed for IGCSE question flow”,
 entry_trigger: [“student safe on basic arithmetic but breaks on indices/standard form/bounds”],
 materials: [“index rules”, “standard form conversions”, “bounds mini-mix”],
 common_errors: [“ER13”, “ER14”],
 success_criteria: [“index operations legal”, “scientific notation stable”, “bounds reasoning visible”],
 exit_rule: “Student can mix these with algebra without reopening ER01–ER03”
}

---

8. Algebra Repair Packets

8.1 Sign and Structure Repair

IGCSE.PKT.R.ALG.01.01 = {
 id: “IGCSE.PKT.R.ALG.01.01”,
 title: “Algebra Repair A: Sign Discipline”,
 board_binding: “All”,
 tier_binding: “All”,
 family: “REPAIR”,
 engine: “ALGEBRA”,
 level: “L1”,
 purpose: “Stop sign drift and bracket corruption”,
 entry_trigger: [“sign_discipline <= 2”, “ER04 active”, “ER05 active”],
 materials: [“expand-simplify strips”, “negative sign drills”, “one-step checking”],
 lesson_runtime: [
  ”identify sign danger zones”,
  ”expand with colour-coded legality”,
  ”reverse-check each line”,
  ”mini timed set”
 ],
 diagnostic_sensors: [“sign_discipline”, “working_visibility”],
 common_errors: [“ER04”, “ER05”],
 success_criteria: [“one algebra move per line”, “sign integrity preserved”],
 exit_rule: “No silent sign flips across 2 controlled sets”,
 follow_on_packet: [“IGCSE.PKT.R.ALG.01.02”, “IGCSE.PKT.M.PR.01.01”]
}

8.2 Rearrangement and Equation Control

IGCSE.PKT.R.ALG.01.02 = {
 id: “IGCSE.PKT.R.ALG.01.02”,
 title: “Algebra Repair B: Rearrangement and Solving”,
 purpose: “Restore lawful symbolic movement in equations and formulas”,
 entry_trigger: [“ER06 active”, “student gets lost between steps”],
 materials: [“equation ladder”, “formula rearrangement sheet”, “inequality control strip”],
 common_errors: [“ER06”, “ER13”, “ER15”],
 success_criteria: [“student can narrate why each move is legal”],
 exit_rule: “Rearrangement stable under mixed contexts”
}

8.3 Factorisation and Pattern Control

IGCSE.PKT.R.ALG.02.03 = {
 id: “IGCSE.PKT.R.ALG.02.03”,
 title: “Algebra Repair C: Pattern Recognition”,
 purpose: “Repair factorisation and pattern matching under pressure”,
 entry_trigger: [“student knows methods but chooses wrong algebra path”],
 materials: [“difference of squares”, “common factor”, “quadratic pattern sheets”],
 common_errors: [“ER13”],
 success_criteria: [“correct family chosen first time more often”],
 exit_rule: “Pattern recognition stable across mixed algebra set”
}

---

9. Graph Repair Packets

9.1 Coordinates, Gradient, Intercepts

IGCSE.PKT.R.GRF.01.01 = {
 id: “IGCSE.PKT.R.GRF.01.01”,
 title: “Graph Repair A: Straight Line Control”,
 purpose: “Repair graph-feature blindness”,
 entry_trigger: [“graph_translation <= 2”, “ER07 active”, “ER08 active”],
 materials: [“coordinate reading”, “gradient-intercept drills”, “equation-to-graph strip”],
 lesson_runtime: [
  ”graph talk before graph drawing”,
  ”label key features”,
  ”connect equation to visual behaviour”,
  ”predict before plotting”
 ],
 common_errors: [“ER07”, “ER08”],
 success_criteria: [“student can identify gradient/intercept cleanly”],
 exit_rule: “Equation/graph/table translation stable”
}

9.2 Curve Behaviour and Translation

IGCSE.PKT.R.GRF.02.02 = {
 id: “IGCSE.PKT.R.GRF.02.02”,
 title: “Graph Repair B: Curve Behaviour”,
 purpose: “Repair visual reading of non-linear graphs and transformed graphs”,
 entry_trigger: [“student plots but does not interpret”],
 materials: [“curve sketches”, “transformation overlays”, “reading from graph tasks”],
 common_errors: [“ER07”, “ER13”],
 success_criteria: [“student can explain behaviour, not only draw shape”],
 exit_rule: “Interpretation no longer lags behind plotting”
}

---

10. Geometry Repair Packets

10.1 Angle and Property Chains

IGCSE.PKT.R.GEO.01.01 = {
 id: “IGCSE.PKT.R.GEO.01.01”,
 title: “Geometry Repair A: Angle Chains”,
 purpose: “Restore property-led reasoning in diagrams”,
 entry_trigger: [“diagram_reading <= 2”, “ER09 active”, “ER10 active”],
 materials: [“angle fact strips”, “polygon property maps”, “annotate-before-solve tasks”],
 lesson_runtime: [
  ”mark known facts first”,
  ”name property before calculation”,
  ”build chain visibly”,
  ”state reason beside line”
 ],
 common_errors: [“ER09”, “ER10”, “ER15”],
 success_criteria: [“student stops jumping straight to random arithmetic”],
 exit_rule: “Property chains visible in working”
}

10.2 Similarity, Congruence, Circle Facts

IGCSE.PKT.R.GEO.02.02 = {
 id: “IGCSE.PKT.R.GEO.02.02”,
 title: “Geometry Repair B: Advanced Property Control”,
 purpose: “Stabilise formal geometry in higher-demand questions”,
 entry_trigger: [“student survives basic angle questions but breaks in similarity/circle tasks”],
 materials: [“similarity ratio map”, “circle theorem cards”, “proof-lite geometry tasks”],
 common_errors: [“ER09”, “ER13”],
 success_criteria: [“diagram parsing happens before numerical substitution”],
 exit_rule: “No more random property guessing in advanced geometry set”
}

---

11. Measure and Trigonometry Packets

11.1 Formula-Shape Binding

IGCSE.PKT.R.MTR.01.01 = {
 id: “IGCSE.PKT.R.MTR.01.01”,
 title: “Measure-Trig Repair A: Formula and Units”,
 purpose: “Bind formula choice to shape and unit logic”,
 entry_trigger: [“ER11 active”, “ER12 active”],
 materials: [“area/volume unit ladder”, “shape tagging sheet”, “compound measure tasks”],
 common_errors: [“ER11”, “ER12”, “ER14”],
 success_criteria: [“student names shape, formula, units before solving”],
 exit_rule: “Formula choice becomes deliberate rather than guessed”
}

11.2 Right Triangle Trig

IGCSE.PKT.R.MTR.02.02 = {
 id: “IGCSE.PKT.R.MTR.02.02”,
 title: “Measure-Trig Repair B: SOHCAHTOA Routing”,
 purpose: “Repair angle-side selection in basic trig”,
 entry_trigger: [“student confuses opposite/adjacent/hypotenuse”, “diagram panic active”],
 materials: [“triangle tagging drill”, “select-the-ratio cards”, “non-calc trig warmups”],
 common_errors: [“ER10”, “ER11”, “ER13”],
 success_criteria: [“student can point, name, choose, then compute”],
 exit_rule: “Trig ratio chosen correctly across unseen right-triangle items”
}

11.3 Sine Rule, Cosine Rule, Bearings

IGCSE.PKT.R.MTR.03.03 = {
 id: “IGCSE.PKT.R.MTR.03.03”,
 title: “Measure-Trig Repair C: Extended Trig Control”,
 purpose: “Stabilise Extended-tier trig selection under diagram load”,
 entry_trigger: [“Extended student freezes on non-right-triangle tasks”],
 materials: [“triangle classification map”, “bearing diagram pack”, “sine-cosine selection strip”],
 common_errors: [“ER10”, “ER11”, “ER13”, “ER14”],
 success_criteria: [“student distinguishes when SOHCAHTOA is invalid”],
 exit_rule: “Correct trig family chosen in mixed advanced set”
}

---

12. Data Repair Packets

12.1 Basic Statistics and Probability

IGCSE.PKT.R.DAT.01.01 = {
 id: “IGCSE.PKT.R.DAT.01.01”,
 title: “Data Repair A: Reading and Representing”,
 purpose: “Repair data reading before inference”,
 entry_trigger: [“student can see chart but not extract correct information”],
 materials: [“mean/median/mode drills”, “table reading”, “probability basics”],
 common_errors: [“ER13”, “ER15”],
 success_criteria: [“student reads what is actually shown, not what is imagined”],
 exit_rule: “Basic data extraction stable”
}

12.2 Inference, Cumulative Frequency, Histogram Logic

IGCSE.PKT.R.DAT.02.02 = {
 id: “IGCSE.PKT.R.DAT.02.02”,
 title: “Data Repair B: Inference Control”,
 purpose: “Teach the student to reason from represented data”,
 entry_trigger: [“higher/data interpretation questions repeatedly lost”],
 materials: [“cumulative frequency”, “histogram interpretation”, “scatter judgement”],
 common_errors: [“ER13”, “ER15”],
 success_criteria: [“student separates reading from inference”],
 exit_rule: “Interpretation becomes explicit and text-supported”
}

---

13. Transfer Packets

13.1 Mixed Transfer Starter

IGCSE.PKT.T.MIX.01.01 = {
 id: “IGCSE.PKT.T.MIX.01.01”,
 title: “Transfer Builder A”,
 purpose: “Move student from chapter comfort to mixed-paper functioning”,
 entry_trigger: [“single-topic okay, mixed-topic weak”],
 prerequisites: [“at least two engine repairs above usable”],
 materials: [“algebra+graph”, “ratio+mensuration”, “geometry+trig”, “stats+inference”],
 lesson_runtime: [
  ”identify topic blend”,
  ”choose first entry step”,
  ”complete with visible switching between methods”
 ],
 common_errors: [“ER13”, “ER18”],
 success_criteria: [“student stops saying ‘I don’t know this’ when it is actually mixed known content”],
 exit_rule: “Mixed tasks no longer trigger immediate freeze”
}

13.2 Multi-Step Structured Problems

IGCSE.PKT.T.MIX.02.02 = {
 id: “IGCSE.PKT.T.MIX.02.02”,
 title: “Transfer Builder B: Multi-Step Routes”,
 purpose: “Train longer chains of reasoning and persistence”,
 entry_trigger: [“student can do parts but loses the whole route”],
 materials: [“structured long questions”, “checkpoint prompts”, “route-map annotations”],
 common_errors: [“ER13”, “ER17”, “ER18”],
 success_criteria: [“student can preserve route across 3 or more steps”],
 exit_rule: “Longer exam questions become survivable”
}

---

14. Paper-Mode Packets

14.1 Non-Calculator Mode A

IGCSE.PKT.P.NC.01.01 = {
 id: “IGCSE.PKT.P.NC.01.01”,
 title: “Non-Calculator Mode A”,
 board_binding: “Cambridge 0580 / 0980 primary”,
 purpose: “Build slow-clean arithmetic and symbolic endurance for non-calculator papers”,
 entry_trigger: [“Cambridge student”, “noncalc risk >= amber”],
 materials: [“mental arithmetic chain”, “exact form strip”, “fraction and index mix”],
 lesson_runtime: [
  ”no-calc warmup”,
  ”error-tight number work”,
  ”algebra without calculator safety net”,
  ”accuracy review”
 ],
 common_errors: [“ER01”, “ER04”, “ER14”, “ER17”],
 success_criteria: [“student does not panic when calculator removed”],
 exit_rule: “Controlled non-calculator mini-paper stable”
}

14.2 Non-Calculator Mode B

IGCSE.PKT.P.NC.02.02 = {
 id: “IGCSE.PKT.P.NC.02.02”,
 title: “Non-Calculator Mode B: Timed Survival”,
 purpose: “Condition the student for real paper pacing”,
 entry_trigger: [“student accurate but too slow”],
 materials: [“timed sections”, “pace checkpoints”, “error review sheet”],
 common_errors: [“ER17”, “ER18”],
 success_criteria: [“pace improves without accuracy collapse”],
 exit_rule: “Student survives a realistic timed no-calc section”
}

14.3 Calculator Control

IGCSE.PKT.P.CC.01.01 = {
 id: “IGCSE.PKT.P.CC.01.01”,
 title: “Calculator Control Mode”,
 board_binding: “All”,
 purpose: “Teach correct setup, bracket use, mode discipline, and sense checking”,
 entry_trigger: [“ER16 active”, “answers look absurd but accepted blindly”],
 materials: [“calculator mode checks”, “bracket drills”, “estimate-then-calc strips”],
 common_errors: [“ER14”, “ER16”],
 success_criteria: [“student predicts rough answer before trusting display”],
 exit_rule: “Calculator becomes tool, not master”
}

---

15. Mark Capture Packets

15.1 Working Visibility

IGCSE.PKT.M.PR.01.01 = {
 id: “IGCSE.PKT.M.PR.01.01”,
 title: “Mark Capture A: Show the Method”,
 purpose: “Prevent answer-only losses”,
 entry_trigger: [“ER15 active”, “student often right-thinking but under-shows”],
 materials: [“line-by-line layout model”, “statement-answer pairs”, “unit checkpoint strip”],
 lesson_runtime: [
  ”rewrite hidden solution visibly”,
  ”one move per line”,
  ”circle final answer”,
  ”mark-scheme comparison”
 ],
 success_criteria: [“visible method appears consistently”],
 exit_rule: “Student writes for marks, not only for self”
}

15.2 Accuracy and Final Form

IGCSE.PKT.M.PR.01.02 = {
 id: “IGCSE.PKT.M.PR.01.02”,
 title: “Mark Capture B: Final Form Discipline”,
 purpose: “Repair exact form, units, significant figures, and rounding control”,
 entry_trigger: [“ER12 active”, “ER14 active”],
 materials: [“rounding traps”, “unit checks”, “exact vs decimal form strip”],
 success_criteria: [“student reads output requirement before finalising answer”],
 exit_rule: “Late-stage mark leakage falls sharply”
}

---

16. Mock and Endurance Packets

16.1 Timed Mini-Paper Conditioning

IGCSE.PKT.X.EN.01.01 = {
 id: “IGCSE.PKT.X.EN.01.01”,
 title: “Endurance Conditioning A”,
 purpose: “Condition the student to preserve quality through time”,
 entry_trigger: [“ER17 active”],
 materials: [“timed mini-paper”, “checkpoint script”, “fatigue notes”],
 lesson_runtime: [
  ”set start-time intention”,
  ”midpoint reset”,
  ”late-paper control cue”,
  ”postmortem by loss bucket”
 ],
 success_criteria: [“late-paper collapse reduced”],
 exit_rule: “Student no longer loses most marks in final section”
}

16.2 Full Mock Review

IGCSE.PKT.X.EN.02.02 = {
 id: “IGCSE.PKT.X.EN.02.02”,
 title: “Mock Review Protocol”,
 purpose: “Turn mock results into routing decisions”,
 entry_trigger: [“after every mock”],
 materials: [“loss bucket sheet”, “error coding sheet”, “retier review notes”],
 lesson_runtime: [
  ”code each lost mark”,
  ”separate knowledge from execution loss”,
  ”assign next packets”,
  ”set next 2-week plan”
 ],
 success_criteria: [“mock produces action, not emotion only”],
 exit_rule: “At least one specific packet route generated from mock”
}

---

17. Memory Packets

17.1 Formula and Relation Recall

IGCSE.PKT.Y.RC.01.01 = {
 id: “IGCSE.PKT.Y.RC.01.01”,
 title: “Memory Packet A: Formula Retrieval”,
 purpose: “Strengthen fast access to required relationships”,
 entry_trigger: [“ER11 active”, “student says ‘I know it when I see it'”],
 materials: [“formula cards”, “blank recall sheet”, “retrieve-apply mini tasks”],
 success_criteria: [“formula recall faster and cleaner”],
 exit_rule: “Student retrieves without heavy prompting”
}

17.2 Mixed Recall Cycling

IGCSE.PKT.Y.RC.02.02 = {
 id: “IGCSE.PKT.Y.RC.02.02”,
 title: “Memory Packet B: Spaced Mixed Recall”,
 purpose: “Prevent old topics from decaying while new ones are repaired”,
 entry_trigger: [“improvement in one area causes another to decay”],
 materials: [“7-day rotating recall strip”],
 success_criteria: [“old floors remain stable while route advances”],
 exit_rule: “Student retains repaired engines over time”
}

---

18. Packet Routing Engine

ROUTER.V1 = {

 if new_student == true -> assign(“IGCSE.PKT.E.MIX.00.01”),

 if ER01 or ER02 or ER03 dominant -> assign(“IGCSE.PKT.R.NUM.01.01”),

 if ER04 or ER05 dominant -> assign(“IGCSE.PKT.R.ALG.01.01”),

 if ER06 dominant -> assign(“IGCSE.PKT.R.ALG.01.02”),

 if ER07 or ER08 dominant -> assign(“IGCSE.PKT.R.GRF.01.01”),

 if ER09 or ER10 dominant -> assign(“IGCSE.PKT.R.GEO.01.01”),

 if ER11 or ER12 dominant and question_family in [mensuration, trig]
  -> assign(“IGCSE.PKT.R.MTR.01.01”),

 if data_inference_breaks == true -> assign(“IGCSE.PKT.R.DAT.02.02”),

 if mixed_questions_fail and chapter_questions_pass
  -> assign(“IGCSE.PKT.T.MIX.01.01”),

 if board == “Cambridge 0580” and noncalc_risk >= amber
  -> assign(“IGCSE.PKT.P.NC.01.01”),

 if calc_setup_error == true
  -> assign(“IGCSE.PKT.P.CC.01.01”),

 if method_visibility_low == true
  -> assign(“IGCSE.PKT.M.PR.01.01”),

 if endurance_drop_high == true
  -> assign(“IGCSE.PKT.X.EN.01.01”)

}

ROUTER.RULE = “Maximum 3 active packets at one time unless the student is in pre-exam conditioning.”

---

19. Packet Stack Templates

19.1 Fragile Foundation Stack

STACK.FRAGILE_FOUNDATION = [
 ”IGCSE.PKT.E.MIX.00.01″,
 ”IGCSE.PKT.R.NUM.01.01″,
 ”IGCSE.PKT.R.ALG.01.01″,
 ”IGCSE.PKT.M.PR.01.01″,
 ”IGCSE.PKT.Y.RC.02.02″
]

19.2 False Safe Student Stack

STACK.FALSE_SAFE = [
 ”IGCSE.PKT.E.MIX.00.01″,
 ”IGCSE.PKT.T.MIX.01.01″,
 ”IGCSE.PKT.T.MIX.02.02″,
 ”IGCSE.PKT.X.EN.01.01″,
 ”IGCSE.PKT.X.EN.02.02″
]

19.3 Calculator-Dependent Cambridge Stack

STACK.CALC_DEPENDENT_CAMBRIDGE = [
 ”IGCSE.PKT.E.MIX.00.01″,
 ”IGCSE.PKT.P.NC.01.01″,
 ”IGCSE.PKT.P.NC.02.02″,
 ”IGCSE.PKT.M.PR.01.02″,
 ”IGCSE.PKT.X.EN.01.01″
]

19.4 Extended Trig-Geometry Stress Stack

STACK.EXTENDED_TRIG_GEOMETRY = [
 ”IGCSE.PKT.R.GEO.02.02″,
 ”IGCSE.PKT.R.MTR.02.02″,
 ”IGCSE.PKT.R.MTR.03.03″,
 ”IGCSE.PKT.T.MIX.02.02″
]

---

20. 4-Week Runtime Template

RUNTIME.4WEEK.TEMPLATE = {

 WEEK1: {
  goal: “diagnose and stabilise”,
  packets: [“Entry”, “one repair”, “mark capture”],
  measurement: “baseline error profile”
 },

 WEEK2: {
  goal: “repair dominant engine”,
  packets: [“repair”, “memory”, “paper micro-drill”],
  measurement: “error frequency falls”
 },

 WEEK3: {
  goal: “add transfer”,
  packets: [“repair”, “transfer”, “presentation”],
  measurement: “mixed questions less threatening”
 },

 WEEK4: {
  goal: “test under pressure”,
  packets: [“paper mode”, “endurance”, “review”],
  measurement: “timed performance trend known”
 }

}

---

21. Sample Tutor Lesson Scripts

21.1 Repair Script

SCRIPT.REPAIR = [
 ”State the exact break clearly.”,
 ”Model one correct line slowly.”,
 ”Make the student narrate the next line.”,
 ”Reduce support gradually.”,
 ”Switch to exam-style wording before ending.”,
 ”Log the dominant error code.”
]

21.2 Transfer Script

SCRIPT.TRANSFER = [
 ”Ask: what topic families are inside this question?”,
 ”Ask: what is the first safe entry point?”,
 ”Prevent random jumping.”,
 ”Make the student mark where topic A becomes topic B.”,
 ”Check whether panic comes from language, diagram, or algebra.”
]

21.3 Mock Review Script

SCRIPT.MOCK_REVIEW = [
 ”Do not begin with marks; begin with losses.”,
 ”Code each loss bucket.”,
 ”Separate ‘did not know’ from ‘did not show’.”,
 ”Find the most expensive repeated error.”,
 ”Assign next packet immediately.”
]

---

22. Homework Prescription Rules

HOMEWORK.PRESCRIBER = {

 if active_packet_family == “REPAIR”
  -> homework_ratio = {repair:60, recall:20, mixed:10, presentation:10},

 if active_packet_family == “TRANSFER”
  -> homework_ratio = {repair:20, recall:20, mixed:40, paper_mode:20},

 if active_packet_family == “PAPERMODE”
  -> homework_ratio = {paper_mode:50, repair:20, presentation:15, review:15},

 if active_packet_family == “MOCK”
  -> homework_ratio = {review:30, targeted_repair:40, timed_set:30}

}

HOMEWORK.RULE = “Homework must continue the active packet, not become a random worksheet pile.”

---

23. Progress Review Rules

PROGRESS.REVIEW = {
 review_cycle: “every 2 to 4 weeks”,
 must_check: [
  ”dominant error frequency”,
  ”paper-mode stability”,
  ”visible working quality”,
  ”fatigue trend”,
  ”tier-fit”
 ],
 promote_packet_when: [
  ”two consecutive clean performances”,
  ”student explains method independently”,
  ”old error no longer reopens under mild pressure”
 ],
 hold_packet_when: [
  ”error reappears in mixed questions”,
  ”student collapses without prompts”,
  ”presentation still hides thinking”
 ],
 downgrade_or_repair_again_when: [
  ”speed increased but accuracy collapsed”,
  ”mock shows same old error is still expensive”
 ]
}

---

24. Tier Review Layer

TIER.REVIEW = {

 Cambridge_0580 = {
  questions: [
   ”Can the student survive both non-calculator and calculator demands?”,
   ”Is Extended ambition supported by stable algebra, graph, geometry, and trig control?”,
   ”Is Core now capping the student unfairly?”
  ]
 },

 Pearson_4MA1 = {
  questions: [
   ”Is Foundation now below ceiling?”,
   ”Can Higher be sustained across two full papers?”,
   ”Is formula-sheet availability disguising weak retrieval or not?”
  ]
 }

}

---

25. Control Panel Minimal View

CONTROL_PANEL.MIN = {
 board: “”,
 tier: “”,
 dominant_packet_1: “”,
 dominant_packet_2: “”,
 dominant_packet_3: “”,
 highest_cost_error: “”,
 paper_mode_risk: “”,
 fatigue_risk: “”,
 mark_capture_risk: “”,
 next_review_date: “”
}

---

26. Full Tutor Log Template

FORM.TUTOR.LOG = {
 student_id: “”,
 date: “”,
 board: “”,
 tier: “”,
 lesson_goal: “”,
 active_packets: [],
 questions_attempted: 0,
 questions_correct: 0,
 dominant_error: “”,
 secondary_error: “”,
 paper_mode_today: “”,
 pace_today: “”,
 confidence_state: “”,
 homework_assigned: [],
 state_shift: “”,
 next_packet_decision: “”
}

---

27. Canonical Operational Doctrine

DOCTRINE = {
 D1: “Board first”,
 D2: “Tier reality before ego”,
 D3: “Repair before acceleration”,
 D4: “Mixed transfer before false confidence”,
 D5: “Non-calculator and calculator are different training states in Cambridge”,
 D6: “Formula knowledge, retrieval speed, and visible method all matter”,
 D7: “A mock is useful only if it changes routing”,
 D8: “The most expensive repeated error should be treated first”
}

---

28. Canonical Lock

CANONICAL_LOCK = {
 CL1: “Packets are state interventions, not content bundles only.”,
 CL2: “Every packet must have entry trigger, success criteria, and exit rule.”,
 CL3: “IGCSE Mathematics tutorial becomes effective when packet assignment matches the student’s real bottleneck.”,
 CL4: “Cambridge and Pearson may share topic families, but their paper logic must remain board-bound.”,
 CL5: “The packet system exists to reduce execution leakage and improve route stability.”
}

eduKateSG Learning System | Control Tower, Runtime, and Next Routes

This article is one node inside the wider eduKateSG Learning System.

At eduKateSG, we do not treat education as random tips, isolated tuition notes, or one-off exam hacks. We treat learning as a living runtime:

state -> diagnosis -> method -> practice -> correction -> repair -> transfer -> long-term growth

That is why each article is written to do more than answer one question. It should help the reader move into the next correct corridor inside the wider eduKateSG system: understand -> diagnose -> repair -> optimize -> transfer. Your uploaded spine clearly clusters around Education OS, Tuition OS, Civilisation OS, subject learning systems, runtime/control-tower pages, and real-world lattice connectors, so this footer compresses those routes into one reusable ending block.

Start Here

• Education OS | How Education Works
• Tuition OS | eduKateOS & CivOS
• Civilisation OS
• How Civilization Works
• CivOS Runtime Control Tower

Learning Systems

• The eduKate Mathematics Learning System
• Learning English System | FENCE by eduKateSG
• eduKate Vocabulary Learning System
• Additional Mathematics 101

Runtime and Deep Structure

• Human Regenerative Lattice | 3D Geometry of Civilisation
• Civilisation Lattice
• Advantages of Using CivOS | Start Here Stack Z0-Z3 for Humans & AI

Real-World Connectors

• Family OS | Level 0 Root Node
• Bukit Timah OS
• Punggol OS
• Singapore City OS

Subject Runtime Lane

• Math Worksheets
• How Mathematics Works PDF
• MathOS Runtime Control Tower v0.1
• MathOS Failure Atlas v0.1
• MathOS Recovery Corridors P0 to P3

How to Use eduKateSG

If you want the big picture -> start with Education OS and Civilisation OS
If you want subject mastery -> enter Mathematics, English, Vocabulary, or Additional Mathematics
If you want diagnosis and repair -> move into the CivOS Runtime and subject runtime pages
If you want real-life context -> connect learning back to Family OS, Bukit Timah OS, Punggol OS, and Singapore City OS

Why eduKateSG writes articles this way

eduKateSG is not only publishing content.
eduKateSG is building a connected control tower for human learning.

That means each article can function as:

• a standalone answer,
• a bridge into a wider system,
• a diagnostic node,
• a repair route,
• and a next-step guide for students, parents, tutors, and AI readers.

eduKateSG.LearningSystem.Footer.v1.0

TITLE: eduKateSG Learning System | Control Tower / Runtime / Next Routes

FUNCTION:
This article is one node inside the wider eduKateSG Learning System.
Its job is not only to explain one topic, but to help the reader enter the next correct corridor.

CORE_RUNTIME:
reader_state -> understanding -> diagnosis -> correction -> repair -> optimisation -> transfer -> long_term_growth

CORE_IDEA:
eduKateSG does not treat education as random tips, isolated tuition notes, or one-off exam hacks.
eduKateSG treats learning as a connected runtime across student, parent, tutor, school, family, subject, and civilisation layers.

PRIMARY_ROUTES:
1. First Principles
   - Education OS
   - Tuition OS
   - Civilisation OS
   - How Civilization Works
   - CivOS Runtime Control Tower

2. Subject Systems
   - Mathematics Learning System
   - English Learning System
   - Vocabulary Learning System
   - Additional Mathematics

3. Runtime / Diagnostics / Repair
   - CivOS Runtime Control Tower
   - MathOS Runtime Control Tower
   - MathOS Failure Atlas
   - MathOS Recovery Corridors
   - Human Regenerative Lattice
   - Civilisation Lattice

4. Real-World Connectors
   - Family OS
   - Bukit Timah OS
   - Punggol OS
   - Singapore City OS

READER_CORRIDORS:
IF need == "big picture"
THEN route_to = Education OS + Civilisation OS + How Civilization Works

IF need == "subject mastery"
THEN route_to = Mathematics + English + Vocabulary + Additional Mathematics

IF need == "diagnosis and repair"
THEN route_to = CivOS Runtime + subject runtime pages + failure atlas + recovery corridors

IF need == "real life context"
THEN route_to = Family OS + Bukit Timah OS + Punggol OS + Singapore City OS

CLICKABLE_LINKS:
Education OS:
Education OS | How Education Works — The Regenerative Machine Behind Learning


Tuition OS:
Tuition OS (eduKateOS / CivOS)


Civilisation OS:
Civilisation OS


How Civilization Works:
Civilisation: How Civilisation Actually Works


CivOS Runtime Control Tower:
CivOS Runtime / Control Tower (Compiled Master Spec)


Mathematics Learning System:
The eduKate Mathematics Learning System™


English Learning System:
Learning English System: FENCE™ by eduKateSG


Vocabulary Learning System:
eduKate Vocabulary Learning System


Additional Mathematics 101:
Additional Mathematics 101 (Everything You Need to Know)


Human Regenerative Lattice:
eRCP | Human Regenerative Lattice (HRL)


Civilisation Lattice:
The Operator Physics Keystone


Family OS:
Family OS (Level 0 root node)


Bukit Timah OS:
Bukit Timah OS


Punggol OS:
Punggol OS


Singapore City OS:
Singapore City OS


MathOS Runtime Control Tower:
MathOS Runtime Control Tower v0.1 (Install • Sensors • Fences • Recovery • Directories)


MathOS Failure Atlas:
MathOS Failure Atlas v0.1 (30 Collapse Patterns + Sensors + Truncate/Stitch/Retest)


MathOS Recovery Corridors:
MathOS Recovery Corridors Directory (P0→P3) — Entry Conditions, Steps, Retests, Exit Gates


SHORT_PUBLIC_FOOTER:
This article is part of the wider eduKateSG Learning System.
At eduKateSG, learning is treated as a connected runtime:
understanding -> diagnosis -> correction -> repair -> optimisation -> transfer -> long-term growth.

Start here:
Education OS
Education OS | How Education Works — The Regenerative Machine Behind Learning


Tuition OS
Tuition OS (eduKateOS / CivOS)


Civilisation OS
Civilisation OS


CivOS Runtime Control Tower
CivOS Runtime / Control Tower (Compiled Master Spec)


Mathematics Learning System
The eduKate Mathematics Learning System™


English Learning System
Learning English System: FENCE™ by eduKateSG


Vocabulary Learning System
eduKate Vocabulary Learning System


Family OS
Family OS (Level 0 root node)


Singapore City OS
Singapore City OS


CLOSING_LINE:
A strong article does not end at explanation.
A strong article helps the reader enter the next correct corridor.

TAGS:
eduKateSG
Learning System
Control Tower
Runtime
Education OS
Tuition OS
Civilisation OS
Mathematics
English
Vocabulary
Family OS
Singapore City OS