nx_teacher_rt.nx

RETIRE CANDIDATE -- ORPHANED BYTE-IDENTICAL DUPLICATE (measured 2026-08-15). This file is a byte-for-byte copy of runtime/nx_teacher_lesson.nx: both were 11087 bytes at content-hash h0e2954e3cb38a146 immediately before this note was added (the note is the ONLY difference; re-derive by hashing both). nx_teacher_lesson.nx has THREE importers (nx_teacher_gate, nx_teacher_run, nx_teacher_serve). THIS file has ZERO references anywhere in buildroot -- nx_shelltool grep, 56,311 files, corpus_complete=1. So retiring it cannot cost a capability, and the live twin already carries every function it defines. WHY IT EXISTS: the three importers each carry the comment "the lesson organ the 2026-07-21 dedupe deleted" -- a previous dedupe removed the LIVE organ, broke those three importers, and it had to be restored. This is the leftover of that repair, not a second implementation. ONE FILE, ONE WRITER: both copies append to knowledge/registry/nishi_lessons.tsv, so leaving both buildable invites the two-writers-one-file race. ACTION: `nx_retire_path retire buildroot/runtime/nx_teacher_rt.nx` (rename-only, reversible). NOT done here -- that tool is capability-denied to this seat, and hand-rolling a rename would bypass the guard that refuses protected paths. The header below is INHERITED FROM THE COPY and names nx_teacher.nx, which is a DIFFERENT, REAL organ (3,969 B, the M0->M4 autonomy ladder). Do not trust it. nx_teacher.nx -- the NISHI TEACHER: turn a work-session into a structured, machine-AND-human-educatable LESSON, validate it is S-class, and organize+log it. WHY (operator 2026-06-17): "take our data from [what] we did meaningful for the nishi team and my growth to learn -- machine and human educatable... build a nishi teacher role... organize and log what we need to practice, takeaways, etc." GROUNDED IN LEARNING SCIENCE (Bjork "desirable difficulties", cited evidence in knowledge/registry/teaching_evidence.tsv): a lesson only TRANSFERS if it has - CONTEXT concrete situation (concrete-before-abstract) - TAKEAWAYS the S-class abstractions - CARDINALS durable reusable rules (the MACHINE-applicable principles) -> cardinal log - DRILLS retrieval-practice prompts (the testing effect) -> drill log - EVIDENCE cited provenance ("we do things with evidence & science, ALWAYS") A lesson missing any of these is NOT S-class -> RED (the teacher's liar-kill / publish-gate). The lesson is a markdown file (so the EXISTING wiki ingestor auto-discovers it as /wiki/<slug>); the teacher additionally EXTRACTS the machine-readable structure (cardinals + drills) into registries the Nishi team / spore can ingest. Two audiences, one source. DRY: reuses nx_syscalls only; no new primitives.