session 2026-06-30 evening: Loom/Mill reconciliation + consolidation substrate reframe + Ars Legendi audit; tool-creep-into-substrate flag proposed

claude/memory/skill-harvest-register.md

@@ -269,3 +269,11 @@ The single place proposed skills live so they don't evaporate between sessions.
 | **structure-from-authoritative-ToC = one engine, two map-producers** | method note (ladder or `/graduate-chamber-source`) | Answer to the long-open unify question: chapter-structure recovery is ONE placement engine (`insert_chapter_headings`: match anchor→unique line→replace-block/insert, fail-loud, dry-run) fed by TWO map-producers — the EPUB **NCX ToC** (`structure_from_ncx`, anchor=`<span id>`) and the OCR **printed page-number** method (ToC printed-page→scan-offset). Honour the work's *declared* structure; never re-infer. | `reference-verification-ladder.md` or the skill | **PROPOSED** |
 
 *(Five, all earned in use today. The gate-PASS-BUT-FALSELY and the prose-word-guard are the load-bearing two — the first is a defect found in the gold standard itself; the second is the reusable faithfulness instrument the whole Musil graduation rode. None created autonomously.)*
+
+### Harvest 2026-06-30 evening (Loom/Mill convergence + the consolidation substrate reframe)
+
+| Element | Kind | One-line | Where it lands | Status |
+|---|---|---|---|---|
+| **Symmetria §3 flag: tool-creep-into-substrate (name genome-or-phenotype before building on a tool)** | Symmetria §3 flag | A convenience tool proposed for one job silently becoming the **durable substrate** (the source of truth) is contamination shape — it solves the immediate need at the cost of inheritability/durability, the wrong *level*. Caught HARD tonight: Calibre, suggested only as "a cheap way to build a catalogue," was about to become the library's substrate (an app-owned `metadata.db` that rewrites files + only Calibre reads → fails the next-hand-can-`cd`-into-it test + byte-preservation). Antidote (now sharpened by the Loom/Mill frame we adopted same evening): before building on a tool, **name whether it is genome (durable, must be plain/inheritable) or phenotype (a disposable view)** — the substrate is plain files + a regenerable manifest; any UI is thrown-away and re-rendered. Kin to `reinvented-governed-tooling-without-checking-it-exists`, one level up (this is about a tool becoming the *substrate*, not about reinventing one). | Symmetria §3 | **PROPOSED** |
+
+*(One, load-bearing — it names the exact wrong-level the steward's "Calibre was only a means" let me catch, and it composes cleanly with the genome/phenotype vocabulary now entering the four-party lexicon. Not manufactured: it was the session's central return. The Loom/Mill reconciliation itself is a one-off artifact, not a skill; the cadence-governor insight lives in the reconciliation doc, not here.)*