session 2026-07-05: close PENDING-48 (Studium V0 jurist gate cleared) + ledger

PENDING-48 closed against the jurist ruling: V0 §2/§5 method-gate cleared with conditions;
fidelity_equivalence@1 doctrine fork; diplomatic-gold flag resolved (modernized -> moot).
Session ledger for 2026-07-05. REVIEWED-N entry owed (steward/jurist).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dsqe1x23NgWaRdiFWSotur

PENDING.md

@@ -1219,3 +1219,25 @@ n=100 random non-Loeb, structured query (title + author-P50, no type). **AUTO 27
 **Jurist RATIFIED** the hash-locality principle + distinct naming + confirmed the attested_pin implementation satisfies the condition (read-of-description caveat: 28/28 accepted on report). 2 small notes (not conditions): `against`→real evidence (HONORED — pins carry the Instrument-B N/M); pins carry implicit re-verify-if-method-revised.
 **FIX-LIST APPLIED (steward "Yes"):** 5 verified FP re-points PINNED to the **permanent Chamber Sources home** (steward correction: pin the permanent home, not the transient library path) with real Instrument-B `against` evidence — the-odyssey, montaigne, lhomme-tome-1, suzuki, berger (5/5 or 4/5). **ARCHIVE-CONTAMINATION FINDING (steward's permanent-home reminder surfaced it):** the FP contamination had reached the permanent archive — `archive_sources.py` had copied WRONG sources under right slugs + `dest.exists()` locked them in; 5 CS copies were the wrong source (0/5) → force-replaced with verified-correct (governed rezip/sha, manifest `corrected-2026-07-04`). **Implication: full archive↔matches reconciliation owed post-gate** (contamination likely in every archived FP). **DEFERRED:** 2 CS-corrected-but-pin-deferred (orthotypo-vol-2, semaison — NO frontmatter, a new corpus-integrity defect beyond the 4 stubs); 4 needs-locate (reverie needs FRENCH ed, meditations/ecrits/nietzsche not on disk — no correct source to pin; the pin mechanism has NO exclusion path → these persist as algorithmic-FPs until an exclusion path or the Axis-A gate). **COMMITTED + PUSHED** the day's chamber-library work (stress-test artifacts, persistence layer, study/tooling docs, 5 pins). `_scratch/` + the nature-of-order-vol-1 untracked file EXCLUDED (not ours).
 **STILL OPEN:** exclusion-path design (for FPs with no correct source) OR rely on the Axis-A gate; the 2 no-frontmatter canonicals' frontmatter repair; the 4 needs-locate source hunts; works-eliot disambiguation; the 2 scope-under-coverage calls; full archive reconciliation; jurist ratification of the work-identity study (item 4).
+
+## PENDING-48 — Studium Engine V0 (verifier contract) — jurist method-gate
+**Date:** 2026-07-05
+**Tag:** [PROPOSAL] — routed to the jurist as a **method gate**. This is the *one named exception* to the engine's steward-direct D-1 governance (cluster-a-data-model.md §0; rebuild-plan §8.5, steward-ruled 2026-07-04): V0 defines *what the engine may assert as verified and when it must abstain*, and everything downstream inherits that standard, so the jurist gates the method before V1 (the byte-existence checker) is built against it.
+**Summary:** The V0 verifier contract + pre-registration is drafted (`studium-engine/docs/spec/v0-verifier-contract.md`, DRAFT). It fixes the claim taxonomy (quoted / constructed / synthesized / ungrounded → verdict registers) and — before any validation data is seen — the pre-registered thresholds for the multilingual/archaic validation (V2). Its D-1 companion, the N0 navigation-tree contract (`docs/spec/n0-navigation-tree-contract.md`), is written together with it (not jurist-gated); N1 may proceed while V0 sits with the jurist. **No V1 code written; the executor holds at this boundary.**
+**Two decisions surfaced for the jurist's gate (leans given, not decided):**
+
+1. **§2 — the definition of "unaltered" (the held literal question; may be doctrine).** The quoted-tier check asks "do these exact words exist, unaltered, at this anchor?" but `text_original` is byte-faithful (long-s, ligatures, original spelling), so byte-for-byte would reject legitimate modernized quotes. Candidate equivalence relations: **(A)** exact bytes (too strict) · **(B)** `normalizer@1` classes (NFC · ſ→s · 7 ligatures · soft-hyphen · whitespace-collapse — the *index* transform) · **(C)** (B)+diacritic-fold (the *search* transform; wrong for a fidelity assertion — é≠e in French/German/Greek). **Executor lean: (B)**, with three conditions — the relation is *versioned and named in the verdict* ("the bound names the equivalence relation"), a near-match under any looser relation verdicts `altered` never `guaranteed`, and diacritic-folding stays out of the fidelity tier. **Jurist ask:** (a) ratify (B) or rule otherwise; (b) rule whether setting/evolving `normalizer@N` for the *guaranteed* tier is D-1 engineering or **doctrine** requiring jurist sign-off per version; (c) confirm diacritics stay out; (d) confirm the surfaced boundary case — **hard-hyphen line-breaks** are a source-cleaning concern, not the checker's to absorb (the checker must not guess dehyphenation).
+2. **§5 — the pre-registered V2 thresholds.** Per (language, tier): primary safety metric = **false-accept rate** on adversarial negatives (injected known-bad: meaning-reversal / near-miss / wrong-span / whole-for-part / translation-as-original), graded on the **one-sided 90% Clopper-Pearson upper bound** (the CI-not-point-estimate rule ratified on PENDING-47), with the underpowered top-up. Pre-committed outcomes: **trust** (U ≤ 5% AND recall ≥ 0.75) / **revise** (5% < U ≤ 15%) / **gate-to-abstain** (U > 15% or no gold → that language's synthesized claims `cannot-verify` by default — honest degradation, a valid completion). **Small-n honesty stated up front:** with the current gold (German ~15–20; French Mauss 17 + Weil; English 26/39) several cells may not reach *trust* even at zero observed false-accepts; the *trust* lever is more adversarial negatives (pre-registered before generation), and a gate-to-abstain is a pre-committed valid result, not a failure. Tier-1 has no statistical bar (decidable) — validated by the deliberate-mismatch suite + orthography tests. **Jurist ask:** ratify the thresholds (5%/15%), the CP-upper-bound application, the small-n disposition, and the adversarial-negative taxonomy; rule what (if anything) is doctrine vs method-engineering.
+
+**Authority for the routing:** rebuild-plan §8.5 (steward-ruled 2026-07-04) — V0 is the one D-1 exception; D-1 stays intact for all other engine decisions (incl. N0, N1).
+**Files affected:** `studium-engine/docs/spec/v0-verifier-contract.md` (V0 DRAFT — revised on the ruling before V1) · `docs/spec/n0-navigation-tree-contract.md` (N0, D-1, informational) · `~/PENDING.md` (this entry). Written, **uncommitted** — held for steward review + push on the steward's word.
+**Awaiting:** jurist method-gate on §2 (the "unaltered" relation + its D-1-vs-doctrine status) and §5 (the pre-registered V2 thresholds), via steward relay. On a clean gate → build V1 to the ratified relation + the deliberate-mismatch suite. On a reshaping ruling → revise V0 before V1. N1 (tree builder) may proceed in parallel under D-1.
+
+### PENDING-48 — JURIST GATE CLEARED 2026-07-05 (steward relayed). CLOSED — REVIEWED entry owed.
+**Disposition: gate clears on both §2 and §5, with conditions.** V1 and V2 unblocked. Ruling folded into `studium-engine/docs/spec/v0-verifier-contract.md` (DRAFT → **v1.0 RATIFIED**, new "Ruling" section) + the fork landed at source in `cluster-a-data-model.md` §5.1.
+**§2 —** (B) ratified (typographic-convention in, orthography out). Ruled **DOCTRINE, not D-1**, with a code-level consequence: **fork the fidelity relation to `fidelity_equivalence@1`** — a frozen constant distinct from `chunker.normalize()`, so a D-1 retrieval-normalizer change can't silently drag the trust floor; every future `fidelity_equivalence@N` needs jurist ratification, `normalizer@N` (retrieval) stays D-1. Diacritics-out confirmed; hard-hyphen-linebreak confirmed as a cleaning-gate concern (cost lands as recall/abstention, not false trust).
+**Cross-cutting flag RESOLVED (executor, verify-before-asking):** gold pairs verified against **modernized** editions — checked the actual source files (Mauss, Weil ×2, Handke all works, March Essay-I): **zero** long-s / fold-ligatures / soft-hyphens; the `œ`/`æ` present (72 in Mauss) are orthographic ligatures `fidelity_equivalence@1` correctly does not fold. ⇒ flag **moot at present gold** (fold clauses inert → "verified" and `guaranteed` can't diverge on glyph grounds). Caveat: reactivates if future gold is drawn from a *diplomatic* edition.
+**§5 —** thresholds ratified as stated (5% / 15% / 0.75; jurist independently confirmed `0/15 → U≈14.2%`). Gate-to-abstain ruled doctrine-**consistent** (refusing the contamination failure mode in advance), not merely tolerated. **Added condition:** negatives-expansion must preserve the original proportional distribution across the five adversarial classes, or pre-register a new distribution before generating. Doctrine = the threshold *values*; D-1 = the CP calc / perturbation code / gold-pair selection. **Coupling recorded (not resolved):** the 5%/15% values are calibrated with the §1 rule-3 evidence-first display guarantee — weakening that display (e.g. a future UI showing a bare scalar) requires re-gating the thresholds.
+**Files touched (recording the ruling):** `studium-engine/docs/spec/v0-verifier-contract.md` (v1.0 + Ruling), `docs/spec/cluster-a-data-model.md` §5.1 (the fork at source), `~/PENDING.md` (this close). **Still uncommitted** — held for steward review + push.
+**Next (unblocked):** V1 (`verify-quote`) against `fidelity_equivalence@1` + the §3 deliberate-mismatch suite; N1 (tree builder) in parallel. Standing conditions carried into the build: the §5 display-coupling, the proportional-expansion rule, the diplomatic-gold caveat.
+**Owed:** a REVIEWED-N entry (steward/jurist) recording this ruling — same as the PENDING-46/47 arc.

claude/memory/session-ledger-2026-07-05.md

@@ -0,0 +1,37 @@
+---
+name: session-ledger-2026-07-05
+description: "Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses."
+metadata: 
+  node_type: memory
+  type: feedback
+  originSessionId: 262afd69-82e0-4a5f-b0df-fcb93a288a6b
+---
+
+# Session Ledger — 2026-07-05
+
+## Returns
+
+- 2026-07-05T11:53 — Wake. Thread validity gate run before synthesis: CONFIRMED (no overnight movement; repos + dotfiles clean). Verified built-state and git state against the substrate rather than inheriting the June record — carrying last session's twice-held trust-prior-pass-frame reflex.
+- 2026-07-05 — **Verify-before-asking:** the jurist's diplomatic-vs-modernized flag — resolved against the actual source files (glyph census: zero long-s/fold-ligatures/soft-hyphens across all gold) rather than assumed or relayed back as a question. Modernized → flag moot at present gold; caveat recorded for future diplomatic gold. Uses reach proactively (CLAUDE.md) instead of adding a round-trip.
+
+## Open horizons
+
+- **Engine (build day, Opus):** V0 + N0 — the two contracts, together (plan §7). V0 = verifier contract + pre-registered thresholds → routes to the jurist (the one named D-1 exception). N0 tree contract must exist before any hand touches the Loeb extractor rebuild (reciprocal obligation, §3.4). N1 can proceed while V0 sits with the jurist.
+- **Corpus:** Region 1.1 — the exclusion path, test-first, surfaced for jurist ratification (chamber corpus-work-map-2026-07-05).
+- **Held literal question:** normalizer@N "unaltered" — engineering (D-1) or doctrine ("the bound must name the edition")? Will the jurist gate V0 clean, or does "what counts as the same words" surface an unanticipated ruling?
+- REVIEWED entries owed for the PENDING-46/47 chamber arc.
+- Skill-harvest backlog awaits a steward authorization pass (last full review 2026-06-05): notably `/model-handoff` (proven end-to-end last session) and `studium-engine tool-evolution-log` (home for V4's pattern-finder retro-gate review).
+- MemPalace 3.3.6 → 3.5.0 available (layers wake-recency fix #1630; likely wing-filter #1665). Read: hold through build day, run scheduled upgrade at a break.
+
+## Confidence to recalibrate
+
+## Authorization moves
+
+- 2026-07-05 — **PENDING-48 filed** (`~/PENDING.md`): routes Studium V0 (verifier contract) to the jurist as a method-gate — the one named D-1 exception (rebuild-plan §8.5). Two decisions surfaced, leans given not decided: §2 the "unaltered" equivalence relation (the held literal question; lean (B) normalizer@1, flagged possibly-doctrine); §5 the pre-registered V2 thresholds (CP-upper-bound; small-n honesty). **Held at the boundary: no V1 code.**
+- 2026-07-05 — V0 drafted (`studium-engine/docs/spec/v0-verifier-contract.md`, DRAFT-awaiting-jurist) + N0 drafted (`docs/spec/n0-navigation-tree-contract.md`, D-1, inhabitable, no jurist gate). Both grounded in code read this session (normalizer@1, sidecar schema, coverage-ledger warrant), not the plan's prose. **Uncommitted — commit+push held for steward's word** (studium is D-1 direct-to-main; not explicitly asked to push).
+- Contamination watch honored: did not let V0 silently decide the doctrine question (surfaced with lean, marked jurist's); thresholds presented as pre-registered-pending-gate, not settled; resisted the pull to build V1 past the boundary.
+- 2026-07-05 — **Jurist gate CLEARED (both §2, §5), with conditions.** Ruling recorded at source, not just relayed: V0 DRAFT→v1.0 (Ruling section); the **`fidelity_equivalence@1` fork** landed in `cluster-a-data-model.md` §5.1 (doctrine split visible at source, per the ruling's explicit instruction); PENDING-48 closed (REVIEWED entry owed). Standing conditions carried: proportional-expansion rule (§5), display↔threshold coupling (§5), diplomatic-gold caveat (§2). V1 + N1 now unblocked. Still uncommitted — commit/push held for steward's word.
+
+## Sub-agent dialogues
+
+## Bypasses