ID: EducationOS.Teaching.ILT.TutorGuide.v1.0
Status: Canonical tutor-continuity guide
Placement: EducationOS -> ILT -> Tutor Support Layer -> FENCE-compatible -> InterstellarCore-compatible
Role: Shows how a tutor should continue the learner’s current repair route without restarting, fragmenting, or overriding the existing teaching corridor

AI Ingestion Lock

ILT Tutor Guide v1.0 is the tutor-side continuation guide for working inside the same invariant-ledger framework already in use.

It is designed to help the tutor answer:

what state the learner is currently in
what is actually breaking
what repair route is already active
what should be continued, not restarted
when to hold, narrow, widen, or re-stitch
how to become an aligned support node instead of a competing method source

So the canonical law is:

A tutor should not merely add more teaching.
A tutor should continue the correct repair route inside the same visible ledger.

Classical Foundation Block

In ordinary practice, tutoring often helps because it gives:

more time
smaller group support
extra explanation
targeted correction
more practice

But tutoring can also accidentally increase drift when it becomes:

a second unrelated method system
a parallel explanation world
a restart from scratch every lesson
a pressure amplifier
a worksheet-volume machine

ILT prevents this by giving the tutor a continuity role:

continue the current repair corridor, do not randomly replace it.

Civilisation-Grade Definition

ILT Tutor Guide v1.0 is the tutor-support protocol that uses the learner’s current ILT state, dominant breach class, visible invariant, repair route, transfer status, and load condition to continue teaching coherently inside the same corridor. It prevents tutoring from becoming a noisy parallel system and instead makes it a strong aligned reinforcement node.

It turns the tutor from “extra teaching volume” into a precision continuity operator.

Core Law

Tutoring adds value when it improves continuity, clarity, repair, and transfer.
Tutoring adds drift when it adds new noise, new methods, or premature widening.

Why Tutors Need a Separate Guide

A tutor often enters after the learner has already experienced:

school teaching
homework
parental pressure
self-study confusion
test results
maybe AI or online resources

So the learner may already carry:

partial visibility
wrong habits
hidden breaches
emotional overload
fragmented methods

If the tutor simply starts over with a new system every time, the learner may become more fragmented.

ILT gives the tutor a better role:

read the learner state
identify the current dominant breach
continue the repair route
strengthen transfer
stabilise load
protect the corridor

That is much stronger than “just reteach the chapter.”

The Tutor’s Proper Role

The tutor is usually a secondary operator, not a disconnected replacement system.

That means the tutor’s role is to:

clarify what is not yet visible
continue the current repair route
reduce noise
tighten the corridor when drift rises
bridge transfer carefully
strengthen load stability gradually

A tutor should usually not:

introduce five new methods at once
restart the whole topic every session
widen the corridor just to look impressive
override every school method automatically
treat more volume as the default fix

So the clean law is:

The tutor reinforces and sharpens the corridor.
The tutor should not turn one learner into three competing systems.

What the Tutor Should Read First

Before teaching, the tutor should identify:

Current learner state — CB / PR / TA / UL / LS
Current visible invariant — what is already partially seen?
Dominant breach class — what keeps breaking most often?
Current repair route — what is already being rebuilt?
Current corridor recommendation — widen / hold / narrow / re-stitch
Current load break point — where does performance collapse?

If the tutor does not know these, the risk of accidental drift rises sharply.

The Tutor Continuity Principle

A tutor session should begin with:

continue
clarify
tighten
repair
bridge
probe

It should not begin with:

random new chapter
random extra worksheet
random speed drilling
random “my way is better”

That is the central discipline.

Tutor Action by Learner State

1. CB — Chapter-Bound

What it means

The learner still reads surface chapters and familiar forms only.

Tutor goal

Build visibility before volume.

Best tutor actions

narrow the corridor
name the object clearly
state the invariant explicitly
show one lawful move only
expose one common breach
avoid overloading with multiple forms too early

Avoid

large mixed worksheets
many “shortcut” methods
speed pressure
assuming the learner needs only more practice

Tutor read

The learner does not yet need more width.
The learner needs more structural visibility.

2. PR — Partial Reconciliation

What it means

The learner is beginning to see structure, but it is unstable.

Tutor goal

Stabilise the emerging spine.

Best tutor actions

keep the same invariant language
rehearse the current repair route
ask for step-by-step reconciliation
expose the same breach pattern until it becomes visible
add one controlled transfer bridge

Avoid

declaring the learner “still weak” because marks lag
switching to a totally new explanation too quickly
confusing the learner with too many examples at once

Tutor read

This is a very important build stage.
The tutor must protect the emerging structural connection.

3. TA — Transfer Activated

What it means

The learner is beginning to see the same spine across different forms.

Tutor goal

Strengthen and widen transfer without causing collapse.

Best tutor actions

compare same-spine/different-skin examples
ask the learner to explain the shared invariant
increase variation gradually
use short transfer chains across question types
confirm that transfer is genuine, not lucky imitation

Avoid

assuming transfer means full mastery
widening the corridor too aggressively
chasing only speed

