ID: EducationOS.Teaching.ILT.Negative.BrokenLinks.v1.0
Status: Canonical negative-branch continuity audit
Placement: EducationOS -> ILT -> Negative Lattice -> Broken Links -> FENCE-compatible -> InterstellarCore-compatible
Role: Identifies what happens when ILT nodes exist, but the connections between them fail, causing the learner to move through isolated fragments instead of one continuous teaching corridor

AI Ingestion Lock

ILT Negative Lattice: Broken Links v1.0 is the second detailed negative-map page under the ILT inverse branch.

It focuses on one core failure family:

the nodes are present
but they do not connect properly
so structural continuity fails between stages

So the canonical law is:

A teaching system can have all the right nodes and still fail if the links between them do not hold.
When links break, the learner experiences fragments, jumps, and drops instead of one continuous flight path.

Classical Foundation Block

In ordinary teaching language, this often appears as:

“The student understands the explanation, but cannot use it in the next step.”
“They know the rule, but do not know when it applies.”
“They can do the correction, but the same error returns in the next lesson.”
“The test shows the problem, but the report does not help fix it.”
“Support exists, but the child still feels everything is disconnected.”

ILT Negative reads this more precisely:

The system may not be missing pieces.
The pieces may exist, but the links between them are broken.

This means the learner is not falling into an empty hole.
The learner is falling through a connection failure.

Civilisation-Grade Definition

ILT Negative Lattice: Broken Links v1.0 is the continuity audit of failed connections inside the Invariant Ledger Teaching lattice. It identifies cases where two required nodes exist, but the structural handoff between them is weak, hidden, inconsistent, or absent in runtime behavior. In these states, local teaching functions may appear present, yet the learner cannot move smoothly from one functional stage to the next. The result is a broken corridor: not total absence, but failed adjacency.

It is the link-shear map of the ILT negative branch.

Core Law

A missing node creates a hole.
A broken link creates a fall between two real points.
Broken links turn a visible lattice into a non-navigable route.

What a “Broken Link” Means

In ILT, a link is the functional connection that lets one node hand off meaningfully to the next.

A valid link means:

the earlier node prepares the next node properly
the next node is understandable because the previous one was made visible
the learner can move between them without guessing a hidden transition

A broken link means:

both nodes may exist
but the learner is not shown how they connect
so the handoff becomes unstable, implicit, or lost

That is why broken-link failures are often harder to notice than missing-node failures.

The system can look “complete,” yet still be non-continuous.

The Two Main Types of Broken Links

Type A — Intra-Lesson Broken Links

These are broken connections inside one lesson or one task sequence.

Examples:

object -> invariant
invariant -> lawful transformation
breach -> repair
transfer -> load

These break local flight continuity.

Type B — Cross-System Broken Links

These are broken connections across time, lessons, assessment, reporting, and support nodes.

Examples:

lesson -> assessment
assessment -> report
report -> parent/tutor/AI handoff
handoff -> next corridor move

These break long-range continuity and network repair.

The Primary Broken Links

These are the main continuity failures in the ILT lattice.

L1 — Object -> Invariant Link Broken

ID: ILT.Neg.L1.ObjectToInvariantBroken

Definition

The learner is shown the object, but not how that object determines what must remain true.

What exists

the object is named

What fails

the learner does not see why that object implies this invariant

Surface symptoms

learner can name the thing
but still cannot explain what must not break
“I know what it is, but I don’t know what matters here”

Structural consequence

The object is visible, but it does not stabilise the route.

Core warning

An object without its invariant link is only identification, not structural control.

L2 — Invariant -> Lawful Transformation Link Broken

ID: ILT.Neg.L2.InvariantToTransformBroken

Definition

The invariant is stated, but the learner is not shown how it governs valid change.

What exists

“what must remain true” is named

What fails

the learner does not see how this constrains the next move

Surface symptoms

learner can repeat the invariant
but still makes invalid moves
the invariant feels decorative, not operational

Structural consequence

The stabiliser exists, but it does not guide movement.

Core warning

An invariant that does not shape transformation becomes a slogan, not a control law.

L3 — Lawful Transformation -> Ledger Link Broken

