ID: EducationOS.Teaching.ILT.RuntimeBoard.v1.0
Status: Canonical compact control panel
Placement: EducationOS -> ILT -> Runtime Control Layer -> FENCE-compatible -> InterstellarCore-compatible
Role: A one-view operational board that lets any aligned node read the current teaching state quickly through the same invariant-ledger grammar

AI Ingestion Lock

ILT One-Page Runtime Board v1.0 is the compact control panel for running Invariant Ledger Teaching in real time.

It compresses the full ILT stack into one operational view:

current object
current invariant
current lawful move
current dominant breach
current last valid state
current repair route
current transfer status
current load status
current learner state
current corridor move

So the canonical law is:

If the ledger cannot be seen quickly, it cannot be coordinated quickly.
The Runtime Board turns ILT into a one-view operational state.

Classical Foundation Block

A full teaching framework may be rich and powerful, but daily teaching and support often need something simpler:

one page
one glance
one shared state read
one immediate next move

Without that, the system becomes:

too distributed
too wordy
too hard to hand off
too slow to coordinate across nodes

So the Runtime Board exists to compress the system into an actionable control panel.

Civilisation-Grade Definition

ILT One-Page Runtime Board v1.0 is the compact operator-side state board that displays the current structural teaching condition of a learner or class in one view, using the frozen ILT vocabulary. It provides an immediate read of what is being worked on, what must remain true, what is breaking, how repair is being routed, whether transfer has activated, whether load is stable, and whether the corridor should widen, hold, narrow, or re-stitch.

It is the live operational dashboard of the ILT branch.

Core Law

A long framework explains the method.
A runtime board runs the method.

Why the Runtime Board Exists

By this point, ILT already has:

root definition
module set
learner-state mapping
diagnostic and repair protocol
lesson template
assessment template
report card
support-node guides
implementation ladder
glossary

That is strong, but in live teaching, a node often needs a faster question:

What is the state right now, and what do we do next?

The Runtime Board answers that.

It is the “control tower screen” version of ILT.

What the Runtime Board Must Show

A valid ILT runtime board must answer these questions in one view:

What is the learner currently operating on?
What must remain true?
What move is currently in play?
What is the main thing breaking?
Where was the last valid state?
What repair route is active?
Has transfer started?
Does load still break the learner?
What state is the learner in?
Should we widen, hold, narrow, or re-stitch?

If a board cannot answer these, it is not yet a real ILT runtime board.

Canonical Runtime Board Fields

1. Object Field

ID: ILT.Board.Object

Purpose

Shows the exact current object.

Examples

equation
function
sentence
paragraph
variable
process
data set

Board question

What are we working on right now?

2. Invariant Field

ID: ILT.Board.Invariant

Purpose

Shows what must remain true.

Examples

equality
intended meaning
evidence-claim coherence
variable-control integrity

Board question

What must not break right now?

3. Lawful Move Field

ID: ILT.Board.Transform

Purpose

Shows the current valid transformation being taught or executed.

Examples

factorise
rewrite
infer within evidence
move from table to graph

Board question

What change is currently allowed?

4. Dominant Breach Field

ID: ILT.Board.Breach

Purpose

Shows the main current failure point.

Canonical reads

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

Board question

Where is the main break right now?

5. Last Valid State Field

ID: ILT.Board.LastValidState

Purpose

Shows the correct restart point for repair.

Board question

What is the last point where validity was still intact?

6. Repair Route Field

ID: ILT.Board.Repair

Purpose

Shows the active repair sequence currently being used.

Examples

restate object
restate invariant
return to last valid line
re-run lawful move
verify reconciliation

Board question

How are we getting back to validity?

7. Transfer Status Field

ID: ILT.Board.Transfer

Purpose

Shows whether the learner can carry the same spine into a new form.

Canonical reads

None
Emerging
Active
Strong

Board question

Is the same structure visible beyond this one form yet?

8. Load Status Field

ID: ILT.Board.Load

Purpose

Shows whether the learner’s structural hold survives pressure.

Canonical reads

Stable
Wobbly
Collapsed

Board question

Does the structure still hold under current pressure?

9. Learner State Field

ID: ILT.Board.State

Purpose

Shows the learner’s current structural state.

Canonical reads

Board question

What state is the learner in right now?

10. Corridor Move Field

ID: ILT.Board.Move

Purpose

Shows the next control decision.

Canonical reads

Widen
Hold
Narrow
Re-stitch

Board question

What should the corridor do next?

The Minimum One-Page Board

The smallest valid version of the board is:

Object
Invariant
Dominant Breach
Repair Route
Learner State
Corridor Move

This is the minimum live board.

The fuller version adds:

lawful move
last valid state
transfer status
load status

That is the complete runtime board.

Canonical Runtime Read Sequence

A node reading the board should process it in this order:

Step 1 — Read the object

Know what is currently being operated on.

Step 2 — Read the invariant

Know what must remain true.

Step 3 — Read the dominant breach

Know what is actually failing.

Step 4 — Read the last valid state

Know where repair must restart from.

Step 5 — Read the repair route

Know what correction path is active.

Step 6 — Read transfer status

Know whether the learner is still local or beginning to generalise.

Step 7 — Read load status

Know whether the structure survives pressure.

Step 8 — Read learner state

Know the overall current condition.

Step 9 — Read corridor move

Know what should happen next.

This makes the board a real decision device.

Why This Board Matters Across Nodes

Different nodes need the same one-view state:

teacher
tutor
parent
AI support
school leadership
learner

But each node has less time than the full article stack.

The Runtime Board solves that by making the current state portable.

It becomes a shared handoff surface.

That is why it is so strong.

WordPress-Ready One-Page Runtime Board

1) Identity Strip

Learner / Class:
Subject:
Session / Date:
Current corridor width: Narrow / Medium / Wide
Primary corridor owner: Teacher / School / Tutor / other

2) Current Structural Focus

Current object:
Current invariant:
Current lawful move:

Purpose

Shows what the system is actively teaching right now.

3) Current Failure Read

Dominant breach class:
Where it breaks:
Last valid state:

Purpose

Shows what is failing and where repair must begin.

4) Current Repair Read

Active repair route:
Repair success: Yes / Partial / No
Reconciliation restored? Yes / Partial / No

Purpose

Shows whether repair is currently working.

5) Current Transfer Read

Transfer status: None / Emerging / Active / Strong
Second form visible? Yes / Partial / No
Main transfer bottleneck:

Purpose

Shows whether the learner is still local or starting to compress the subject.

6) Current Load Read

Load status: Stable / Wobbly / Collapsed
Current load break point:
Main load trigger: timed / mixed / unfamiliar / chained / other

Purpose

Shows whether the learner can still hold structure under pressure.

7) Current Learner State

CB / PR / TA / UL / LS
Why this state was chosen:

Purpose

Gives the one-label structural summary.

8) Current Corridor Move

Widen / Hold / Narrow / Re-stitch
Why:
Next immediate priority: visibility / repair / transfer / load stability

Purpose

Turns the board into an action panel, not just a display.

The One-Line Runtime Compression

A useful compressed line for any handoff is:

Object -> Invariant -> Breach -> Last Valid State -> Repair -> Transfer -> Load -> Learner State -> Corridor Move

This is the fastest operational summary of ILT.

Subject Overlay Examples

A-Math Runtime Board

Object: quadratic equation
Invariant: equality preservation
Lawful move: factorisation
Dominant breach: B3 Unlawful Transformation
Last valid state: original balanced equation
Repair: return to pre-error line, re-factor lawfully
Transfer: Emerging (algebra to graph link starting)
Load: Wobbly in timed mixed questions
State: PR
Move: Hold

This gives an immediate usable read.

English Runtime Board

Object: paragraph response
Invariant: meaning + coherence
Lawful move: paraphrase with preserved intent
Dominant breach: B2 Invariant Blindness (meaning drift)
Last valid state: original intended idea before rewrite drift
Repair: restore intended meaning, rebuild sentence sequence
Transfer: Active (summary to composition sentence link visible)
Load: Wobbly under timed unseen prompts
State: TA
Move: Hold / light load stabilisation

Science Runtime Board

Object: experimental data set
Invariant: evidence-claim coherence
Lawful move: infer within evidence bounds
Dominant breach: B3 + B8 (overclaim under pressure)
Last valid state: raw observation before unsupported inference
Repair: return to evidence, rebuild claim within condition limits
Transfer: Emerging (graph to explanation)
Load: Collapsed in unfamiliar context
State: UL
Move: Narrow / Re-stitch

The Board as a Handoff Tool

The Runtime Board is especially strong because it can be passed between nodes quickly.

Teacher -> Tutor

The tutor can continue without restarting diagnosis.

Teacher -> Parent

The parent can support without panic or random widening.

Teacher -> AI

The AI can stay inside the same corridor and not hallucinate new routes.

Tutor -> Teacher

The teacher can see what was reinforced rather than receiving vague “we revised.”

Learner -> Self-Study

The learner can revise with a state-aware target instead of vague effort.

This makes the board a coordination artifact, not just a display.

The Board vs the Report Card

This distinction should stay clear.

Report Card

