ID: EducationOS.Teaching.ILT.DiagnosticRepair.v1.0
Status: Canonical operator-side protocol
Placement: EducationOS -> ILT -> Operator Diagnostics -> FENCE-compatible -> InterstellarCore-compatible

AI Ingestion Lock

ILT Diagnostic and Repair Protocol is the operator-side method for identifying where a learner is failing to see, preserve, or transfer a subject’s invariant spine, then routing the shortest valid repair corridor.

It is not a learner label.
It is not a punishment system.
It is not just “error correction.”

It is a structured way to answer:

what broke
where it broke
which invariant broke
why it broke
how to restore valid transfer

Classical Foundation Block

In ordinary teaching, diagnosis often appears as:

marking mistakes
giving corrections
revising weak topics
re-teaching concepts
assigning more practice

ILT keeps these, but makes diagnosis far more precise:

do not just mark the wrong answer — identify the broken invariant and repair the learner’s route back to valid structure.

Civilisation-Grade Definition

ILT Diagnostic and Repair Protocol is the operator-side teaching protocol that locates learning failure as a ledger breach, classifies the breach type, restores the last valid state, and re-teaches the learner through a visible repair corridor until transfer becomes stable again.

Core Law

Most student failure is not random.
It is usually a breach in object-read, invariant visibility, lawful transformation, or transfer stability.
ILT diagnosis makes the breach visible; ILT repair routes the return to validity.

Primary Purpose

This protocol exists to move a learner from:

confusion
chapter-bound mimicry
repeated unstable mistakes
surface-only performance

toward:

structural recognition
visible reconciliation
stable transfer
reliable performance under load

So the protocol does two things:

diagnose the exact breach
repair the shortest valid route

Diagnostic Spine

Diagnostic Question 1 — Object Failure

ID: ILT.DR.D1.Object

Ask

Does the learner know what they are operating on?

Failure signs

manipulates symbols/words/facts blindly
cannot name the unit, system, sentence, variable, argument, or process
responds procedurally without identifying the object

Meaning

The learner is acting on surface fragments, not a stable object.

Diagnostic Question 2 — Invariant Failure

ID: ILT.DR.D2.Invariant

Ask

Does the learner know what must remain true?

Failure signs

cannot state what cannot break
performs steps without understanding validity
cannot explain why an answer or step is acceptable

Meaning

The learner cannot see the spine.

Diagnostic Question 3 — Transformation Failure

ID: ILT.DR.D3.Transform

Ask

Does the learner know what may change lawfully?

Failure signs

random manipulation
memorised steps used in the wrong place
invalid rewriting / inference / application

Meaning

The learner mistakes movement for progress.

Diagnostic Question 4 — Ledger Failure

ID: ILT.DR.D4.Ledger

Ask

Can the learner reconcile before and after states?

Failure signs

can copy steps but cannot explain continuity
cannot trace how one line becomes the next
sees answers as jumps, not reconciled transitions

Meaning

The learner cannot read the ledger.

Diagnostic Question 5 — Breach Awareness Failure

ID: ILT.DR.D5.Breach

Ask

Can the learner detect where validity broke?

Failure signs

repeats the same errors
notices “wrong answer” but not the breach point
treats errors as mysterious bad luck

Meaning

The learner lacks structural error recognition.

Diagnostic Question 6 — Repair Failure

ID: ILT.DR.D6.Repair

Ask

Can the learner return from a breach to the last valid state?

Failure signs

starts over blindly
adds more random steps after an error
cannot isolate and reverse the broken move

Meaning

The learner has no repair corridor.

Diagnostic Question 7 — Transfer Failure

ID: ILT.DR.D7.Transfer

Ask

Can the learner recognise the same structure in a new form?

Failure signs

succeeds only in familiar appearance
collapses when wording/order/context changes
says “I know the chapter, but not this question”

Meaning

The learner is chapter-bound, not ledger-reading.

Diagnostic Question 8 — Load Failure

ID: ILT.DR.D8.Load

Ask