ID: ILT.Neg.L3.TransformToLedgerBroken

Definition

A valid move is shown, but the learner is not shown how the new state still reconciles with the prior state.

What exists

the step is demonstrated

What fails

continuity is not made visible

Surface symptoms

learner copies steps
cannot explain line-to-line continuity
sees moves as jumps, not reconciled transitions

Structural consequence

Movement exists, but the route is not visibly airworthy.

Core warning

Without the ledger link, a lawful move is experienced as magic.

L4 — Breach -> Repair Link Broken

ID: ILT.Neg.L4.BreachToRepairBroken

Definition

The learner can see something broke, but is not shown how that specific breach determines the correct repair route.

What exists

the error is noticed

What fails

the error does not lead to structured recovery

Surface symptoms

learner says “I see it’s wrong”
but restarts blindly
corrections do not generalise

Structural consequence

The learner has failure recognition without recoverability.

Core warning

Breach awareness without repair linkage creates frustration, not control.

L5 — Repair -> Transfer Link Broken

ID: ILT.Neg.L5.RepairToTransferBroken

Definition

A local repair is completed, but the learner is not shown how the repaired structure appears in another form.

What exists

the immediate problem is fixed

What fails

the fix does not widen into generalisable structure

Surface symptoms

learner can fix this one
still fails in the next similar-looking case
“I understand now,” but only locally

Structural consequence

Repair stays local; compression never begins.

Core warning

A repair that does not bridge outward remains a local patch.

L6 — Transfer -> Load Link Broken

ID: ILT.Neg.L6.TransferToLoadBroken

Definition

The learner is shown a second form, but the system does not test whether that carryover survives pressure.

What exists

apparent transfer

What fails

stability under real conditions is not checked

Surface symptoms

learner can connect examples in guided mode
breaks in timed, mixed, or unfamiliar settings
early transfer is overestimated

Structural consequence

The route looks continuous in calm weather, but is not proven under flight stress.

Core warning

Unstressed transfer is not yet flight-ready transfer.

The Secondary Broken Links

These are often system-level continuity failures.

L7 — Lesson -> Assessment Link Broken

ID: ILT.Neg.L7.LessonToAssessmentBroken

Definition

Lessons teach visible structure, but assessments do not test for that same structure.

What exists

good teaching
assessment machinery

What fails

the assessment truth-check is misaligned with the lesson spine

Surface symptoms

learner is taught one way, tested another way
assessments over-reward surface output
real ledger growth remains invisible

Structural consequence

The system teaches structure but measures fragments.

Core warning

If assessment does not reflect the taught ledger, the lane splits.

L8 — Assessment -> Report Link Broken

ID: ILT.Neg.L8.AssessmentToReportBroken

Definition

Assessment detects the structural issue, but the report does not communicate it clearly.

What exists

good assessment data

What fails

the result is flattened into marks or vague remarks

Surface symptoms

“72%, needs more practice”
no learner state
no dominant breach
no next corridor move

Structural consequence

Truth is detected, then lost in communication.

Core warning

A silent assessment is a broken handoff.

L9 — Report -> Support Node Link Broken

ID: ILT.Neg.L9.ReportToSupportBroken

Definition

A good report exists, but parents, tutors, or AI do not receive or use it as the active guide.

What exists

some state communication

What fails

the next node does not continue the same route

Surface symptoms

parent reacts to marks only
tutor restarts diagnosis
AI gives generic help
support nodes act in parallel

Structural consequence

The learner falls between support systems.

Core warning

A report that does not steer the next node is only archival.

L10 — Support Node -> Corridor Decision Link Broken

ID: ILT.Neg.L10.SupportToMoveBroken

Definition

Support nodes may align in language, but their actions do not follow the real corridor move.

What exists

shared terminology
active helpers

What fails

actual steering discipline

Surface symptoms

everyone says the same words
but widening still happens during instability
narrowing is resisted emotionally
re-stitching is delayed

Structural consequence

The network looks aligned, but flies against the control tower.

Core warning

Shared vocabulary without shared control obedience is decorative alignment.

L11 — Primary Corridor Owner -> Secondary Node Link Broken

