session 2026-07-23: PENDING-69 closed + PENDING-70 (ruling received) · REVIEWED-69/70 placed · v2.4.0+v2.5.0 · character-as-image finding + glyph-mapping built · session record + KG + glyph-map-source proposal

claude/memory/knowledge-graph.jsonl

@@ -421,3 +421,8 @@
 {"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"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "reframe-drops-the-condition's-telos — reframing a RULED condition by what it literally required, not what it was FOR (its purpose). Caught by the jurist on PENDING-70 Q2: my legacy-body reframe ('the classes the body produces') faithfully replaced the witness requirement but DROPPED the judgment-cost test the condition existed to enforce, and was unbounded/self-fulfilling. A faithful 'reframe' that answers a neighboring question is a miss. Antidote: trace the condition's PURPOSE (here: can a human classify judgment-requiring divergences tractably at scale?), state the replacement in advance of the evidence that satisfies it. Kin to transcribe-ruled-finding-inverts-inference, one level up — the condition's telos, not its words.", "valid_from": "2026-07-23", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-23-reviewed69-70-v2.4-v2.5-character-as-image-glyph-mapping.md", "extracted_at": "2026-07-23"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "assert-from-derivation-not-substrate RECURRENCE (glyph-mapping) — verify-the-glyph-not-the-filename caught TWO of my own errors at the tail of a long session: (1) I keyed the glyph-map on calibre's 000042-style OUTPUT numbers (a derived identifier from its conversion-time renaming) instead of the EPUB-internal names; (2) I inferred Brașov's glyph as comma-below ș from the place-name's standard orthography — the source image is ş CEDILLA, and mapping to ș would have been the exact Tier-3 source-departing 'correction' the whole arc forbids. VIEWING the 4 source images corrected both. Existing consolidated flag (Symmetria §3 assert-from-derived); the discipline earned its keep even when exhausted.", "valid_from": "2026-07-23", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-23-reviewed69-70-v2.4-v2.5-character-as-image-glyph-mapping.md", "extracted_at": "2026-07-23"}
+{"subject": "chamber-library-specification", "predicate": "operative-version", "object": "v2.4.0", "valid_from": "2026-07-23", "valid_to": "2026-07-23", "confidence": 1.0, "source_file": "session-2026-07-23-reviewed69-70-v2.4-v2.5-character-as-image-glyph-mapping.md", "extracted_at": "2026-07-23"}
+{"subject": "chamber-library-specification", "predicate": "operative-version", "object": "v2.5.0 — lands the PENDING-70 ruling (REVIEWED-70): Q1 witness-comparison claim-scope split (curated vs legacy) · Q3 §V Tier-3 alteration-by-omission (character-bearing images are content) · Q4 legacy-fidelity-not-self-certifiable; declared data = reframed scale_application substitute condition + witness_class + character_as_image glyph-map/census", "valid_from": "2026-07-23", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-23-reviewed69-70-v2.4-v2.5-character-as-image-glyph-mapping.md", "extracted_at": "2026-07-23"}
+{"subject": "character-as-image-hazard", "predicate": "remedy-mechanism", "object": "chamber-library/scripts/apply_char_glyphs.py (REVIEWED-70/v2.5.0) — letter-adjacent glyph <img> -> declared SOURCE Unicode; REFUSES unclassified (attest-never-default); wired into convert_lane_borndigital.py as the Q3 hard precondition (an imaged source without a complete policy is refused). Levi glyph-map DEMONSTRATED; per-source maps owed for the other 12 census-flagged files", "valid_from": "2026-07-23", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-23-reviewed69-70-v2.4-v2.5-character-as-image-glyph-mapping.md", "extracted_at": "2026-07-23"}