session 2026-07-17: constitution block drafted-whole — #2/#4/#5 RATIFIED (REVIEWED-60/61, PENDING-60/61), verify-before-compose hook + memory, MEMORY.md compacted

This commit is contained in:
David F Glidden
2026-07-17 16:11:58 +02:00
parent 4bf7f1ad67
commit ed43422bbb
9 changed files with 171 additions and 20 deletions
+18 -2
View File
@@ -471,7 +471,7 @@ DONE + DEPLOYED (a9e5196).
- **`engine_source_binding` kept as ONE entry** (names a relationship across three files that move together; fragmenting recreates the failure). **Dual warning kept** (inline ⚠ + block comment — two reading grains).
- **Required correction (applied):** "…re-anchors ACROSS BOTH REPOS" (descriptive) → **"…REQUIRES re-anchoring across both repos"** (prescriptive — the gate catches the failure; nothing does it automatically; that IS the incident).
- **Change-class FIX** (downgraded from the filed [PROPOSAL] default — documents an already-existing, already-enforced mechanism; adds no gate predicate). **Lane: lightweight in-place edit**, `PENDING.md`/`REVIEWED.md` audit trail sufficient.
- **Durable lane-rule (jurist proposed, executor responded):** ACCEPT "lane tracks change-class" for `graduation-spec.yaml` (machine-data). **NARROW the `.md` generalization** — A2/A4 (REVIEWED-50/51) are FIX-class doctrinal `.md` additions that correctly took the *heavier* freeze+semver lane, because the operative axis for the constitution is *doctrinal-traceability* (a successor must trace doctrine to a dated marker), not change-class; the two coincide only for machine-data files. *[Awaiting jurist accept/narrow of this refinement.]*
- **Durable lane-rule (jurist proposed, executor responded):** ACCEPT "lane tracks change-class" for `graduation-spec.yaml` (machine-data). **NARROW the `.md` generalization** — A2/A4 (REVIEWED-50/51) are FIX-class doctrinal `.md` additions that correctly took the *heavier* freeze+semver lane, because the operative axis for the constitution is *doctrinal-traceability* (a successor must trace doctrine to a dated marker), not change-class; the two coincide only for machine-data files.
- **[ACCEPTED + narrowed by the jurist 2026-07-10** (`hash-locality-ratification-and-lane-narrowing-JURIST-RULING-2026-07-10.md` §2). **Ruled rule:** machine-data files (`graduation-spec.yaml`) — *lane tracks change-class* (the code/git/`test_tools` history is the independent fallback that pins "what was true when"). The `.md` constitution — *lane tracks whether the change touches doctrine a successor must trace to a dated marker*, regardless of change-class (no code-level fallback; the prose IS the sole record). The two axes coincide only for machine-data files. Not "every `.md` edit gets the heavy lane" — a typo/dead-link fix that adds no doctrine does not.**]**
## REVIEWED-54 — PENDING-54 — EPUB footnote pre-processor (verbatim-safe conversion stage) + mega-EPUB split-convert
@@ -559,4 +559,20 @@ DONE + DEPLOYED (a9e5196).
**Date:** 2026-07-16
**Decision:** AUTHORIZED — ratifying the jurist-reviewed PROPOSAL (jurist review PASSED 2026-07-16 with 3 edits applied + the release-mechanism gap closed). Advances REVIEWED-49 · A3.
**Notes:** Trust-attestation baseline conditioning OPERATIVE status. Three dimensions (fixity excluded — automated): provenance-completeness (annual, FLAG) · registry-linkage (annual, FLAG; double-duty for A1's emergent `agent_id` promotion signal) · legibility-to-successor (every 2–3 cycles, HARD FLOOR on failure). Legibility failure = fence-verdicts-unreadable OR fence-evidence-unreadable OR operative-doctrine-not-followable (evidence-alone-floors); degrees above still flag. **Cold-instance audits; jurist adjudicates the result** (neither steward nor jurist audits — both carry participation-context). Release from a floor: a fresh cold-instance pass, jurist-adjudicated. Flag home: `corpus-quality-ledger.tsv` + a dated status-marker line. Fixity stays automated (the audit confirms the automation, never re-hashes by hand). Legibility at 2–3 cycles by design (a load-bearing check run too often turns decorative).
**If AUTHORIZED:** land as a **new spec section** (*Trust Attestation / Self-Audit*, cross-ref §IX) by supersession + semver — new section = a minor bump (**steward's call: v2.0.2 → v2.1.0**). Tag commit REVIEWED-59. Records: PENDING-59; draft `docs/A3-self-audit-PROPOSAL-FOR-JURIST-2026-07-16.md`; ruling `docs/A3-self-audit-PROPOSAL-JURIST-RULING-2026-07-16.md`.
**If AUTHORIZED:** land as a **new spec section** (*Trust Attestation / Self-Audit*, cross-ref §IX) by supersession + semver — new section = a minor bump (**steward's call: v2.0.2 → v2.1.0**). Tag commit REVIEWED-59. Records: PENDING-59; draft `docs/A3-self-audit-PROPOSAL-FOR-JURIST-2026-07-16.md`; ruling `docs/A3-self-audit-PROPOSAL-JURIST-RULING-2026-07-16.md`.
## REVIEWED-60 — PENDING-60 — Citation amendment (#2): specify the adopted CTS-URN model + chamber-minted namespace/boundary + per-scheme coverage attestation
**Date:** 2026-07-17
**Decision:** AUTHORIZED — RATIFIED. Steward ratification, following the jurist editor-gate (2026-07-17, passed on doctrinal soundness + format) with two corrections + one condition discharged.
**Notes:** Ratifies the citation amendment as a **specification** of §IV's already-adopted CTS-URN edition-identity — not a re-adoption. Ratified content: the **chamber-minted CTS-URN namespace** + the **internal (T1) / external (T2, leashed Condition-2) boundary** (the precondition genuinely met — CTS boundary drawn, clean-separation verified against the tier survey, not asserted); **per-scheme in-source anchor recovery** with the routing as **declared data** in `graduation-spec.yaml` (§VII generative principle); the **per-scheme coverage attestation** (§IX-as-precondition) as an **explicitly *partial*** answer to §IX's open silence-as-finding (anchor-scheme silence only; the general question stays open); **work-level as the honest default** (§III's sectionless floor applied); **Decision-1**; and the **additive-only** sidecar fields.
- **Q1 confirmed:** minting inside `urn:cts:` is grammatically valid (not IANA-governed; CHS registry dormant; witness-not-notary) — not an affiliation; a proprietary scheme would lose additive-openness for no gain.
- **Corrections discharged (package Addendum):** Q2 partial-§IX wording applied; Q6 shed/inherit cross-checked #1↔#2 side-by-side (six-for-six identical, (f) "originates" in both — the seam is closed); Q5 additive-only verified against the LOCKED schema (`anchors[].scheme` already present; `citation_coverage[]` a new optional field = FIX).
**If AUTHORIZED:** Land by supersession at **MINOR v2.1.0** (jurist-confirmed defensible; forward-only, 0 Loeb verified). Tag commits REVIEWED-60. **Semver/vehicle — steward annotation here:** land as one **atomic** v2.1.0 supersession together with A3 (REVIEWED-59) [and optionally #4/#5, REVIEWED-61], OR sequence — the jurist's atomicity constraint applies (one edit, not several racing the same version). Production dependencies (the ~3,333-anchor re-stamp, the Region-4 re-extraction, the flagged-token held-queue) run **after** ratification.
## REVIEWED-61 — PENDING-61 — B(i) `licence` provenance axis + B(ii) PREMIS borrow-vocabulary (the two light FIXes, paired)
**Date:** 2026-07-17
**Decision:** AUTHORIZED — RATIFIED (FIX, both). Steward ratification, following the jurist editor-gate (2026-07-17, both passed as FIX) with two wording corrections discharged.
**Notes:** Two gap-fills on already-ratified layers; neither changes what any gate accepts.
- **#4 (B(i)) — `licence` provenance axis (§IV):** the machine-readable rights status of the *edition converted*, holding §IV's **"must carry, where known"** discipline (jurist correction applied — not the weaker "may carry"), with an explicit `unknown` **distinguishable from an unrecorded gap**; graceful-degradation, **never a gate**; value vocabulary = declared data in `graduation-spec.yaml`.
- **#5 (B(ii)) — PREMIS borrow-vocabulary (§V naming note):** names the existing PROV-shaped conversion record with PREMIS's preservation vocabulary — the DTS "borrow-vocabulary, build thin" posture; **naming-only, no data model, pre-authorizes no field** (jurist clarification applied — any future PREMIS-named field is a separate additive amendment on its own FIX review). §V's shape/requirement unchanged.
**If AUTHORIZED:** Land by supersession as FIX. Tag commits REVIEWED-61. **Semver/vehicle — steward annotation here:** (a) fold into the atomic v2.1.0 supersession with #2/A3, or (b) a standalone v2.0.3 patch — the jurist's default-(b) if #2/A3 aren't landing imminently; steward's coupling-of-timing call.