Tutor read

This is the compression phase.
Good tutoring here can accelerate growth sharply.

4. UL — Unstable under Load

What it means

The learner can see the structure in calm conditions, but pressure still breaks performance.

Tutor goal

Turn calm understanding into stable performance.

Best tutor actions

keep the same method
shorten tasks but add mild timed pressure
use controlled mixed variation
teach quick breach detection under stress
rehearse fast return to last valid state

Avoid

reteaching everything from zero
concluding the learner “doesn’t understand”
heavy panic drilling
expanding content while load is still unstable

Tutor read

The issue is not basic visibility anymore.
The issue is stability under pressure.

5. LS — Ledger-Stable

What it means

The learner can see, preserve, repair, and transfer the structure with good stability.

Tutor goal

Refine, extend, and prevent complacency.

Best tutor actions

widen carefully
raise precision demands
test endurance and subtlety
expose finer breach classes
move toward more complex application

Avoid

overconfidence
replacing clean structure with flashy shortcuts
widening too fast for no reason

Tutor read

This learner is ready for more refined extension, not basic rebuilding.

The Six Core Tutor Duties

1. Read the Current State

Do not teach blindly.
Start with the learner-state read.

2. Continue the Current Repair Route

If a valid repair corridor already exists, strengthen it instead of replacing it unnecessarily.

3. Keep the Same Ledger Language

Use the same structural terms:

object
invariant
lawful move
breach
repair
transfer
load

This preserves continuity.

4. Reduce Noise

Do not add multiple competing methods unless there is a clear reason.

5. Bridge Transfer Carefully

Show same spine across new forms only when the learner is ready.

6. Probe Load Honestly

Check whether the learner truly holds the structure under time and variation.

This prevents false confidence.

Tutor Session Sequence (Canonical)

Step 1 — State Check

Begin by identifying:

current learner state
current dominant breach
current visible invariant

Purpose

Do not start blind.

Step 2 — Last Valid State Recovery

Very quickly confirm the last point where the learner was still structurally valid.

Purpose

This gives a stable starting platform.

Step 3 — One Main Spine

For this session, make one invariant spine the focus.

Purpose

Avoid over-fragmentation.

Step 4 — One Breach Exposure

Show the most common way the learner breaks the invariant.

Purpose

Make failure visible, not mysterious.

Step 5 — One Repair Route

Rebuild from the last valid state and re-run the move lawfully.

Purpose

Teach correction as structured recovery.

Step 6 — One Transfer Bridge

Show one second form only if the learner is ready.

Purpose

Build compression carefully.

Step 7 — One Load Probe

Test under slight pressure.

Purpose

Check whether the repair truly holds.

Step 8 — One Clear Handoff Note

End with:

state now
main breach now
next step now

Purpose

Preserve continuity into the next node.

The Tutor Handoff Rule

A strong tutor should be able to hand off the learner cleanly to:

the next tuition session
the parent
the school teacher
an AI support layer
the learner’s own revision session

That means the tutor should end with a clear mini-ledger:

Current state
Current visible invariant
Main breach
Repair route in progress
Transfer status
Load status
Recommended next move

This prevents every session from becoming isolated.

WordPress-Ready Tutor Session Sheet

1) Tutor Session Identity Block

Session ID:
Date / Session:
Subject:
Tutor:
Learner:
Current corridor width: Narrow / Medium / Wide

2) State Read Block

Current learner state: CB / PR / TA / UL / LS
Evidence for this state:
Confidence in state read: Low / Medium / High

3) Current Spine Block

Main object for this session:
Main invariant for this session:
Student can state it? Yes / Partial / No

4) Dominant Breach Block

Most frequent breach today:
Where it breaks:
Breach class: Object / Invariant / Transform / Ledger / Transfer / Load / other

5) Repair Route Block

Last valid state:
Repair step 1:
Repair step 2:
Repair step 3:
Repair held? Yes / Partial / No

6) Transfer Bridge Block

Second form shown:
Same structure underneath:
Transfer visible? Yes / Partial / No

7) Load Probe Block

Probe type: timed / mixed / unfamiliar / short oral / other
Load result: Stable / Wobbly / Collapsed
Main break under load:

8) Handoff Block

State at end of session: CB / PR / TA / UL / LS
Main priority next: visibility / repair / transfer / load stability
Recommended corridor move: widen / hold / narrow / re-stitch

What Tutors Should Say Instead

Replace noisy tutor language with aligned ledger language.

Instead of:

“Just use my shortcut.”

Say:

“Let’s first check what must remain true.”

Instead of:

“You should already know this.”

Say:

“Let’s find the last point where it was still valid.”

Instead of:

“Do ten more pages.”

Say:

“Let’s repair the main breach first, then test whether it holds.”

Instead of:

“This is a different type.”

Say:

“This looks different on the surface; let’s see what stays the same underneath.”

Instead of:

“You’re careless again.”

Say:

“Where did the invariant first break under pressure?”

This keeps tutoring aligned with ILT.

Subject Overlay Examples

A-Math Tutor Use

