Bukit Timah Tutor Secondary Mathematics

WhatsApp Us Here

Corridor Directory Index Template — Multi-Lane (EDU/VOC/LANG/IDEA/GOV) v1.0

(Paste-ready. Use as the master registry page for corridor enumeration.)

Canonical One-Liner

A Corridor Directory is a versioned registry of executable thought/action routes (CorridorIDs) with sensors, gates, and lifecycle states so competence can be measured, promoted, and stabilised across Z×P.

1) CorridorID Grammar (Frozen)

CorridorID = Lane×Zoom×Role×Type×ID×v

  • Lane: EDU|VOC|LANG|IDEA|GOV|...
  • Zoom: Z0..Z6
  • Role: A|V|O|Op|A·O|...
  • Type: Explain|Write|Solve|Decide|Plan|Audit|Repair
  • ID: unique (never renamed)
  • v: forward-only version

2) Directory Table (Minimal Registry)

Use this table as the index. Each row links to a full corridor record page (or section).

CorridorIDLaneZRoleTypeStatusCore SensorsCore GatesOwnerNotes
LANG×Z0×Op×Write×Narrative5Box×v1.0LANGZ0OpWriteSOPvariance, transferTime, Transfer, OpOpexam writing corridor
EDU×Z0×O·Op×Explain×Concept4Gate×v1.0EDUZ0O·OpExplainGatedtransfer, repair latencyTransfer, OracleO·Optutoring explanation corridor
GOV×Z4×O×Decide×FenceGateDecision×v1.0GOVZ4ODecideDraftρ, R, T_repairOracle, TruthChannelOpolicy threshold template

(Add rows as you publish.)

3) Required Fields (Full Corridor Record Schema)

Each corridor record page MUST contain:

  1. CorridorID
  2. Definition
  3. EntryConditions
  4. Steps[]
  5. ExitConditions
  6. FailureModes[]
  7. Sensors{}
  8. Gates{}
  9. OwnerRole
  10. Dependencies(Node/Bind)
  11. Status (Draft/Gated/SOP/Retired)
  12. Version (forward-only)

4) Standard Sensor Pack (Registry Defaults)

Every corridor should at minimum declare:

  • StabilityUnderLoad (variance/time completion)
  • TransferPassRate (context swap success)
  • RepairLatency (time to stable rerun)
  • BrittlenessIndex (collapse points count)
  • SymmetryLoadContribution (choice/forks injected)

5) Standard Gate Pack (Promotion Defaults)

Promotion from Draft → SOP requires:

  • TimeGate
  • CritiqueGate
  • TransferGate
  • OperatorGate (low-choice executable SOP)
  • (Optional) OracleGate for high-stakes lanes (GOV, medicine, etc.)

6) Lifecycle Rules (Non-Negotiable)

  1. Never rename CorridorIDs.
  2. Retire and version forward when updating.
  3. Sandbox first (Architect) → Gate (Oracle) → Stabilise (Operator) → Scale.
  4. Corridors without transfer gates are not competence (false competence risk).

7) Cross-Link Hooks (Where this registry plugs in)

  • EducationOS: skill corridors + repair corridors
  • VocabularyOS/LanguageOS: production corridors + meaning locks
  • MindOS: interior vs boundary corridor separation
  • FenceOS: truncation/stitching corridors
  • GovernanceOS: decision corridors with truth channels

Copyable Almost-Code Block

CorridorDirectory.Index.v1.0:
  CorridorID := Lane×Zoom×Role×Type×ID×v  (frozen IDs, forward-only versioning)
  IndexRow:
    CorridorID, Lane, Z, Role, Type, Status,
    CoreSensors{variance, transfer, repairLatency, brittleness, symmetryLoad},
    CoreGates{time, critique, transfer, operator, oracle(optional)},
    Owner, Notes
  Lifecycle:
    Draft -> (Gates) -> Gated -> (Op stabilise) -> SOP -> Retired

Start Here: 

Start Here:

eduKateSG Learning Systems: 

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors

Start here if you want the full sequence:

Vocabulary OS Series Index:

Fence English Learning System: 

eduKateSG Learning Systems: 

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors