session 2026-07-24 (evening): PENDING-71/72 + REVIEWED-72/73 (both jurist-ruled) + evening session memory + KG drift-patterns + skill-harvest

claude/memory/skill-harvest-register.md

@@ -8,7 +8,7 @@ metadata:
   node_type: memory
   type: reference
   originSessionId: a8eb1d46-314e-4545-a133-f747c69ad5b4
-  modified: 2026-07-23T19:26:17.914Z
+  modified: 2026-07-24T12:50:14.817Z
 permalink: claude-memory/skill-harvest-register
 ---
 
@@ -614,3 +614,12 @@ No new skill proposal. Two register notes: **(1)** the S1 proposal **implementat
 | `/glyph-map-source` | **create** | Per-source character-as-image glyph-mapping — the repeatable procedure built + proven on Levi this session (REVIEWED-70/v2.5.0), owed for the other **12+ census-flagged files** (Jung, Derrida, Zibaldone, Lichtenberg, Blake, Donne, …). Steps: unzip EPUB → locate letter-adjacent glyph `<img>` in the XHTML → **extract + VIEW each glyph image** → build `graduation-spec.yaml` `character_as_image.glyph_map` (per-source, EPUB-internal image names) + `decorative` → run `apply_char_glyphs.apply` on the whole source, require **`unclassified=0`** + spot-check pandoc end-to-end. Carries the two disciplines that caught real errors this session: **VERIFY-THE-GLYPH-NOT-THE-FILENAME** (calibre output-numbers ≠ EPUB names) and **MAP-TO-SOURCE-FORM-NOT-CORRECTED** (ş cedilla, not comma-below ș — "correcting" is a Tier-3 source-departing violation). The tool refuses until the map is complete, so the skill's value is the *disciplined authoring procedure*, not enforcement. | 2026-07-23 (built once, 12+ repeats owed) | **PROPOSED** |
 
 *(No skill patches this session: wake-up/wrap-up/symmetria/jurist-package all served as written across a very long run. `/glyph-map-source` is a genuine build-candidate — a hard-won multi-step procedure with two fidelity-trap disciplines, about to be repeated 12+ times; but build-on-need is defensible since the tool already refuses-until-complete. Steward's call on create-now vs build-on-first-repeat.)*
+
+## Harvest 2026-07-24 (evening — PENDING-71/72 both ruled; two disciplines the rulings named)
+
+| Item | Kind | One-line | Origin | Status |
+|---|---|---|---|---|
+| Amendment-process: **reassigned-component check** | **patch** (chamber `CLAUDE.md` Load-bearing disciplines and/or the verification ladder) | Jurist-minted in the REVIEWED-72 ruling: *"when a change reassigns a named component, check what else names it."* F4 moved the born-digital candidate onto pandoc, silently voiding the source-fidelity clause's "different converter (pandoc for V-TEXT)" — the two were ruled the same day and never cross-checked; cost five days and a wave. A cheap, standing check to add where the amendment process is described. **Discipline/governance-posture change → surface for steward, not auto-applied.** | 2026-07-24 (jurist-directed) | **PROPOSED** |
+| Chamber graduation: **build to the constitution, not to a legacy canonical** | **patch** (chamber `CLAUDE.md` Load-bearing disciplines) | Steward-corrected 2× this session: *"we cannot use the extant canon as precedent."* The extant canon is a pre-constitution/pre-fleet legacy body being *brought* to trust; inferring a requirement's absence from what a legacy peer looks like (no-sidecar from peers; frontmatter mirrored from Bringhurst which predates the schema) reproduces the legacy gap. Build to the spec/`graduation-spec.yaml` schema; where the constitution is silent/unbuilt for a tier, name the gap — never fill it from a peer. The legacy-witness principle (REVIEWED-70) applied to graduation *method*. The chamber `CLAUDE.md` already carries the "legacy body / resolve-source-through-Chamber-Sources" framing (2026-07-24 morning); this generalizes it to the graduation bar. **Discipline change → surface for steward.** | 2026-07-24 (steward-directed) | **PROPOSED** |
+
+*(Both are propose-only governance-doc patches surfaced for steward authorization; neither auto-applied. They also chime with jurist-package's existing "trace a ruled finding's inference, not its words" — I violated that this session by quoting REVIEWED-64 without applying it to `sections[]`, so the existing discipline held; no patch needed there, only the reminder that it fired.)*