session 2026-07-16: constitution-close block — #1 gated+landed, #3 A3 RATIFIED (REVIEWED-59/PENDING-59), #6/#7/#8/PENDING-53 closed; block-map + candidates register + REVIEWED/PENDING-59 drafts + session memory/ledger/KG
This commit is contained in:
+7
-2
@@ -472,8 +472,7 @@ DONE + DEPLOYED (a9e5196).
|
||||
- **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.]*
|
||||
- **PENDING-47 generalized principle: ratification DECLINED** (relayed text truncated — jurist won't ratify unread text). Stays `[awaiting jurist ratification]`; relay the full principle text to close.
|
||||
**If AUTHORIZED:** LANDED — `_curation/graduation-spec.yaml` `layers:` block (voice_manifest annotated ⚠ + single `engine_source_binding` key + shared-word comment). YAML re-parses; bounded 6-ins/1-del. Governance record: PENDING-53. Tag commits REVIEWED-53.
|
||||
- **[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
|
||||
**Date:** 2026-07-10
|
||||
@@ -555,3 +554,9 @@ DONE + DEPLOYED (a9e5196).
|
||||
- **43-book census CONFIRMED:** V-DSL 952 · V-TEXT 239 · V-SCAN 50 · V-SUSPECT 29 · V-NONE 14 = 1,284; the 43 = V-SUSPECT+V-NONE = the fenced-out tier (no confirmed source) → correctly outside the sweep (a provenance problem, not a coverage gap). Jurist noted (not a condition): these 43 are the same gap-shape PENDING-52 closes going forward — worth attention once the queue moves.
|
||||
|
||||
**If AUTHORIZED:** land by supersession into `graduation-spec.yaml` (make the listed `body_word_conservation` gate enforced + declare the per-tier dispatch) + `verify_graduation.py` (add the per-tier body-conservation gate with source access + tier dispatch) — tag commits REVIEWED-57. Follow-ons: the retroactive sweep run (diagnostic-first) once landed; the sidecar-declaration REVIEW shortcut when convenient; the 43 fenced-out books to source-location. The V-DSL loss residual + revisit-trigger are already in the gate's docstring.
|
||||
|
||||
## REVIEWED-59 — PENDING-59 — A3: CoreTrustSeal-level self-audit
|
||||
**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`.
|
||||
Reference in New Issue
Block a user