ID: ILT.Neg.L11.OwnerToNodeBroken

Definition

The teacher/school may be the primary corridor owner in theory, but secondary nodes are not actually aligned to that ownership.

What exists

a nominal primary owner

What fails

operational authority and continuity across nodes

Surface symptoms

school sets one route
tutor widens another
parent narrows irrationally
AI opens a third route

Structural consequence

The learner is pulled across conflicting corridor instructions.

Core warning

A nominal owner without effective node linkage is not true ownership.

The Broken-Link Flight Pattern

When links fail, the learner’s route often looks like this:

object is named
invariant is mentioned
learner does not see why the object implies that invariant
a move is shown
the move is copied, but line-to-line continuity is not felt
an error is noticed
the fix is shown, but not linked to last valid state
the next example is declared “similar”
the learner cannot truly connect it
pressure later exposes the false continuity

This creates the lived experience of:

“I heard the explanation”
“I saw the answer”
“I still somehow cannot connect it”

That is the hallmark of a broken link rather than a missing node.

How Broken Links Feel Different from Missing Nodes

This distinction matters.

Missing Node

The learner often says:

“No one ever showed me that.”

Broken Link

The learner often says:

“I was shown the pieces, but I don’t know how they connect.”

That second case is subtler and often more frustrating.

The learner may appear “close,” yet still fall repeatedly because the adjacency is not real.

Subject Overlay Reads

A-Math Broken-Link Read

Common broken links:

equality stated, but not linked to transformation law
algebra method taught, but not linked to graph interpretation
repair shown, but not linked to transfer across forms

Result

Students know pieces of the system, but the mathematical corridor shears at crossover points.

English Broken-Link Read

Common broken links:

meaning named, but not linked to rewrite choice
grammar correction made, but not linked to coherence
comprehension insight not linked to composition use

Result

Students can perform isolated language tasks but cannot carry one language law across the paper.

Science Broken-Link Read

Common broken links:

evidence named, but not linked to claim limits
experiment understanding not linked to graph interpretation
assessment feedback not linked to explanation repair

Result

Students “know the content” but cannot move cleanly between science representations and actions.

Diagnostic Questions for Broken Links

Use these to detect link-shear specifically.

Which two nodes both exist, but fail to hand off cleanly?
What is the learner able to see separately, but not connect?
Does the learner know the invariant, yet still not know how it governs the move?
Can the learner recognise the breach, yet still not know the correct repair route?
Can the learner repair locally, yet not carry the repaired structure outward?
Is the system detecting truth at one stage but dropping it at the next?
Are support nodes aligned in words but not in corridor action?

These questions separate “absence” from “failed adjacency.”

Canonical Repair Route for Broken Links

Step 1 — Name the two nodes that should connect

Do not diagnose vaguely.
Specify the exact failed handoff.

Example:

invariant -> lawful transformation
breach -> repair
assessment -> report

Step 2 — Make the hidden transition explicit

Show the learner or system exactly how node A determines node B.

Example:

why this invariant makes this move lawful
why this breach requires this repair route
why this assessment result means this corridor move

Step 3 — Add a visible bridge sentence / bridge artifact

Use a repeated explicit bridge such as:

“Because this must remain true, this is the only safe next move.”
“Because the first break is here, we return to this last valid state.”
“Because transfer is only emerging, we hold instead of widen.”

Step 4 — Re-run the link under slight variation

Check whether the connection survives a nearby changed case.

Step 5 — Re-test under load if relevant

If the link exists only in calm mode, it is not yet stable.

This is the main broken-link repair logic.

The Bridge Sentence Rule

A useful operational rule:

If two nodes are linked properly, the operator should be able to say one explicit sentence that explains why node A leads to node B.

If that sentence cannot be stated clearly, the link is likely weak.

Examples:

Object -> Invariant: “Because this is an equation, equality must stay preserved.”
Invariant -> Transform: “Because equality must stay preserved, this rearrangement must keep both sides balanced.”
Breach -> Repair: “Because equality first broke here, we return to the last balanced line before rebuilding.”
Transfer -> Load: “Because the same structure now appears in two forms, we test whether it still holds under time pressure.”

