David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

session 2026-07-09 evening: PENDING-53 (cross-repo re-anchor gap) + P1-clean/EPUB-normalizer-pivot session memory + KG drift-patterns

Browse Source
This commit is contained in:
David F Glidden
2026-07-09 23:38:21 +02:00
parent c9c2049bc1
commit 5d3b017f0a
6 changed files with 88 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PENDING.md
+15
View File
@@ -1385,3 +1385,18 @@ Disposition (verbatim capture + executor action-list: `chamber-library/docs/libr
- **Parked separately (jurist §3, not folded in):** is the graduated corpus uniformly title-first or genuinely mixed? Per-candidate resolution is robust either way.
- **Full FIX for graduate_to_canonical's follow-on line:** `body_word_conservation` (the 3rd declared gate, still "tracked as follow-on, not yet enforced") is untouched here — out of PENDING-52 scope.
**Awaiting only:** steward placement of **REVIEWED-52** (the authorization record).
## PENDING-53 — Hash-locality principle omits the engine consumer surface (re-anchor spans both repos)
**Date:** 2026-07-09
**Tag:** [PROPOSAL]
**Summary:** Complete the graduation-spec `layers` hash-locality principle to name the studium-engine binding surface (`corpus/manifest.yaml` sha · `corpus/sidecars/*.source_sha256` · `corpus/coverage-ledger.json`) that a chamber-canonical re-hash invalidates — the ratified doc currently lists only chamber-internal bindings, and its `voice_manifest: engine-side; carries NO source hash` line mis-frames the engine as non-binding.
**Rationale:** P1 (2026-07-09, `lenracinement` source-clean) re-anchored chamber `catalogue.yaml` but left the engine's manifest sha + sidecar `source_sha256` + coverage-ledger bound to the OLD sha. The engine `ingest_gate` §1.1 hash-binding would have FAILED `weil-enracinement`, but nothing runs it after a chamber edit and the stale ledger hid it — caught only by chance during P2 diagnosis. Root cause is a governed-doc gap: the ratified hash-locality principle enumerates reading-index + source-match (chamber) and declares the engine voice_manifest hash-free — the exact frame that stopped the re-anchor at the chamber boundary. The engine SOURCE manifest + sidecars DO bind and ARE enforced.
**Change-class:** Documentation-completing in substance (names an existing, enforced binding reality; changes no gate acceptance) — but it touches the RATIFIED graduation-spec, so it runs the loop, not a unilateral edit.
**Already landed (operational, not the ratified spec):** `_curation/conversion-runbook.yaml` gained a `reanchor:` block — the full cross-repo binding surface + the completeness check (grep BOTH repos for the old sha; regenerate the engine ledger via `ingest_gate`; the engine gate is the proof). Born-note cites the Weil incident.
**Options:**
1. Complete the graduation-spec `layers` note to enumerate the engine consumer surface + a cross-repo re-anchor pointer to the runbook `reanchor:` block. *(recommended)*
2. Runbook note only — weaker; the mis-framing line stays in the governed doc.
3. Follow-on tool: a `reanchor` helper that, given a canonical, greps both repos for the old sha, updates all bindings, and runs both gates (a real class-fix; larger; own PENDING).
**Recommendation:** Option 1 now (correct the governed doc's frame + point to the runbook); Option 3 as a follow-on if re-hash/re-anchor recurs across the ~30-source Making batch.
**Files affected:** `_curation/graduation-spec.yaml` (layers/hash-locality note). Runbook already updated. No gate-acceptance change.
**Awaiting:** Steward authorization + jurist review (touches the ratified spec).