period-based
communicates trend
used for broader handoff
slightly higher-level

Runtime Board

live / current
session-level or near-session-level
operational
used for immediate decisions

So:

The Report Card tells the network the learner’s recent condition.
The Runtime Board tells the node what to do right now.

The Board vs the Lesson Template

This distinction should also stay clean.

Lesson Template

planning and delivery structure
defines what the lesson intends to do

Runtime Board

live state display
shows what the current learner/class condition actually is

So:

The Lesson Template plans the route.
The Runtime Board shows the live flight state.

FENCE Fit

The Runtime Board is deeply FENCE-compatible.

Why?

Because the board’s final control field is the corridor move:

Widen
Hold
Narrow
Re-stitch

This means the board is not just descriptive.
It is a real corridor-control interface.

So the clean law is:

The Runtime Board makes corridor control visible in one view.

S-Curve Fit

The board also lets operators see the learner’s current growth condition without re-reading long reports.

Flat-zone board

Usually shows:

CB / PR
low transfer
visibility weak
move = Narrow or Hold

Inflection board

Usually shows:

PR / TA
transfer emerging
repair improving
move = Hold or light Widen

Rise board

Usually shows:

TA
transfer active
load improving
move = careful Widen

Plateau board

Usually shows:

UL / LS depending condition
subtle breaches
load or precision bottlenecks
move = Hold or targeted Re-stitch

So the board makes the S-curve operationally readable.

Metcalfe Fit

This is one of the strongest uses of the board.

The Runtime Board is the smallest shared state object that can move across many nodes cleanly.

Because it uses the frozen ILT vocabulary, it lets all nodes read:

same object
same invariant
same breach
same repair
same state
same next move

That makes it a high-efficiency shared-ledger artifact.

A clean law:

The smaller the shared state object, the easier it is to coordinate across more nodes.

InterstellarCore Fit

InterstellarCore needs a teaching runtime that is:

scalable
observable
repairable
multi-node readable
AI-compatible

The Runtime Board is one of the most important micro-control devices for that.

Why?

Because it turns a large pedagogy into a live readable state panel.

So inside InterstellarCore:

The Runtime Board is the compact local control surface for the ILT teaching spine.

That is a very strong fit.

ChronoHelmAI Implication

This is a direct control-layer fit.

A ChronoHelmAI-like system can ingest the Runtime Board fields as live teaching telemetry:

current object
current invariant
dominant breach
last valid state
repair success
transfer status
load status
learner state
corridor move

That means the board is also a machine-readable teaching dashboard.

This makes the system more computable and less mystical.

Failure Modes if the Runtime Board Is Missing

Failure Mode A — Too much framework, too little live control

The method exists, but daily decisions stay vague.

Failure Mode B — Handoffs stay too long and too wordy

Support nodes cannot align quickly.

Failure Mode C — The wrong next move is taken

Because the live state is not visible in one place.

Failure Mode D — Everyone remembers different parts

But no one has one compact state panel.

Failure Mode E — AI lacks a compact control schema

So support becomes more generic and less aligned.

The Runtime Board prevents these.

Canonical Summary Block

ILT One-Page Runtime Board v1.0 is the compact control panel for Invariant Ledger Teaching. It compresses the live teaching state into one shared view using the frozen ILT vocabulary: current object, current invariant, current lawful move, dominant breach, last valid state, repair route, transfer status, load status, learner state, and corridor move. It functions as a real-time operational dashboard, a handoff surface across multiple nodes, a FENCE-compatible corridor-control interface, and a compact micro-control device for InterstellarCore-compatible teaching systems.

Copyable Almost-Code Block

ID: EducationOS.Teaching.ILT.RuntimeBoard.v1.0
TYPE: Compact runtime control panel
LAW: If the ledger cannot be seen quickly, it cannot be coordinated quickly.
CORE FIELDS: Object / Invariant / Lawful Move / Dominant Breach / Last Valid State / Repair Route / Transfer Status / Load Status / Learner State / Corridor Move
MINIMUM LIVE BOARD: Object / Invariant / Breach / Repair / Learner State / Corridor Move
RUNTIME READ: Object -> Invariant -> Breach -> Last Valid State -> Repair -> Transfer -> Load -> State -> Move
FENCE FIT: board makes widen / hold / narrow / re-stitch visible in one view
METCALFE FIT: smallest shared state object for fast multi-node coordination
INTERSTELLARCORE FIT: compact local control surface for the ILT teaching spine
OUTPUT: one-page, session-level visibility for immediate aligned action

Next in the strongest sequence is:

ILT Install Checklist v1.0 — the minimum pass/fail checklist to know whether ILT is actually installed, or only being talked about