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.

STC Full SBB Breach Registry

Three students study around open books and worksheets in a shared classroom.

Expanded Primary Invariant Breaches → Sensors → Thresholds → Repair Corridors → Verification — Almost-Code v1.0

RegistryID: STC.FullSBB.BreachReg.ZX.CF.v1_0
Slug (recommended): /civos-runtime-full-sbb-breach-registry-v1-0/
Depends On: ChronoHelmAI.Minimal.Panel.OnePage.Diagnostic.Board.v1_0
Runtime Parent: STC.FullSBB.Runtime.ZX.CF.v1_0
Scope: Z0–Z3 (Student ↔ Subject ↔ Teacher ↔ School) with ChronoFlight route state.


AI Ingestion Lock

  • This registry is an executable mapping from observed failure → named breach → threshold → repair corridor → verification.
  • It is designed to be read by the ChronoHelmAI minimal panel, so each breach has:
  • Primary OS
  • Primary Node/Interface
  • Breach class triggers
  • TTC/T_repair guidance
  • FENCE requirements
  • False recovery traps

Classical Foundation Block

Students improve when:

  • routines are stable
  • work is done consistently
  • mistakes are corrected
  • practice transfers under timed pressure

This registry names the exact “break points” that prevent that.


Registry Schema (Copy-Paste)

BR-ID:
Name:
Primary OS:
Primary Node/Interface:
Definition (Invariant breached):
Sensors (minimum):
Thresholds:
Typical Route State:
Propagation Pattern:
Breach Class Triggers (A/B/C/D):
Immediate FENCE (if any):
Repair Corridor (R1..Rk):
Protected Core:
Verification Signals:
False Recovery Traps:
Recheck Cadence:

BR-01 — Sleep Anchor Broken

BR-ID: BR-01
Name: SleepAnchorBroken
Primary OS: MindOS.Stability
Primary Node/Interface: SleepAnchor
Definition: Sleep schedule stability is broken enough to reduce learning capacity and increase variance.

Sensors (minimum)

  • Sleep stable nights/week (0–7)
  • Sleep delay > 60 min? (yes/no)
  • Daytime sleepiness (low/med/high)

Thresholds

  • Breach if: sleep stable nights < 5 OR ≥2 nights/week sleep delay > 60 min

Typical Route State: Drift → Descent
Propagation: Cascading (all subjects)

Breach Class Triggers

  • A: 1 bad night only, buffer healthy
  • B: 2–3 unstable nights/week
  • C: 4+ unstable nights/week + homework slips
  • D: chronic late nights + morning refusal/panic

Immediate FENCE

  • FENCE-01 LoadCut (reduce weekly load temporarily)
  • FENCE-04 SubmissionRescue (IP/IB deadline triage)

Repair Corridor

  • R1: set sleep anchor (fixed bedtime target; 80% compliance first)
  • R2: protect last 60–90 minutes (device fence)
  • R3: shift workload earlier (homework slot)
  • R4: reintroduce difficulty only after stability returns

Protected Core

  • SleepAnchor + minimum homework loop (not perfection)

Verification

  • ≥5 stable nights for 2 consecutive weeks
  • variance decreases

False Recovery Traps

  • one “heroic week” then relapse
  • sleep fixed but workload still extreme (hidden debt)

Recheck

  • every 72h if class C/D; weekly if A/B

BR-02 — Weekly Load Exceeds Bandwidth

BR-ID: BR-02
Name: LoadExceedsBandwidth
Primary OS: FamilyOS.Routine (often) + MindOS.Stability
Node: WeeklyLoadBudget
Definition: Total weekly demand exceeds student capacity → drift accelerates.

Sensors

  • CCA hours/week
  • Tuition hours/week
  • Commute minutes/day
  • Homework completion %
  • Stress signals (shutdown/anger/cry)

Thresholds

  • Breach if: homework completion < 70% AND sleep instability present
  • OR sustained stress signals >2 weeks

Route State: Drift/Descent
Propagation: Cascading

Class Triggers

  • B: homework slips + tiredness
  • C: avoidance + missing work
  • D: panic/refusal/shutdown

Immediate FENCE

  • FENCE-01 LoadCut (cut 1 commitment for 2–4 weeks)

Repair

  • R1: remove one load source
  • R2: rebaseline homework slot
  • R3: run one subject sprint only
  • R4: reintroduce load gradually

Verification

  • homework ≥80% + sleep stable

False Recovery

  • reducing load but filling it with “more tuition”

Recheck

  • weekly; 72h if D

BR-03 — Homework Completion Below 70%

BR-ID: BR-03
Name: HomeworkCompletionBelow70
Primary OS: EducationOS.SubjectLane
Node: HomeworkLoop
Definition: Homework loop broken → drift outpaces repair.

