🔧 Auto-commit from sysupdate on 2026-07-05 22:41

2026-07-05 22:41:29 +02:00
parent d707c5f670
commit 9ca673fe50
4 changed files with 65 additions and 2 deletions
@@ -16,6 +16,8 @@ metadata:

 ## Open horizons

+- 2026-07-05 — **Repo CLAUDE.md files + frontmatter census + freshness mechanism.** Drafted `chamber-library/CLAUDE.md` + `studium-engine/CLAUDE.md` (pointer-style; chamber=governed, engine=D-1; uncommitted, for steward review). Ran the read-only frontmatter census → `chamber-library/_curation/frontmatter-census-2026-07-05.md`: **332 non-Loeb, only 11 (3%) conformant**; 204 missing ≥1 un-fabricatable provenance field; 109 no-frontmatter. **Loeb (952) OUT of the sweep** — their v2 frontmatter comes at Region 4 reconversion (steward-confirmed; matches the map). Migration plan drafted (generative-from-spec; phased M/P/C; honest-unknown marker needs ratification) — sweep is `[needs-authorization]`. **Freshness → skill-harvest register:** event-based `/wrap-up` check (challenged the steward's count-threshold: pointer docs → count fires on noise; event = tool/discipline/governance/term change) + optional git staleness canary (prompts, never auto-writes). All uncommitted (chamber can't push — skemantix down).
+
 - **Engine (build day, Opus):** V0 + N0 — the two contracts, together (plan §7). V0 = verifier contract + pre-registered thresholds → routes to the jurist (the one named D-1 exception). N0 tree contract must exist before any hand touches the Loeb extractor rebuild (reciprocal obligation, §3.4). N1 can proceed while V0 sits with the jurist.
 - **Corpus:** Region 1.1 — the exclusion path, test-first, surfaced for jurist ratification (chamber corpus-work-map-2026-07-05).
 - **Held literal question:** normalizer@N "unaltered" — engineering (D-1) or doctrine ("the bound must name the edition")? Will the jurist gate V0 clean, or does "what counts as the same words" surface an unanticipated ruling?