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

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

Browse Source
This commit is contained in:
David F Glidden
2026-07-17 00:55:12 +02:00
parent 07538c0ce4
commit 4c49dd22c1
9 changed files with 173 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PENDING.md
+13 -1
View File
@@ -1515,6 +1515,8 @@ Disposition (verbatim capture + executor action-list: `chamber-library/docs/libr
**Date:** 2026-07-13 (original filing) · **REWRITTEN 2026-07-14** (corollary refuted on the record; steward-directed rewrite-not-withdraw).
**Tag:** [PROPOSAL] — change-class PROPOSAL (changes what graduation PRODUCES; per chamber CLAUDE.md "FIX→PROPOSAL when it changes what a gate accepts"). **Jurist editor-gate → steward ratification (REVIEWED-58), FRESH** — the prior editor-gate ruled on the struck corollary's *shape* and does NOT carry.
> **⟳ RESHAPED + LIGHT-GATE PASSED 2026-07-16 — operative proposal text: `chamber-library/docs/PENDING-58-rewrite-FOR-JURIST-2026-07-16.md`** (gate ruling: `…-light-editor-gate-RULING-2026-07-16.md`). The body below is the 07-14 record; the gated proposal supersedes it on these points (Decision-2 rulings + light-gate, all landed): **`app[]` NOT produced** (2(i); was "produced-but-uncredited") · **`anchors[]` originates entirely in the citation amendment (#2)** — #1 produces none (2(ii) + §3(A), confirmed *entailed*) · `sections`/`provenance` = **produced-without-proof** (first-citation needs its own spot-check) · the three sub-questions **RESOLVED** (see Awaiting) · **REVIEWED-58 gates on residual-(b)** (first V-DSL exercise, Block 3), not a 128-book demonstration. Shed/inherit pair reconciled to identical (OQ-5).
**WHY THIS IS A REWRITE, NOT THE ORIGINAL:** The original PENDING-58 hung on a **reconciliation corollary** — `multiset(DSL-full) == multiset(candidate_body) ⊎ multiset(app[])` — which would have turned the corpus-health map's magnitude-diagnosis ("apparatus-shaped") into a **mechanical fact** (reconciles→apparatus / doesn't→body, no eyeballing). **That corollary is REFUTED and struck** — not renamed, not quietly dropped (steward + jurist explicit: a filing that drops its central justification and keeps the conclusion is what this process exists to prevent). The sidecar wiring never *depended* on the corollary; the corollary was a bonus hung on it. This rewrite argues the remaining, untouched case on its own merits.
**THE REFUTATION, on the record** (evidence: 2026-07-13/14 session ledger; the demonstration `scratchpad/proto_reconcile.py` + `decompose_v2.py`; jurist rulings `docs/2b-sidecar-wiring-jurist-*-2026-07-13.md`):
@@ -1543,4 +1545,14 @@ Disposition (verbatim capture + executor action-list: `chamber-library/docs/libr
**History (superseded, preserved — not archived away):** the original corollary filing + its jurist editor-gate + rationale-correction live at `docs/2b-sidecar-wiring-jurist-editor-gate-ruling-2026-07-13.md` + `docs/2b-sidecar-wiring-jurist-rationale-correction-2026-07-13.md` + git history + the 2026-07-13/14 ledger. The refutation is recorded above, in the open.
**Awaiting:** jurist editor-gate + steward ratification (REVIEWED-58), **fresh**. Open sub-questions for the ruling: **(i)** is "produce-but-uncredited `app[]`" the right posture, or should `app[]` not be produced at all until it has a use + a proof? **(ii)** is the `anchors[]` spot-check a ratification pre-condition (block until it clears) or a fast-follow after wiring? **(iii)** does the entanglement finding warrant a standing note on the corpus-health map's interpretation (its buckets are magnitude-shaped, not causal)?
**Awaiting:** ~~jurist editor-gate~~ **LIGHT-GATE PASSED 2026-07-16** → proposal text GATED/operative. **REVIEWED-58 (landing the wiring) gated on residual-(b)** — the first V-DSL gate exercise (Block 3). Sub-questions RESOLVED (07-14 response + light-gate): **(i)** `app[]` → **NOT produced** (datum-not-ledger). **(ii)** `anchors[]` → its own **citation amendment (#2)**; #1 produces no anchors at all. **(iii)** map buckets → a **firing constraint** ("no causal claim from bucket membership"), pinned to the corpus-health map (Block-1 #7).
---
## PENDING-59 — A3: CoreTrustSeal-level self-audit (trust-attestation baseline conditioning OPERATIVE status)
**Date:** 2026-07-16
**Tag:** [PROPOSAL] — conditions the corpus's OPERATIVE status (a new status-gate); lane = freeze + semver (doctrinal-traceability, per the 07-10 lane doctrine).
**Summary:** The periodic trust-attestation adopted as A3 (REVIEWED-49, 07-06), now drafted + jurist-reviewed. Three dimensions (fixity excluded — stays automated): **provenance-completeness** (annual) · **registry-linkage** (annual, double-duty for A1's emergent `agent_id` signal) · **legibility-to-successor** (every 2–3 cycles). Gate strength (OQ-3): **FLAG** (honest-degradation) for the first two; **HARD FLOOR** for legibility *failure*. Legibility failure threshold: fence-verdicts-unreadable **OR** fence-evidence-unreadable **OR** doctrine-not-followable (evidence-alone-floors). **Cold-instance AUDITS, jurist ADJUDICATES.** Release from a floor: a fresh cold-instance pass, jurist-adjudicated.
**Full proposal:** `chamber-library/docs/A3-self-audit-PROPOSAL-FOR-JURIST-2026-07-16.md`. **Jurist review PASSED 2026-07-16** (`…-JURIST-RULING-2026-07-16.md`), 3 edits applied + a mechanism gap closed.
**Files affected (on ratification):** a new spec section (*Trust Attestation / Self-Audit*, cross-ref §IX); a census tool for the two flag dimensions; the cold-instance legibility-audit procedure.
**Awaiting:** ~~steward ratification~~ **RATIFIED 2026-07-16 (REVIEWED-59).** Land as a new spec section by supersession + semver on the steward's version call (v2.0.2 → v2.1.0 suggested). Jurist review passed.