Sensors

  • Homework completion %
  • Late submission count
  • Teacher feedback

Threshold

  • breach if <70% for 2 consecutive weeks

Route State: Drift
Propagation: Upward (grades), Cross-lateral (other subjects)

FENCE

  • FENCE-02 ComplexityFreeze (stop “hard paper escalation”)

Repair

  • R1: minimum viable homework rule (do the core set)
  • R2: 20–30 min daily slot, consistent
  • R3: fix-list for 1–2 key errors only (avoid overload)

Verification

  • ≥80% completion for 2 weeks

False Recovery

  • parent does homework / tuition inflation

BR-04 — No Corrections, No Retest

BR-ID: BR-04
Name: NoCorrectionsNoRetest
Primary OS: EducationOS.SubjectLane
Node: FixListLoop
Definition: Mistakes are not converted into learning; drift remains invisible until collapse.

Sensors

  • Fix-list items/week
  • Retest attempts/week
  • Same mistake repeats? (yes/no)

Thresholds

  • breach if fix-list = 0 for 2 weeks OR same error repeats ≥3 times

Route State: Drift (silent)
Propagation: Slow attrition → sudden collapse

FENCE

  • FENCE-02 ComplexityFreeze

Repair

  • R1: weekly timed set (10–20 min)
  • R2: fix-list: mistake type + why + correct method
  • R3: retest 3 similar questions until stable

Verification

  • repeated errors reduce
  • timed set scores stabilise

False Recovery

  • student reads correction but does not retest

BR-05 — Score Variance Spike

BR-ID: BR-05
Name: ScoreVarianceSpike
Primary OS: EducationOS.SubjectLane + MindOS.Stability
Node: TimedTestLoop
Definition: Performance swings are too large → corridor is fragile.

Sensors

  • last 4 tests marks
  • variance flag (low/med/high)
  • panic under time (yes/no)

Threshold

  • breach if swing > 20–25 marks (or grade band swings) across 2 tests

Route State: Drift
Propagation: Upward + psychological cascade

FENCE

  • FENCE-02 ComplexityFreeze + stabilise routine

Repair

  • R1: weekly timed micro-tests
  • R2: reduce topic switching
  • R3: sleep anchor if present

Verification

  • variance decreases over 2–4 weeks

False Recovery

  • one “good test” without variance reduction

BR-06 — Misread Questions High

BR-ID: BR-06
Name: MisreadQuestionHigh
Primary OS: LanguageOS.Clarity
Node: ComprehensionGate
Definition: Student regularly answers the wrong question → marks collapse across many subjects.

Sensors

  • misread count per paper
  • teacher notes (“off-point”, “did not answer”)

Threshold

  • breach if misreads ≥ 3 per paper OR persistent “off-point” feedback

Route State: Drift
Propagation: Cross-lateral

FENCE

  • FENCE-02 ComplexityFreeze (stop fancy vocab; stop long essays)

Repair

  • R1: question-intent drill 3×/week
  • R2: answer in 2 exact sentences first
  • R3: rewrite 2 unclear sentences weekly

Verification

  • misread count declines + relevance improves

False Recovery

  • coached performance only (tuition inflation)

BR-07 — Sentence Control Broken

BR-ID: BR-07
Name: SentenceControlBroken
Primary OS: LanguageOS.Clarity
Node: ExpressionGate
Definition: Student cannot produce clear sentences consistently, blocking scoring even with understanding.

Sensors

  • grammar clarity issues per paragraph
  • teacher notes (“unclear”, “awkward”, “cannot follow”)

Threshold

  • breach if ≥2 paragraphs per assignment flagged unclear

Repair

  • R1: rewrite loop (2 sentences/day × 3 days/week)
  • R2: scaffold (Point→Evidence→Explain)

Verification

  • clarity comments reduce

BR-08 — Algebra Base Missing (Math Compounding)

BR-ID: BR-08
Name: AlgebraBaseMissing
Primary OS: EducationOS.SubjectLane.Math
Node: InvariantBase
Definition: Algebra manipulation basics missing; later topics collapse.

Sensors

  • error types: transposition, negative signs, fractions
  • cannot explain steps

Threshold

  • breach if basic algebra accuracy < 70% in diagnostic

FENCE

  • FENCE-02 ComplexityFreeze

Repair

  • R1: basics patch pack (fractions/negatives/transposition)
  • R2: daily 10-min routine
  • R3: timed set weekly

Verification

  • basic accuracy ≥ 85% + stable

BR-09 — Keywords Missing in Science