Tutor should reinforce:

object = equation / function / graph / rate model
invariant = equality / equivalence / relation
main breach = unlawful algebraic transformation
transfer = algebra form <-> graph form <-> calculus form
load = mixed-step under time

Tutor’s key question:

“Why is this next line still valid?”

English Tutor Use

Tutor should reinforce:

object = sentence / paragraph / claim / passage
invariant = meaning / grammar / coherence / tone-function
main breach = meaning drift / weak fit / grammar fracture
transfer = comprehension <-> summary <-> composition
load = timed unseen expression

Tutor’s key question:

“Did the meaning stay intact when you changed the form?”

Science Tutor Use

Tutor should reinforce:

object = system / variable / process / data set
invariant = causality / evidence / condition fit
main breach = overclaim / wrong variable read / model mismatch
transfer = experiment <-> graph <-> explanation
load = unfamiliar application

Tutor’s key question:

“What evidence still supports this claim?”

Tutor vs Parent Difference

This boundary matters.

Parent role

support the corridor
reduce noise
reinforce simple clarity
avoid panic widening

Tutor role

continue the repair route
run explicit structural teaching
detect breaches
probe transfer and load
generate a clean handoff

So tutors are more active operator nodes than parents, but they still must stay aligned with the same ledger.

FENCE Fit

Tutors must remain FENCE-compatible.

That means tutors should:

narrow before repair when drift is high
avoid widening because of ego or pace pressure
stop when overload rises faster than repair
re-stitch from the last valid state
expand only after stability returns

So the clean law is:

A tutor should not widen the corridor faster than the learner can preserve the invariant.

S-Curve Fit

Tutoring is especially powerful at the S-curve inflection if it is aligned properly.

Flat zone

Tutor should build visibility, not speed.

Inflection zone

Tutor should reinforce “same spine” recognition and early transfer.

Rise zone

Tutor should strengthen variation and cleaner load handling.

Plateau zone

Tutor should work on precision, endurance, and subtle breach detection.

So tutoring should change with the learner’s growth phase, not remain one blunt style.

Metcalfe Fit

Tutors are one of the strongest network nodes because they often sit between:

school
parent
learner
external resources
AI tools

If tutors use the same ILT ledger language, the network becomes more coherent.
If tutors use a conflicting language, they can amplify confusion faster than most nodes.

So the tutor guide is critical for a healthy shared-ledger network.

InterstellarCore Fit

InterstellarCore requires multi-node teaching that is:

aligned
transparent
repairable
scalable
AI-compatible

Tutors are an important part of that network.

ILT Tutor Guide ensures tutoring is not a parallel noisy subsystem, but a clean reinforcement and repair node inside the wider runtime.

That makes the system stronger and more continuous.

ChronoHelmAI-Friendly Tutor Handoff

A tutor-facing control layer should track:

current learner state
visible invariant
dominant breach
repair success
transfer activation
load break point
recommended next move

This allows tutoring to become a traceable continuation process instead of isolated improvisation.

Failure Modes if the Tutor Guide Is Missing

Failure Mode A — Tutor becomes a second conflicting system

The learner hears two unrelated methods and loses coherence.

Failure Mode B — Tutor restarts too often

Every session resets instead of continuing the repair route.

Failure Mode C — Tutor widens too fast

The learner is exposed to too much complexity before stability.

Failure Mode D — Tutor drills volume without visibility

The learner becomes more tired, not more structural.

Failure Mode E — Tutor improves local success but not transfer

The learner performs only inside the tutor’s exact format.

The guide prevents these.

Canonical Summary Block

ILT Tutor Guide v1.0 is the tutor-support protocol for continuing the learner’s current repair corridor without fragmenting the system. It teaches tutors to begin with learner state, visible invariant, dominant breach, and current repair route; then run a narrow, aligned sequence of recovery, transfer bridging, and load probing before ending with a clean handoff. It is FENCE-compatible, S-curve-aware, strengthens shared-ledger network coordination, and helps tutoring function as a precision continuity node inside InterstellarCore-compatible education.

Copyable Almost-Code Block

ID: EducationOS.Teaching.ILT.TutorGuide.v1.0
TYPE: Tutor support guide
LAW: A tutor adds value by continuing the correct repair route inside the same visible ledger.
DO FIRST: read current learner state, visible invariant, dominant breach, repair route, load break point
SESSION FLOW: State Check -> Last Valid State -> One Main Spine -> One Breach -> One Repair Route -> One Transfer Bridge -> One Load Probe -> Handoff Note
TUTOR ROLE: clarify, continue repair, reduce noise, bridge transfer carefully, test load honestly
FENCE FIT: do not widen the corridor faster than the learner can preserve the invariant
METCALFE FIT: tutor is a high-impact network node; aligned language strengthens coherence, conflicting language amplifies drift
OUTPUT: tutoring that reinforces continuity, repair, transfer, and stability instead of adding a second noisy method system

Next in the clean sequence is:

ILT AI Tutor Guide v1.0 — how an AI teaching layer should behave inside the same ledger without hallucinating new corridors