PENDING-69: one-door REVIEW-resolution mechanism (session 2026-07-21)

PENDING.md

@@ -1640,3 +1640,14 @@ Disposition (verbatim capture + executor action-list: `chamber-library/docs/libr
 **Evidence:** `chamber-library/docs/one-door-eichmann-pilot-REPORT-2026-07-19.md` (F3/F4 + §9 flag-2 byte-census) + `…-JURIST-RULING-2026-07-19.md` §4 + `_curation/eichmann-pilot-2026-07-19/` (harness + census data).
 **Files affected (on authorization):** `_curation/conversion-runbook.yaml` (routing) · `chamber-library/CLAUDE.md` (fleet/terminology lines) · the PENDING-56 record layer (amendment cross-ref) · `_curation/graduation-spec.yaml` if the lane is encoded as declared data.
 **Awaiting:** Jurist design gate (steward to relay). **Package DRAFTED 2026-07-20** — `chamber-library/docs/per-tier-conversion-lanes-JURIST-PACKAGE-2026-07-20.md` (the first exercise of the `/jurist-package` skill; hook-passed, GROUNDED-IN §V Tier-2/Tier-3 + conversion-record + §Governance + PENDING-56/REVIEWED-56 D1 + the pilot ruling §4 + report F3/F4/§9, all quoted verbatim). Five gate questions posed (Q1 landing · Q2 lane-boundary · Q3 re-widening-class · Q4 eligibility-reach · Q5 one-door-interaction). Executor lean: **no new constitutional text** — §V already forbids the acts (prophylactic uncatalogued Tier-2 + Tier-3 word alteration); the amendment operationalizes §V as a front-end eligibility rule (census-before-trust) + declared-data routing (`conversion-runbook.yaml`) + a REVIEWED superseding REVIEWED-56's D1 clause; re-widening gated on a fresh byte-census, not a changelog. **RULED 2026-07-20** (`chamber-library/docs/per-tier-conversion-lanes-design-gate-JURIST-RULING-2026-07-20.md`, filed verbatim; dispositions in the package Addendum): proposal SOUND, compliance framing confirmed. **Q1 SPLITS** — III.2 lane assignments = declared data; **III.1 eligibility rule = CONSTITUTIONAL** (overrules the executor lean — §V is silent on *who must demonstrate compliance, when, by what evidence*, the gap PENDING-56 fell through; A3 legibility) → one-line §V note, MINOR → v2.3.0, folded atomically with the queued one-door text. **Q2** boundary named by MECHANISM (any source class whose Docling path routes through the HTML backend; presently = all born-digital EPUB); over-inclusion is FREE not a cost. **Q3** re-widening = FIX, conditioned on the census SPECIFIED as declared data (sample · char-classes · whether partial preservation passes). **Q4** general, gating ADOPTION not use. **Q5** confirmed + **DISCHARGED** — graduation-record check ran 2026-07-20: **verified-zero** (zero EPUB-via-Docling in canon ever; only Docling file = Bringhurst PDF; window added only 11 Loeb DSL; 0 re-conversions) → purely forward-looking, no live breach. Forward item (unconditioned): the **per-conversion typography gate** (byte-census wired per-conversion, closes the §V Tier-2 blind spot) — named horizon, future PROPOSAL. **REVIEWED-67 draft in the package Addendum; awaiting steward placement.**
+
+## PENDING-69 — One-door V-TEXT graduations REVIEW-hold structurally: the boundary-drop resolution mechanism
+**Date:** 2026-07-21 *(numbered 69: REVIEWED-68 was consumed by the v2.3.0 placement gate with no paired PENDING)*
+**Tag:** [PROPOSAL] — changes what the body-conservation gate accepts (a REVIEW-resolution path) → change-class PROPOSAL per §Governance.
+**Summary:** The first one-door landing (Eichmann, 2026-07-21, chamber `780106b`) surfaced a structural seam: `verify_body_conservation`'s V-TEXT verdict is `REVIEW if boundary_runs`, and the graduation-spec's mandatory trims (front matter, ToC, index) ARE boundary runs by construction — so **every trimmed one-door V-TEXT graduation holds at the wired door with no mechanism to consume the human identification** the REVIEW verdict requests. The Eichmann hold was reconciled 1:1 against the declared `trim.drop` list (interior_loss ZERO in both runs), the identification performed under the steward's live directive, and the move completed manually with the wired REVIEW verdict preserved in the run record — honest, but not repeatable at class scale (47 files remain).
+**Rationale:** REVIEWED-57 ruled "REVIEW holds (human drop-vs-keep identification)" without specifying how a performed identification reaches the gate; the one-door trims (REVIEWED-66/v2.3.0) made the collision structural. Attest-never-default applies: the resolution must be a positive, attributed attestation, never a bypass flag.
+**Options:** **(a)** an attested boundary-drop declaration the gate consumes — the candidate (or a per-run declared-data entry) carries the identified drop classes (declared-trim / relocation) with by/date, and the gate re-derives the boundary runs and PASSES only those fully covered by the attestation (RECOMMEND — the identification becomes checkable data, the gate stays the enforcer); **(b)** the gate learns the trim classes itself (compare against the trimmed reference) — larger, and hides the human step; **(c)** status quo + manual completion per file, hold recorded each time (honest but unwired — the gap-shape this arc keeps closing).
+**Recommendation:** (a), design brief FOR-JURIST before code (gate-acceptance territory).
+**Files affected (on authorization):** `scripts/verify_body_conservation.py` or `scripts/graduate_to_canonical.py` (the gate's REVIEW consumption), `_curation/graduation-spec.yaml` (the attestation shape as declared data), `scripts/test_tools.py`.
+**Evidence:** `_curation/tool-evolution-log.md` 2026-07-21 (the landing record; the two wired-door runs both REVIEW-held on exactly the 8 declared-trim boundary runs); the door's own dry-run output preserved in the session record.
+**Awaiting:** Steward reading; jurist design gate on the attestation shape.