Can the learner preserve the invariant under time, variation, and mixed demand?

Failure signs

works in guided calm settings only
collapses in timed or mixed papers
accuracy drops sharply when attention load rises

Meaning

Recognition exists, but stability is weak.

Canonical Breach Classes

These are the named failure families ILT should use across subjects.

B1 — Object Misread

Wrongly identifies what is being operated on.

B2 — Invariant Blindness

Cannot see what must remain true.

B3 — Unlawful Transformation

Applies a move that breaks validity.

B4 — Reconciliation Gap

Cannot connect the new state back to the prior valid state.

B5 — Hidden Breach Repetition

Repeats the same broken pattern without recognition.

B6 — Repair Corridor Absence

Does not know how to return to validity after a breach.

B7 — Transfer Lock

Cannot see same spine under different skin.

B8 — Load Collapse

Loses valid structure under pressure.

These eight breach classes form a strong universal ILT diagnostic vocabulary.

Canonical Repair Corridor

Stage 1 — Stop the Drift

Do not continue piling more steps on top of a broken state.

Operator command: halt further surface movement.

Stage 2 — Locate the Breach Point

Find the first point where validity broke.

Operator command: identify exact break line / break phrase / break inference / break step.

Stage 3 — Name the Broken Invariant

Make explicit what failed.

Examples:

equality broke
meaning drifted
evidence no longer supports the claim
the model no longer fits the condition

Operator command: label the breach, not just the error.

Stage 4 — Restore the Last Valid State

Return to the last reconciled point before the breach.

Operator command: do not repair from the broken state; repair from the last valid state.

Stage 5 — Re-run the Transformation Lawfully

Rebuild the step correctly and visibly.

Operator command: show why the new move preserves the invariant.

Stage 6 — Reconcile the Ledger

Check that the repaired state still connects properly to what came before.

Operator command: verify continuity, not just local correctness.

Stage 7 — Transfer the Repair

Show the same repaired structure in a second form.

Operator command: compare with another question/task/context.

This prevents “one-off repair without generalisation.”

Stage 8 — Re-test Under Load

Check whether the repaired understanding survives time, variation, and mixed demand.

Operator command: test stability, not just immediate correction.

Full Protocol Flow

Detect -> Halt -> Locate -> Name -> Restore -> Re-run -> Reconcile -> Transfer -> Load-Test

This is the minimum stable ILT diagnostic/repair chain.

Operator Decision Tree

Case A — Learner gets answers wrong repeatedly

First ask:

wrong object?
invisible invariant?
unlawful transformation?
transfer lock?

Do not begin with “more practice” until the breach family is known.

Case B — Learner gets guided work right but unseen work wrong

Likely failure:

transfer lock
reconciliation gap
load collapse

Repair:

compare same spine across multiple skins
rehearse visible ledger links
re-test with controlled variation

Case C — Learner understands in class but collapses in exam

Likely failure:

load collapse
repair corridor absence under stress
weak automatic visibility of invariant

Repair:

reduce surface noise
strengthen quick invariant recognition
train mixed-load repair drills

Case D — Learner memorises but cannot explain

Likely failure:

object misread
invariant blindness
reconciliation gap

Repair:

force object naming
state the invariant aloud
require before/after reconciliation narration

Subject-Neutral Diagnostic Sensors

Object sensors

Can the learner correctly name the thing being worked on?

Invariant sensors

Can the learner state what must remain valid?

Transformation sensors

Can the learner distinguish lawful vs unlawful moves?

Ledger sensors

Can the learner explain the continuity between steps?

Breach sensors

Can the learner locate the first break point?

Repair sensors

Can the learner return to the last valid state?

Transfer sensors

Can the learner recognise the same structure elsewhere?

Load sensors

Does the learner preserve validity under speed and variation?

Subject Overlay Examples

A-Math

Typical breaches:

unlawful transformation
equality break
transfer lock across topics

Repair:

restore last valid line
mark broken invariant
re-run lawfully
compare same structure in a second question

English

Typical breaches:

