session 2026-07-07 (evening): chamber A4+B(iii) spec v2.0.2 + A1 Agent/Nomen registry v1 (REVIEWED-49/51); /wake-up + /wrap-up rewired off MemPalace to the files layer (wind-down item 3)

PENDING.md

@@ -1322,4 +1322,40 @@ Disposition (verbatim capture + executor action-list: `chamber-library/docs/libr
 **Files affected (on ratification):** `chamber-library/docs/chamber-library-specification.md` (§I new subsection; version treatment per lane call). No code/gate change.
 **Awaiting:** jurist editor-gate (format + doctrinal soundness) + steward ratification, per §Governance & Amendment. A4's scope-citation redirect is sequenced after this lands.
 
-**RULED + LANDED 2026-07-07 (REVIEWED-50).** Editor-gate PASSED (doctrinal soundness approved; §2 trust-thesis bridging clause ADDED — distinguishes *arrangement-honesty* from §I's *fidelity* sense of trust; §3 "must" confirmed conceptual-entailment, FIX-class holds; no A4 leakage). Placement **§I CONFIRMED**; lane **CONFIRMED v2.0.1 patch supersession**. **LANDED:** `chamber-library-specification.md` bumped v2.0.0→v2.0.1 (§I subsection added, header supersession note); v2.0.0 archived immutable (`chamber-library-specification-v2.0.0.md`, byte-identical); chamber `CLAUDE.md` version pointer updated. Steward places REVIEWED-50 in `~/REVIEWED.md`. chamber-library uncommitted (Seb's Gitea; steward's commit call). **NEXT: A4 scope-citation redirect** (now that A2 has a ratified home to point to), then the REVIEWED-49 tail; then the verification-architecture `[PROPOSAL]` (steward-sequenced priority).
+**RULED + LANDED 2026-07-07 (REVIEWED-50).** Editor-gate PASSED (doctrinal soundness approved; §2 trust-thesis bridging clause ADDED — distinguishes *arrangement-honesty* from §I's *fidelity* sense of trust; §3 "must" confirmed conceptual-entailment, FIX-class holds; no A4 leakage). Placement **§I CONFIRMED**; lane **CONFIRMED v2.0.1 patch supersession**. **LANDED:** `chamber-library-specification.md` bumped v2.0.0→v2.0.1 (§I subsection added, header supersession note); v2.0.0 archived immutable (`chamber-library-specification-v2.0.0.md`, byte-identical); chamber `CLAUDE.md` version pointer updated. Steward places REVIEWED-50 in `~/REVIEWED.md`. chamber-library committed `34c39f1` (Gitea). **NEXT: A4 scope-citation redirect** (now that A2 has a ratified home to point to), then the REVIEWED-49 tail; then the verification-architecture `[PROPOSAL]` (steward-sequenced priority).
+
+## PENDING-51 — A4 + B(iii): the corpus-as-data framing term, and the scope-warrant it does not carry (one coupled §I subsection)
+**Date:** 2026-07-07
+**Tag:** [FIX] change-class — a spec amendment, so it runs the §Governance & Amendment editor-gate (executor drafts → jurist editor-gates format + doctrinal soundness → steward ratifies). **Filed for that gate, NOT for direct implementation.** The spec is never edited in place; this lands by v2.0.1→v2.0.2 patch supersession after ratification. Advances REVIEWED-49 · A4 + B(iii). Sequencing precondition MET: A2's preamble landed (REVIEWED-50, `34c39f1`), so A4 now has a ratified home to point to.
+**Summary:** One new §I subsection that (B(iii)) introduces 'collections as data' into the spec as a framing term worded **computational-tractability sense only**, and (A4) records — in the same breath — that this framing does **not** supply the corpus's bounded/personal scope warrant; that warrant is the A2 partiality preamble, not the Santa Barbara Statement's Principle 4.
+
+**Diagnosis (verify-against-the-substrate, not the brief):** grep of the live spec (`chamber-library-specification.md`) for `collections?[ -]as[ -]data` returns **zero hits** — the phrase, and the refuted Principle-4 scope-citation, are present only in the research briefs and the RULING, never in the constitution. So **A4 is preventive/recording, not a redirect-in-place** (there is no bad citation in the spec to move); and **B(iii) is the first entry of the term into the spec.** They are logically one edit — A4 is the boundary-clause on B(iii)'s introduction — so they land as one subsection, honouring the RULING's flag ("(iii)'s text must use 'collections as data' only in the computational-tractability sense; do not reintroduce the refuted scope-justification through drafting"): the boundary is written *into* the introduction.
+
+**Proposed placement:** a new subsection under §I (The trust thesis), immediately **after** 'On the partiality of the arrangement' (the A2 preamble it points to). Tag `[NEW — A4 + B(iii) · REVIEWED-49]`.
+
+**Proposed amendment lane:** **v2.0.1 → v2.0.2 patch supersession** — same shape the jurist confirmed for A2: substantive-but-non-normative (adds a doctrinal subsection, not a typo → not the errata lane; no gate change → not a MAJOR re-verify). Rationale text only; **no consumer re-verification.** Defer to jurist per §Governance & Amendment.
+
+**Drafted subsection text (house voice; single-quotes; Canadian spelling; British punctuation — a draft for the jurist's editor-gate and the steward's voice):**
+
+> ### The corpus as data — and the warrant it does not carry  `[NEW — A4 + B(iii) · REVIEWED-49]`
+>
+> *§I grounds the library's trustworthiness in fidelity; the subsection above grounds the arrangement's trustworthiness in owned partiality. This subsection names, in the field's own vocabulary, what the corpus is built to be — and marks one boundary that vocabulary does not cross.*
+>
+> In the language of library science, the Chamber is a **collection as data**: a corpus shaped so that a reasoner — the Studium Engine — can compute over it directly, not only a shelf for human reading. The Santa Barbara Statement on *Collections as Data* names, in the field's terms, the posture this spec already enforces by other means — its Principle 8 grounds trust in 'the technical integrity of the data as well as its provenance' (§IV–§V) and requires stewards to 'acknowledge absences and areas of uncertainty' (§IX's coverage-ledger and honest-degradation disciplines). The term is adopted as **framing only**: it says what the corpus *is to the field*. It adds no gate and changes nothing any gate accepts.
+>
+> Its reach is bounded in one respect, recorded here so it cannot later be over-drawn. 'Collections as data' warrants the corpus's **computational tractability** — its fitness to be read by a machine. It does **not** warrant the corpus's **bounded, personal scope.** That warrant is the owned partiality named above (Berman, Olson). The Statement's Principle 4 ('collections as data designed for everyone serve no one') is sometimes enlisted for it, but Principle 4 concerns a different thing — designing a collection *for* an intended community of use — not the epistemic standing of a bounded, personal curation; a deep-research review (2026-07-05) found the scope-licensing reading refuted by two of three independent verifiers. The scope rests on a declared standpoint, not on a data-posture; the two pillars are kept distinct so that neither borrows the other's authority.
+
+**Primary-source verification (2026-07-07 — steward-directed 'verify now', before the gate):** fetched the primary Santa Barbara Statement (`collectionsasdata.github.io/statement`). **Principle 8 CONFIRMED verbatim** — 'the technical integrity of the data as well as its provenance' + 'acknowledge absences and areas of uncertainty' (draft now anchored to these exact phrases). **Principle 4 CORRECTED** — verbatim it reads 'Collections as data designed for everyone serve no one. Specific needs inform collections as data development'; it *does* concern designing for specific communities, but as **audience-fit of a data product**, not the **epistemic warrant for a bounded/personal curation**. The brief's flat shorthand ('does not license scoping to one named community') was imprecise against the primary; the draft now states the precise distinction (audience-design ≠ scope-warrant). A4-shaped error avoided on my own draft by reading the source. Relay brief for the editor-gate: `chamber-library/docs/library-science-A4-Biii-FOR-JURIST-2026-07-07.md`.
+
+**Files affected (on ratification):** `chamber-library/docs/chamber-library-specification.md` (§I new subsection + header supersession note, v2.0.1→v2.0.2); freeze `chamber-library-specification-v2.0.1.md` (byte-identical immutable); chamber `CLAUDE.md` version pointer. No code/gate change.
+**Awaiting:** jurist editor-gate (format + doctrinal soundness) + steward ratification, per §Governance & Amendment. On ratification → land by patch supersession, tag commit REVIEWED-51. This closes the A4 + B(iii) items of the REVIEWED-49 action-list; remaining tail = A1 registry (hot-path read first), A3 PROPOSAL, B(i)/(ii), C reconciliation-target.
+
+**JURIST EDITOR-GATE RULING 2026-07-07 — PASSES 1/2/4/5 as drafted; Q3 gated on one fact, now CONFIRMED (verbatim ruling: `chamber-library/docs/library-science-A4-Biii-RULING-2026-07-07.md`).**
+- **Q1 (audience-design ≠ scope-warrant):** sound, confirmed as drafted — "different *kinds* of claim" (Principle 4 instrumental / scope-warrant normative); the primary-source correction is "the right level of precision."
+- **Q2 (no leakage):** confirmed, "stronger than a minimal pass" — naming Principle 4 to refute it in the same breath is the safer construction (pre-empts a future reader making the association independently).
+- **Q3 (§IX cross-ref):** ruled *confirm-don't-default-soften.* **Executor confirmed by §IX substrate read → Case A:** §IX's own `Still open` text settles census→coverage-ledger, evidence-tier column, and the freshness invariant (honest-degradation named verbatim there); leaves open ONLY silence-as-finding, explicitly separated. Both cited terms independently live, neither entangled → **citation stands exactly as drafted, both terms, NO edit** (one-word fallback not triggered).
+- **Q4 (placement + lane):** confirmed, no redirect — §I-after-A2, v2.0.1→v2.0.2 patch supersession.
+- **Q5 (voice):** no changes required — single-quotes / Canadian spelling / British punctuation clean; 2-of-3 hedge appropriately non-unanimous.
+**STATUS: gate fully passed; draft final (no edit). Ratification pending — steward places REVIEWED-51, NOT pending revision.** On ratification the executor lands: freeze `chamber-library-specification-v2.0.1.md` (byte-identical immutable) → bump canonical v2.0.1→v2.0.2 (subsection after the A2 preamble + header supersession note) → chamber `CLAUDE.md` pointer → commit tagged REVIEWED-51 (Gitea; steward's commit call).
+
+**RATIFIED + LANDED 2026-07-07 (steward ratified; REVIEWED-51).** Committed `7d1d8d3` (local; not pushed — steward's Gitea call). v2.0.1 frozen byte-identical (`cmp`-verified, 763 lines) → `chamber-library-specification-v2.0.1.md` immutable; canonical bumped v2.0.1→v2.0.2 (subsection *'The corpus as data — and the warrant it does not carry'* after the A2 preamble + v2.0.2 header supersession note); chamber `CLAUDE.md` pointer updated. **Bounded-diff verified** — canonical change = exactly the title tag + header note + the new subsection; CLAUDE.md = only the pointer line. Audit trail committed: `library-science-A4-Biii-{FOR-JURIST,RULING}-2026-07-07.md`. REVIEWED-51 draft left on steward's Desktop for placement in `~/REVIEWED.md`. **Closes A4 + B(iii).** REVIEWED-49 tail: A1 registry (retrieve.py hot-path read first), A3 PROPOSAL, B(i)/(ii), C reconciliation-target.