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

“`yaml id=”d7k3pr”
PAGE_START
PageID: EDUKATE::MATHOS::RECOVERY_DIR_01
Slug: /mathos-recovery-corridors-p0-to-p3/
Title: MathOS Recovery Corridors Directory (P0→P3) — Entry Conditions, Steps, Retests, Exit Gates
Version: v0.1 (LOCK)
Parent: /mathos-runtime-control-tower-v0-1/
Intent:

  • CivOS-parity “corridor directory” for repairs
  • Every corridor is indexed, runnable, and retestable
  • Maps directly to Failure Atlas patterns + FenceOS triggers
    GrammarLock:
    Place×Lane×Zoom×Role×Type×ID
    Lane: MATH
    CivOSOverlaysAllowed:
  • CORRIDOR_ENTRIES
  • BOX_NEG_VOID_META
  • SENSOR_PANEL_CORRIDORS_DIR

============================================================

BLOCK_01_QUICK_ANSWER (AboveTheFold)
Answer:
This directory lists the official recovery corridors used by MathOS to move learners from P0/P1 instability back to P2 transfer stability and onward to P3 builder behavior. Each corridor has entry conditions (which sensor triggers), exact steps (truncate/stitch), a retest protocol, and an exit gate. Use this like emergency procedures: when a threshold triggers, do the corridor, retest, then re-enter load.

Pointers:

  • thresholds: /mathos-fenceos-threshold-table-v0-1/
  • failure patterns: /mathos-failure-atlas-v0-1/
  • training engine: /how-mathematics-works/

============================================================

BOX_NEG_VOID_META (Directory contract)
DirectoryContract:

  • Each CorridorID is immutable once published
  • Corridors can be versioned forward (v0.2 adds steps), never renamed
  • Every corridor must specify:
    EntryConditions
    Truncate
    Stitch
    Retest
    ExitGate
    LinkedPatterns

============================================================

CORRIDOR_ENTRIES

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_001
Name: P0 Stop-Loss (Immediate Truncation Under Panic)
EntryConditions:

  • (LS high AND SML low) OR panic/blanking
    Truncate:
  • remove timer (48–72h)
  • shrink width: 1 structure only, 3 questions only
  • write meaning line every question
    Stitch:
  • 1 worked example + 2 near copies + 2 independent
  • 1 sanity check per question
    Retest:
  • 3 questions untimed; SML pass (10s meaning test)
    ExitGate:
  • SML stable for 2 sessions
    LinkedPatterns:
  • MATH_FAIL_003 (Meaning Drift)
  • MATH_FAIL_008 (Premature Timing)
    Links:
  • /math-truncation-and-stitching-recovery-protocol/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_002
Name: Meaning-Lock Rebuild (SML Corridor)
EntryConditions:

  • SML low; cannot define symbols/units/asked
    Truncate:
  • forbid solving without a meaning line
    Stitch:
  • for each question:
    (1) meaning line
    (2) structure tag
    (3) 2-line plan
  • add unit checks and sign checks
    Retest:
  • 10 questions: SML present rate >= 90%
    ExitGate:
  • SML present rate >= 90% for 1 week
    LinkedPatterns:
  • MATH_FAIL_003
  • MATH_FAIL_009 (Translation failure)
    Links:
  • /math-as-mindos/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_003
Name: Equivalence Discipline (EQ Corridor)
EntryConditions:

  • illegal moves; cancellations; meaning changes during rewrite
    Truncate:
  • switch to “legal move only” mode; no multi-step expansions
    Stitch:
  • daily:
    5 rewrite drills (produce 3 equivalent forms)
    5 bug-hunts (find first illegal step)
    Retest:
  • 15-item set with 0 illegal moves
    ExitGate:
  • 0 illegal moves across 2 sessions
    LinkedPatterns:
  • MATH_FAIL_006 (Verification collapse)
  • MATH_FAIL_004 (Parsing drift)
    Links:
  • /math-fenceos-stop-loss-for-exam-mistakes/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_004
Name: Transfer Repair (TR Corridor: 3-Skin Packs)
EntryConditions:

  • TR < 0.4 OR collapse on variants
    Truncate:
  • stop blocked repetition
  • stop mixed timed papers
    Stitch:
  • daily:
    2 × (3-skin pack) for one structure family
    structure tag before solving
    1 variant after any correction
    Retest:
  • TR >= 0.7 on 2 different packs
    ExitGate:
  • TR >= 0.7 + CHOICE >= 70%
    LinkedPatterns:
  • MATH_FAIL_001 (Template illusion)
    Links:
  • /math-transfer-test-same-structure-different-skin/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_005
Name: Parsing Grammar Clinic (OOO Corridor)
EntryConditions:

  • E2 parsing dominates; bracket/precedence errors
    Truncate:
  • restrict expressions to small length until stable
    Stitch:
  • daily:
    10 parsing micro-drills
    rewrite with explicit brackets
    explain step order in 1 sentence
    Retest:
  • 10-item parsing test = 0 errors
    ExitGate:
  • 0 errors across 2 sessions
    LinkedPatterns:
  • MATH_FAIL_004
    Links:
  • /order-of-operations-why-people-get-it-wrong/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_006
Name: Strategy Choice Rebuild (CHOICE Corridor)
EntryConditions:

  • CHOICE low; wrong method selection in mixed sets
    Truncate:
  • pause solving until structure tag is written
    Stitch:
  • method cards:
    choose-before-solve + 1 sentence justification
  • interleaving:
    ABCABC sets (3 types) once per day
    Retest:
  • CHOICE >= 70% on 10 mixed items BEFORE solving
    ExitGate:
  • CHOICE >= 80% for 2 weeks
    LinkedPatterns:
  • MATH_FAIL_005
    Links:
  • /math-worksheets/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_007
Name: Oracle Recovery (Verification Corridor)
EntryConditions:

  • ORA absent; FD low; repeated silent errors
    Truncate:
  • enforce “one check per question”
    Stitch:
  • daily:
    5 bug-hunt items (first illegal step)
    2 counterexample attempts (for false statements)
    1 sanity check on every solved question
    Retest:
  • FD >= 70% on 5 bug-hunts + sanity checks present rate >= 80%
    ExitGate:
  • ORA stable for 2 weeks
    LinkedPatterns:
  • MATH_FAIL_006
    Links:
  • /math-fenceos-stop-loss-for-exam-mistakes/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_008
Name: Time Bleed Triage (TB Corridor)
EntryConditions:

  • TB high; late-paper accuracy crash
    Truncate:
  • skip-return rule applied immediately
    Stitch:
  • triage drills:
    mark value -> time budget -> attempt -> park -> return
  • minimal-solve + one check
    Retest:
  • TB_rate decreases over 2 timed sessions
    ExitGate:
  • TB stable at exam pacing
    LinkedPatterns:
  • MATH_FAIL_007
    Links:
  • /math-fenceos-stop-loss-for-exam-mistakes/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_009
Name: Timed Re-Entry Ladder (LS Corridor)
EntryConditions:

  • LS_ratio < 0.75 OR time-trigger panic
    Truncate:
  • drop to Level0 (untimed) immediately
    Stitch:
    Ladder:
    Level0: Untimed (>=85%)
    Level1: Gentle timer (>=80%)
    Level2: Standard pacing (>=75%)
    Level3: Mixed timed (>=70% + CHOICE correct)
    Rule:
    if any LS spike -> revert one level + run RC_002 or RC_004
    Retest:
  • stable LS across 2 sessions at target level
    ExitGate:
  • Level2 stable for 2 weeks
    LinkedPatterns:
  • MATH_FAIL_008
  • MATH_FAIL_012 (shame/avoidance often co-occurs)
    Links:
  • /math-phase-slip-why-students-panic/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_010
Name: Translation Repair (Word→Model Corridor)
EntryConditions:

  • MF low; word problems cannot be started
    Truncate:
  • stop solving; require representation build first
    Stitch:
  • mandatory 3 representations:
    bar model / table / equation
  • define variables + units explicitly
  • do 3 skins: story -> table -> equation
    Retest:
  • 3 word problems with correct setup + units
    ExitGate:
  • MF stable + CHOICE stable
    LinkedPatterns:
  • MATH_FAIL_009
    Links:
  • /math-as-simulation-language/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_011
Name: Representation Stabilization (Fractions↔Decimals Corridor)
EntryConditions:

  • conversion errors; place value drift
    Truncate:
  • enforce one representation per sub-step; no switching mid-step
    Stitch:
  • conversion drills + estimation sanity checks
  • write “reasonableness range” before final answer
    Retest:
  • 10 conversion items >= 90%
    ExitGate:
  • conversion stability + reduced E4 errors
    LinkedPatterns:
  • MATH_FAIL_010
    Links:
  • /math-worksheets/

CORRIDOR_END

CORRIDOR_START
CorridorID: EDUKATE::MATHOS::CORRIDOR::RC_012
Name: Sandbox Safety Reset (rho Corridor)
EntryConditions:

  • rho high OR exploration causes LS spikes
    Truncate:
  • stop Architect sandbox immediately
    Stitch:
  • return to exploit week (Operator/Oracle/Visionary)
  • cap corridors to 1/day with audit + reuse
    Retest:
  • TR stable + LS stable
    ExitGate:
  • rho safe band maintained for 2 weeks
    LinkedPatterns:
  • MATH_FAIL_011
    Links:
  • /math-architect-training-pack-12-week/

CORRIDOR_END

============================================================

SENSOR_PANEL_CORRIDORS_DIR (minimal mapping)
CoreSensors:

  • SML, EQ, TR, LS, CHOICE, ORA, FD, TB, MF, rho
    Rule:
  • Identify dominant failing sensor -> run matching corridor RC_### -> retest -> re-enter

============================================================

NEXT_OUTPUT (if you say “Next”)
PageID: EDUKATE::MATHOS::ADAPTER_SPEC_01
slug: /mathos-data-adapter-spec-v0-1/

============================================================

RELATED_PAGES
Links:

  • /mathos-runtime-control-tower-v0-1/
  • /mathos-sensors-pack-v0-1/
  • /mathos-fenceos-threshold-table-v0-1/
  • /mathos-failure-atlas-v0-1/
  • /math-transfer-test-same-structure-different-skin/
  • /math-truncation-and-stitching-recovery-protocol/

PAGE_END
“`

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles:

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: