session 2026-07-22: PENDING-69 boundary-drop mechanism (drafted→ruled→BUILT, Q7 capstone passed, on branch 21e3499) + /model-handoff skill; REVIEWED-69 awaiting steward placement

claude/memory/knowledge-graph.jsonl

@@ -419,3 +419,5 @@
 {"subject": "claude-code", "predicate": "drift-pattern", "object": "wired-gates-green-seams-broken — the session's two REAL defects (per-spine -f html leaves ALL footnote defs EMPTY with bodies stranded as plain prose; pandoc places defs after the index so the spec trim swallowed them) were invisible to EVERY wired gate (verify_conversion, body-conservation, witness compare — no words lost, only structure detached) and found ONLY by seam probes: reading boundary lines for the engine sidecar, re-running a def-content assertion. Recurrence of the 07-19 session-scale lesson in new dress: probe the artifact's SEAMS (joins, def content, boundary lines), don't trust green. Antidote built: the lane driver's non-empty-defs + count==pairs teeth.", "valid_from": "2026-07-21", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-21-verify-guard-chain-fold-eichmann-graduated.md", "extracted_at": "2026-07-21"}
 {"subject": "claude-code", "predicate": "drift-pattern", "object": "calibration (the Eichmann night): census-through-a-pattern self-caught twice (a [^a-z]{1,40} bridge regex could not match .calibre38 — letters in class names; two adjacency-regex hypotheses returned x0 and were DROPPED, sites localized by token-stream alignment instead); instrument-signature misuse (prose_delta takes TEXT not paths — fed paths it diffed the FILENAMES, the pre/strip ghost-loss, self-caught by chasing the tokens to source); tool-report-vs-write seam (strip_cruft --apply prints transform counts BEFORE the write decision — three distinct refusal causes each read as applied until cmp verified the write). The fold-widening ordering held: real-loss classes excluded BEFORE any fold widened, every fold built on a fully byte-accounted census.", "valid_from": "2026-07-21", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-21-verify-guard-chain-fold-eichmann-graduated.md", "extracted_at": "2026-07-21"}
 {"subject": "chamber-library", "predicate": "one-door-first-landing", "object": "Eichmann graduated 2026-07-21 (chamber 780106b, engine edbaf60): sha 145e6edd, 1,070 lines, kindle_residue 0 (was 4,712), 10 native footnotes ref-def non-empty, engine substrate-caveat RETIRED, ingest_gate 13/13. Class 48→47. Door proven but NOT repeatable: PENDING-69 (REVIEW-hold resolution mechanism) gates the remaining 47.", "valid_from": "2026-07-21", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-21-verify-guard-chain-fold-eichmann-graduated.md", "extracted_at": "2026-07-21"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "trust-by-name — a privileged label/class drawn from a shared vocabulary reads as more-verified than a per-item claim, when the gate never confirmed membership. Caught by the jurist on PENDING-69 Q2 (my 'declared spec-class' lean, overturned to vocabulary-only on the package's OWN Part-II evidence that the gate can't confirm class identity). The honest shape: a label constrains what you may CALL a thing, never certifies what it IS. Kin to the app[]/ABSTAIN shared-name collision family. Antidote: when the substrate proves a gate can't verify a category, don't let a shared vocabulary smuggle it back in as trusted.", "valid_from": "2026-07-22", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-22-pending69-boundary-drop-mechanism-built-model-handoff.md", "extracted_at": "2026-07-22"}
+{"subject": "verify_body_conservation", "predicate": "substrate-fact", "object": "the k-gram body-conservation aligner (classify, k=8) is MOVE-BLIND — a verbatim block >= k tokens matches wherever it lands, so cleanly relocated content is COVERED, not a lost boundary run. Boundary runs are therefore dominated by genuine DROPS (front-matter/ToC/index); `relocation` is the RARE label for reordered/short moved fragments (words present but k-grams don't match at the new position). Reading the gate's verdict code BEFORE designing the PENDING-69 resolution was decisive and corrected the package's own 'NOTES-husk = relocation boundary run' framing (the 8 real Eichmann runs are front-matter + index, no relocation among them).", "valid_from": "2026-07-22", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-22-pending69-boundary-drop-mechanism-built-model-handoff.md", "extracted_at": "2026-07-22"}