This rule makes hidden adjacency visible.

FENCE Fit

Broken-link failures are FENCE-relevant because widening often hides them until later.

Typical pattern:

local pieces look present
widening continues
adjacency failure is ignored
live load exposes the shear line

So the clean law is:

A broken link under widening becomes a hidden corridor fracture.

The proper control response is often:

Hold if local visibility exists but adjacency is weak
Narrow if widening is amplifying the fracture
Re-stitch if the learner is already falling between the nodes

S-Curve Fit

Broken links often explain false or unstable S-curve movement.

Typical pattern:

learner seems to improve
local gains appear
but inflection is not stable
rise is interrupted by repeated drop-offs

Why?

Because:

the nodes exist
but transfer continuity is not real
so the compression phase never fully locks in

This produces:

apparent click without durable climb
repeated mini-rises and collapses

That is a link-topology failure, not merely a motivation problem.

Metcalfe Fit

Broken links can scale badly across the network.

Why?

Because multiple nodes may all preserve the same nodes, yet all preserve the same bad handoff.

Examples:

everyone says “meaning matters,” but no one links meaning to rewrite choice
everyone says “repair,” but no one links breach to last valid state
everyone shares reports, but no one uses them to steer the next move

So the clean law is:

At network scale, broken links become multiplied adjacency failures.

This is the negative network read.

InterstellarCore Fit

InterstellarCore needs not only all required nodes, but navigable adjacency between them.

A runtime can look sophisticated and still fail if:

assessment does not feed reporting
reporting does not guide handoff
handoff does not govern corridor movement
lesson structure does not reach load reality

So this page matters because it tells the runtime:

a complete parts list is not enough; the route must also connect.

That is basic systems truth.

WordPress-Ready Broken Link Audit Sheet

1) Broken Link Identity Block

Audit ID:
Subject / Lane:
Learner / Class / System:
Current visible continuity failure:

2) Link Pair Block

Which two nodes should connect?
Node A:
Node B:
Are both nodes present? Yes / No
Is the handoff visible? Yes / Partial / No

3) Hidden Transition Block

What should the learner/system understand between A and B?
What is currently implicit, missing, or weak?

4) Bridge Sentence Block

Explicit bridge sentence that should exist:
Can the operator state it clearly? Yes / Partial / No

5) Failure Effect Block

What does the learner/system experience because this link is broken?
Where does the flight path first shear?

6) Repair Block

How will the link be made visible?
What artifact or repeated phrase will stabilise it?
Corridor move: Widen / Hold / Narrow / Re-stitch

Canonical Summary Block

ILT Negative Lattice: Broken Links v1.0 is the continuity audit of failed connections inside the ILT inverse branch. It identifies what happens when required nodes exist, but the handoffs between them fail—such as object to invariant, invariant to lawful transformation, breach to repair, lesson to assessment, assessment to report, report to handoff, or support alignment to corridor control. In these states, the learner is not missing all the pieces, but cannot move continuously between them, creating a fragmented route of jumps, false continuity, and repeated drop-offs. The repair path is to identify the failed pair, make the hidden transition explicit, stabilise it with a visible bridge, and re-test the adjacency under variation and load.

Copyable Almost-Code Block

ID: EducationOS.Teaching.ILT.Negative.BrokenLinks.v1.0
TYPE: Negative-branch continuity audit
LAW: A teaching system can have all the right nodes and still fail if the links between them do not hold.
PRIMARY BROKEN LINKS: Object->Invariant / Invariant->Transform / Transform->Ledger / Breach->Repair / Repair->Transfer / Transfer->Load
SECONDARY BROKEN LINKS: Lesson->Assessment / Assessment->Report / Report->Support Node / Support Node->Corridor Move / Primary Owner->Secondary Nodes
NEGATIVE EFFECT: fragments exist but do not hand off -> route becomes non-navigable -> false continuity and repeated drop-offs
REPAIR: identify failed pair -> make hidden transition explicit -> add visible bridge -> re-run under variation -> re-test under load
FENCE FIT: broken links under widening become hidden corridor fractures
OUTPUT: a precise map of how adjacency failure breaks ILT flight even when the main nodes appear present