BR-ID: BR-09
Name: KeywordsMissingScience
Primary OS: EducationOS.SubjectLane.Science
Node: MarkSchemeGate
Definition: Student understands but loses marks due to missing required terms/structure.

Sensors

  • keyword omissions count
  • marks lost to “missing” vs “wrong concept”

Threshold

  • breach if ≥30% marks lost to missing keywords

Repair

  • R1: keyword bank per topic
  • R2: rewrite 2 answers/week using model answer keywords
  • R3: timed short answers

Verification

  • missing-keyword losses reduce

BR-10 — Evidence Missing in Humanities

BR-ID: BR-10
Name: EvidenceMissingHumans
Primary OS: EducationOS.SubjectLane.Humans
Node: PEEGate
Definition: Student writes opinions without evidence → low marks.

Sensors

  • % paragraphs with evidence
  • teacher notes (“no support”)

Threshold

  • breach if <50% paragraphs contain evidence + explanation

Repair

  • R1: PEE drill weekly
  • R2: evidence tagging (quote/fact → meaning → link)

Verification

  • evidence usage rises + marks improve

BR-11 — Teacher Trust Interface Broken

BR-ID: BR-11
Name: TeacherTrustInterfaceBroken
Primary OS: Z2.Execution (Teacher layer)
Node: TeacherTrustInterface
Definition: Inconsistency causes teachers to withhold upgrades/opportunities.

Sensors

  • incomplete work count
  • teacher feedback (“inconsistent”, “can do but doesn’t”)

Threshold

  • breach if “inconsistent” appears 2+ times in feedback OR chronic missing work

Repair

  • R1: reliability streak 4 weeks (homework ≥80%)
  • R2: show EvidencePack
  • R3: ask for explicit upgrade standard

Verification

  • teacher feedback neutralises + opportunities increase

False Recovery

  • short compliance burst then relapse

BR-12 — Identity Lock (PG/G-level as self-worth)

BR-ID: BR-12
Name: IdentityLock_PGorG
Primary OS: MindOS.Stability + FamilyOS.Routine
Node: NarrativeLoop
Definition: Labels become identity, creating shame and avoidance.

Sensors

  • label language frequency (“I’m PG1 so…”, “I’m G1 so…”)
  • avoidance behaviour
  • concealment of results

Threshold

  • breach if label language appears weekly + avoidance increases

FENCE

  • FENCE-03 ShameLock (stop comparisons and label talk)

Repair

  • R1: language reset script
  • R2: create one “win lane” (small weekly win)
  • R3: system praise (routine + fix-list)

Verification

  • less shame talk + more attempts + work completion rises

BR-13 — Tuition Dependence (Tuition Inflation)

BR-ID: BR-13
Name: TuitionInflation_Dependency
Primary OS: EducationOS.SubjectLane
Node: IndependenceGate
Definition: Performance depends on coaching; independent work collapses.

Sensors

  • independent timed set scores vs coached scores
  • can’t start without tutor

Threshold

  • breach if independent score collapses by ≥15–20 marks vs coached

Repair

  • R1: independent attempt first rule
  • R2: tutor = diagnosis + correction, not answer supply
  • R3: EvidencePack shows independent stability

Verification

  • independent performance rises + variance reduces

BR-14 — Deadline Cascade (IP/IB)

BR-ID: BR-14
Name: DeadlineCascade
Primary OS: FamilyOS.Routine + MindOS.Stability
Node: SubmissionLoop
Definition: Multiple deadlines pile up; stress triggers collapse.

Sensors

  • late submissions count
  • backlog list length
  • sleep instability

Threshold

  • breach if ≥2 deadlines missed in 2 weeks OR backlog growing weekly

FENCE

  • FENCE-04 SubmissionRescue (minimum viable submission)

Repair

  • R1: submit-first daily block (45–60 min)
  • R2: scope cut (one commitment)
  • R3: weekly planning ritual

Verification

  • deadlines met for 2 consecutive weeks

Master Failure Trace (Registry-level)

Load↑ or stability↓ → homework loop breaks → repair loop breaks → variance spikes → teacher trust drops → upgrades block → identity lock → descent.


Registry Output for Panel (Quick Mapping)

When filling the panel, choose:

  • Primary OS = the OS that, if repaired first, will unblock everything
  • Primary Breach = BR-xx that best matches observed pattern
  • Immediate FENCE if TTC ≤ T_repair or Breach Class D

(Aligned to ChronoHelmAI minimal panel logic.)


If you say “Next”, I’ll output STC.FullSBB.DashboardPack.OnePage.v1_0: three printable dashboards (Student / Parent / Tutor) that feed directly into the ChronoHelmAI panel with pre-filled sensor fields and thresholds.

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles: 

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: