session 2026-07-25: PENDING-75 — kind-scoping the verification criterion (jurist-package filed)

PENDING.md

@@ -1706,3 +1706,14 @@ Disposition (verbatim capture + executor action-list: `chamber-library/docs/libr
 **Awaiting:** steward relay → jurist design-gate. On ruling: build the added-side check per the disposition, then the three-case demonstration (clean PASS · deliberate prose deletion FLAGs · deliberate fabrication-outside-manifest FLAGs), then land atomically with the REVIEWED-72 reference supersession. Related: PENDING-71 (REVIEWED-72), PENDING-69 (`moved_to`/`resolve_review`), REVIEWED-70 (§V glyph).
 **RULED 2026-07-24 — design-gate PASSED; in-scope + atomic with REVIEWED-72** (`docs/borndigital-added-side-fabrication-check-JURIST-RULING-2026-07-24.md`, filed verbatim; Addendum + REVIEWED-74 draft appended to the package). The jurist OWNED the refuted premise (the injector enumerates `converted_markers` on the LOST side, not the added delta — *"the producer must know X is not evidence the producer records X"*; the measurement found it). Shape survives; surface refuted. **Q1 in-scope + atomic on a recorded THREE-PART test** (property unchanged · surface refuted-by-measurement-not-inconvenience · design-gate-reviewed; a change missing any leg is its own cycle — record it so "in-scope" sets no mechanism-drift precedent). **Q2 MULTISET confirmed** (strictly dominates presence: catches new-vocab AND duplication, cancels displacement); reordering residual **scoped to the standing Q3 order-blindness stamp-block** (gate does not verify passage order — demonstrated Eichmann §7), NOT to a converter-behaviour claim. **Q3 two-sided glyph manifest confirmed, COUNT-SCOPED both sides:** added = `Counter` subtraction (a 7th surplus of a declared token still flags); a lost run excused ONLY IF every token is manifest-accounted (partially-accounted run stays flagged — "and nothing more", PENDING-69 Q5 on the loss side). **Q4 authorizes the CLASS** (glyph restoration) not future declared normalizations (each by its own §V review). **Latent:** the 646 `converted_markers` = excusable apparatus (REVIEWED-54 §2), invisible only while the loss side stays run-based → named dependency on any future loss-side count-basing; added=count/lost=position asymmetry = deliberate choice. **Demonstration = FOUR cases** (adds Eichmann regression PASS). Architecture: sibling `resolve_added`, `classify()` byte-identical, V-DSL + §6 sweep do NOT inherit.
 **Awaiting (updated):** steward placement of REVIEWED-74 (draft in the package Addendum) → build `resolve_added` + two-sided glyph manifest test-first → four-case demonstration → land atomically with the REVIEWED-72 §Tiering & Fence reference supersession. Related: PENDING-71 (REVIEWED-72), PENDING-69 (`moved_to`/`resolve_review`), REVIEWED-70 (§V glyph), REVIEWED-54 (§2 markers-as-apparatus).
+
+## PENDING-75 — Kind-scoping the verification criterion (foreclosure check on §Tiering & Fence)
+**Date:** 2026-07-25
+**Tag:** PROPOSAL (candidate; change-class classified in the package Part 6 — jurist to confirm PROPOSAL/MINOR vs FIX)
+**Summary:** Bound the ratified verified criterion to text-bearing kinds and declare a demonstrated-method extension path (with an anti-bypass guard), so a future non-text canonical enters as an additive amendment rather than forcing a re-founding of the load-bearing clause. Claim-scoping, not new doctrine; nothing about images decided or written.
+**Rationale:** The verified criterion silently *defines* verification as prose-word identity — the evidence-tier table (V-DSL/V-TEXT/V-SCAN/V-SUSPECT/V-NONE) presents text-source methods as exhaustive, and tier-1 is "prose-word-identical against its on-hand source." A non-prose work has no tier and no method, so admitting one later is a MAJOR disturbance to the clause the whole trust architecture rests on. Same defect-shape corrected 3× already (one-door Q6, REVIEWED-70 Q1, REVIEWED-72 F4) — an unscoped clause claiming more than its method delivers; applied here prospectively while cheap.
+**Package (self-contained, jurist has no repo access):** `chamber-library/docs/kind-scoping-verification-JURIST-PACKAGE-2026-07-25.md` — hook-passed (GROUNDED-IN §Tiering & Fence + §V + the line_frame Naming note, all quoted verbatim from v2.6.0 read 2026-07-25). Three edits: (1) §Tiering & Fence evidence-tiers preamble — method-declared-for-its-kind + PROPOSAL-with-demonstrated-method extension + the anti-bypass clause (no kind weakens its method by re-declaring); (2) §V three-tiers preamble — tiers bound to text-bearing canonicals; (3) sidecar-schema line_frame naming note — the *declaration principle* generalizes (⚑ corrected off the jurist's "line_frame is the general slot" shape: the field is line-named/five-line-family-scoped; generality attaches to declare-don't-assume, not the field).
+**Gate questions (with leans):** Q1 placement (lean: evidence-tiers preamble, tightest adjacency) · Q2 anti-bypass clause verbatim (lean: keep, it is the separator) · Q3 Edit-3's true subject (⚑ flagged: principle not field) · Q4 change-class (lean PROPOSAL/MINOR/additive-in-effect) · Q5 is Edit 2 needed or subsumed by Edit 1 (lean: keep).
+**Landing:** standalone MINOR supersession (v2.7.0 or steward's version call) — NO in-flight supersession assembling (v2.2.0→v2.6.0 all landed); additive-in-effect (no current canonical changes tier/method → no re-verify storm). Requirement = constitution; which-kinds-exist + their methods = declared data.
+**Files affected (on ratification only, drafted to the Addendum's corrected design):** `docs/chamber-library-specification.md` (§Tiering & Fence + §V), `docs/sidecar-schema-LOCKED-2026-07-12.md` (naming note). Nothing built/run/landed now.
+**Awaiting:** steward relay → jurist design-gate.