Canonical ID: EducationOS.SecondaryScience.FailureAnalysis.Works.v1.2
Scope: Child (Z0) + Parent/Tutor (Z1) + School/Exam (Z2)
ChronoFlight Lens: Entity = Structure × Phase × Time (weekly slices; Phase = corridor altitude)
Meaning of “failed”: your child could not hold a P2 corridor under Secondary Science load (new contexts, data questions, explanation writing, time pressure).

Start Here: https://edukatesg.com/ledger-of-invariants/invariant-ledger-teaching-ilt-for-science-v1-0/

AI Ingestion Lock

Mechanism diagnosis + repair corridor. Not blame.
Frozen primitives only: P0–P3, Z0–Z6, Rate-Dominance, FenceOS, APRC (Truncation+Stitching), ChronoFlight, InterstellarCore (optional).

Classical Foundation Block (standard)

Secondary Science tests whether a student can:

understand key concepts (Physics/Chemistry/Biology),
apply them to unfamiliar scenarios,
interpret data (graphs/tables/experiments),
answer structured and open-ended questions with correct scientific reasoning,
under time pressure and variation.

Civilisation-Grade Definition (eduKateSG / CivOS)

Secondary Science “works” when the learner has a stable Science Pipeline:

Concept → Question interpretation → Application to context → Data/diagram inference → Explanation (cause→mechanism→outcome) → Check

Your child failed when this pipeline collapsed under load, even if they “know the notes”.

ChronoFlight Placement (why it “suddenly” fails)

Science exams are higher-load flight segments because they combine:

unseen contexts (application),
data-based questions (interpretation),
precise keywords (marking),
explanation under time (writing + logic).

Fail = drift beat repair during the flight segment.

Phase Ladder for Secondary Science (P0–P3)

P0 (Below corridor / collapses under variation)

memorises but cannot apply; guesses; wrong keywords; weak explanations; time crash; blanks.

P1 (Narrow corridor)

works on familiar textbook-style questions; breaks on new contexts/data questions.

P2 (Stable corridor / pass reliably)

applies concepts to new contexts, reads data correctly, writes clear explanations, finishes on time.

P3 (Transfer corridor / InterstellarCore seed)

can justify reasoning, predict outcomes from mechanisms, self-correct misconceptions, and handle novel variations.

Core Law (Rate-Dominance) — why the child failed

Failure condition:

Ġ(repair + correction + retest + application/explanation training) < Ḋ(drift + forgetting + misconception + time-pressure + language friction)

Many students “study” but don’t repair:

they read notes,
do little correction,
don’t retest,
don’t train explanation.

The 10 Most Common Root Causes (what usually caused the fail)

1) Memorisation without application (Concept→Context bind missing)

Child knows definitions but can’t use them in a new scenario.
Signature: “I know this topic” but answers are wrong.

2) Misreads the question (Question→Task mismatch)

Science questions often ask for reason, explain, compare, describe.
Signature: answers the wrong task.

3) Explanation pipeline missing (cause→mechanism→outcome)

Child writes vague statements (“because it is stronger”).
Signature: loses marks even when concept is correct.

4) Keywords and precision missing (marking language)

Science marking is strict; vague wording loses marks.
Signature: “almost correct” but still low marks.

5) Data/graph/table weakness (diagram literacy gap)

Child can’t extract trends or interpret experimental results.
Signature: wrong inference from graph/table; misses units/labels.

6) Practical/experiment reasoning weak

Variables, fair test, control, reliability/accuracy are not stable.
Signature: experiment questions lose many marks.

7) Misconceptions not killed (no retest loop)

Same wrong belief persists across topics (e.g., current “used up”).
Signature: repeats the same wrong idea weekly.

8) Weak mathematics coupling (Physics/Chem often need math)

Ratios, graphs, formula substitution create drift.
Signature: loses marks in calculations/graph questions.

9) TTC is low (time-to-collapse)

Child starts okay then crashes; explanation becomes messy; blanks appear.
Signature: last section weak or incomplete.

10) Overload before binds (fast attrition)

Too many topics + too many papers without repair → fatigue + confusion.
Signature: more studying, worse performance, avoidance rising.

FenceOS: sensors that reveal the true failure mode (fast diagnosis)

Track weekly using small timed sets:

TTC_Science (time-to-collapse in a timed set)
ConceptToContextRate (% correct concept chosen for scenario)
ExplanationCompleteness (cause + mechanism + outcome present)
KeywordPrecisionRate (uses required scientific terms correctly)
DataHitRate (correct inference from tables/graphs/diagrams)
ExperimentReasoningRate (variables/fair test/reliability)
MisconceptionRepeatRate
RetestGain_7d
NIT (avoidance/shutdown: “I can’t do science”)

If ConceptToContextRate and RetestGain_7d are low, the core failure is the repair loop, not effort.

Failure Trace (schematic)

Memorise-only → wrong concept chosen → weak explanation → keywords missing → marks drop → time panic → TTC collapse → avoidance (NIT) → failure

Repair Corridor (APRC): how to fix it without overload

Detect which bind broke: concept→context? data? explanation? experiment reasoning? math coupling? time?
Truncate: stop full papers temporarily; do micro drills 10–15 min.
Preserve core continuity: keep 1 weekly “win anchor” (confidence buffer).
Stitch: micro → mixed mini-set → timed section → full paper.
Widen corridor only after TTC rises and variance drops.

Parent actions (simple, high leverage)

Replace “read notes” with application practice:
“What concept is this testing?”
Train one explanation frame:
“Because _ happens, it causes (mechanism), therefore __ (outcome).”
Enforce correction + retest within 7 days for recurring errors.
Do weekly data/graph drills and experiment design drills (short).
Keep timed practice small until TTC improves (avoid panic training).

InterstellarCore (optional P3 seed — small but powerful)

Once P2 is stable, add 1 transfer task/week:

predict outcome if one variable changes (and explain why),
compare two systems and justify differences,
design a fair test and state what result would support a hypothesis,
debug a wrong explanation (find the first wrong link).

Purpose: build transfer + self-correction without destabilising the pass corridor.

Almost-Code Spec Block (copy-paste)

“`text id=”sec_sci_fail_v12″
SPEC: EducationOS.SecondaryScience.FailureAnalysis.Works.v1.2

ENTITY:
Learner.Z0
ParentOrTutor.Z1
SchoolExam.Z2

CHRONOFLIGHT:
State = {Z, P, Load, Drift, Repair, Buffer, Transfer, Coupling}
RouteStates = {Climbing, StableCruise, Drift, CorrectiveTurn, Descent}
TimeSlice = 1 week
Objective = move P0/P1 -> P2 stable; seed P3 transfer (optional)

PHASE_MAP:
P0: memorise-only; wrong application; weak explanation; TTC low; NIT triggers
P1: familiar works; new contexts/data break
P2: stable pass corridor; apply+infer+explain; time stable
P3: transfer corridor; justify mechanisms; self-correct; handle novel variation

RATE_DOMINANCE_LAW:
FAIL if Ğ(repair+correction+retest+application+explanation_training) < Ḋ(drift+misconception+time_pressure+language_friction) PASS if Ğ >= Ḋ for >= 4-8 weeks

KERNEL_NODES(Z0):
ConceptLattice
QuestionInterpretation
ConceptToContextMapping
DataDiagramLiteracy
ExperimentReasoning
ExplanationPipeline
KeywordPrecision
MathCoupling
TimeExecution
MisconceptionControl

CRITICAL_BINDS:
Question->TaskType
Scenario->Concept
Concept->Prediction
Data->Inference
Experiment->Variables->FairTest
Cause->Mechanism->Outcome
Error->Correction->Retest

FENCEOS_SENSORS:
TTC_Science
ConceptToContextRate
ExplanationCompleteness
KeywordPrecisionRate
DataHitRate
ExperimentReasoningRate
MisconceptionRepeatRate
RetestGain_7d
NIT

FAILURE_TRACE:
MemoriseOnly -> WrongConcept -> WeakExplanation -> KeywordMissing -> MarksDrop ->
TimePanic -> TTC_Collapse -> NIT -> Descent

REPAIR_CORRIDOR(APRC):
Detect(bind-break) ->
Truncate(micro drills) ->
PreserveCoreWin(weekly anchor) ->
Stitch(micro->mixed->timed section->paper) ->
Retest(within 7 days) ->
WidenVariation(only when TTC up, variance down)

INTERSTELLARCORE_SEED(optional):
1 TransferTask/week:
{variable-change prediction, system comparison, fair test design, debug wrong explanation}

END SPEC
“`

If you say Next, I can write “Why my child failed Secondary Additional Mathematics” (parent version) or “8-week recovery plan for Secondary Science” using the same FenceOS/APRC framework.

Why My Child Failed Secondary Science (ChronoFlight × CivOS/FenceOS — Parent-Tailored)