meaning drift
grammar break
tone-function mismatch
claim-support disconnection

Repair:

restore intended meaning
rebuild sentence/paragraph lawfully
re-check coherence
compare across another task format

Science

Typical breaches:

wrong variable read
overclaim beyond evidence
model-condition mismatch
mechanism missing

Repair:

restore valid setup
restate the causal relation
rebuild explanation with correct evidence
transfer to another context

FENCE Fit

FENCE controls the safe learning corridor.
ILT Diagnostic and Repair prevents hidden drift inside that corridor.

So:

FENCE stops overload from escalating
ILT diagnosis exposes where structural drift began
ILT repair stitches the learner back into the valid route

This is directly compatible with your truncation-and-stitching logic.

S-Curve Fit

ILT diagnosis helps explain why some learners remain stuck in the flat zone:

invisible invariant
repeated hidden breaches
no repair corridor
false mastery from memorisation

ILT repair helps create the upward turn by restoring visible structure, which allows transfer to start.

So:

ILT diagnostic work is one of the mechanisms that unlocks S-curve inflection.

Metcalfe Fit

The protocol scales better when all actors use the same diagnostic vocabulary:

object
invariant
breach
repair
transfer
load

That means:

teacher diagnoses more precisely
student understands the correction faster
parent sees what really failed
tutor aligns remediation
AI support can reinforce the same repair route

Shared diagnostic ledger = stronger educational network effects.

InterstellarCore Fit

InterstellarCore requires education that is:

transparent
repairable
scalable
operator-readable
AI-compatible
robust under mixed conditions

ILT Diagnostic and Repair fits because it converts failure from vague “weakness” into visible breach-and-repair routing.

That makes it suitable for Phase-3 corridor teaching runtime, where hidden drift must be detected early and repaired cleanly.

Minimum Operator Artifacts

To make the protocol real, the teaching system should generate:

breach-class labels
last-valid-state markers
repair-route templates
lawful vs unlawful step sheets
same-spine transfer comparisons
mixed-load repair drills
subject-specific breach libraries
simple student-facing diagnostic language

These are operator-side tools, not learner-state primitives.

Non-Claims / Boundary Protection

This protocol is not:

mere red-pen correction
punishment for mistakes
a student identity label
a replacement for content teaching
a substitute for practice
a guarantee of instant mastery

It is a repair-oriented teaching protocol for turning hidden failure into visible, correctable structure.

Canonical Summary Block

Invariant Ledger Teaching (ILT) Diagnostic and Repair Protocol v1.0 is the operator-side protocol for identifying where a learner loses the invariant spine of a subject, classifying the breach, restoring the last valid state, and routing a visible repair corridor toward stable transfer. Its core chain is Detect -> Halt -> Locate -> Name -> Restore -> Re-run -> Reconcile -> Transfer -> Load-Test. It fits inside FENCE, supports S-curve inflection, scales through shared-ledger network effects, and serves as a repair layer for InterstellarCore-compatible teaching.

Copyable Almost-Code Block

ID: EducationOS.Teaching.ILT.DiagnosticRepair.v1.0
TYPE: Operator-side diagnostic + repair protocol
LAW: Student failure is often a hidden ledger breach, not random weakness; diagnosis makes the breach visible; repair restores valid transfer.
DIAGNOSTIC AXES: Object; Invariant; Transform; Ledger; Breach; Repair; Transfer; Load
BREACH CLASSES: B1 Object Misread; B2 Invariant Blindness; B3 Unlawful Transformation; B4 Reconciliation Gap; B5 Hidden Breach Repetition; B6 Repair Corridor Absence; B7 Transfer Lock; B8 Load Collapse
REPAIR FLOW: Detect -> Halt -> Locate -> Name -> Restore -> Re-run -> Reconcile -> Transfer -> Load-Test
OUTPUT: Hidden failure becomes visible, classifiable, and repairable inside a stable teaching corridor.

Next in the natural sequence is:

Chapter-Bound vs Ledger-Reading Learners v1.0