session 2026-08-08: REVIEWED-97 (vi disposition) placed + REVIEWED-98 draft; PENDING-114 authorized, PENDING-115 filed

2026-08-08 12:53:11 +02:00
parent 65ff40710d
commit 1a6cdf6cf1
11 changed files with 442 additions and 7 deletions
@@ -1464,3 +1464,74 @@ This is the positive-control standard running **forward** in time rather than ba
 **Awaiting:** Steward disposition of (vi), which gates step 2 of the remediation order.
 ---
 ## PENDING-114 — Scripture quoted inside a host text, unmarked: a live instance in Harrison, and a class no detector reliably sees
 **Date:** 2026-08-08
 **Tag:** [HARDENING]
 **Related:** REVIEWED-96 (Q1, Q3) · PENDING-113 (the (vi) remediation) · REVIEWED-97 (PENDING-113) if placed. **Split out of the (vi) work deliberately** — it is a new finding, not supporting evidence for that disposition, and filing it inside one would be how it evaporates (the REVIEWED-95 shape PENDING-113 already names).
 **Summary.** `harrison-dominion` quotes the Gospel of Mark, with verse numbers, inside its own prose; the sidecar declares three sections all inheriting the file voice, so **Mark 16:7–8 is currently served as `voice: harrison`, citable, with no marking of any kind.** This is a second live instance of the class REVIEWED-96 was convened over — and the first one that is scriptural.
 **The instance, measured.** `chamber-library/canonical_texts/traditions/critical_modernity/phenomenology/the-dominion-of-the-dead-harrison.md` L426 carries *"…and they said nothing to anyone, for they were afraid" (vv. 7–8)*. (`harrison-dominion` is the **manifest id**, not the filename — the two differ for this source, and an earlier draft of this entry cited a file that does not exist.) `studium-engine/corpus/sidecars/harrison-dominion.meta.json` declares **3 sections** — 1 `text`, 2 `apparatus` — and **none carries a `voice` override**, so the whole body resolves to the catalog voice. The corpus therefore holds Mark's words attributed to Harrison, exactly as it held Stevens, Rilke and Ungaretti (session 2026-08-07 night).
 **Why this is a class and not a span.** The obvious detector — scan for scriptural reference markers — was run across all 14 manifested sources and **does not discriminate**. It puts 7 of 14 in range, but the hits are heterogeneous in kind: Weil's *Gravity and Grace* references to the Upanishads and the Gita are **mentions**, not quotations (verified by reading them); Harrison's is an actual quotation with verse numbers. A marker census cannot tell those apart, so its output cannot be trusted as either a finding or an all-clear. This is the *census-by-mechanism-not-proxy* discipline, and the proxy fails here.
 **The harder half.** The quotation in Harrison carries **no quotation marking in the sidecar at all** — Harrison has zero `quotation` sections. So no sidecar-based detector can see it either; the only signals are in the prose (verse citations, quotation marks, lead-in formulae), which is precisely the intra-line class that session 2026-08-07 measured at ~6,455 runs across 8 sources, ~94% of them intra-line and therefore not expressible at the current section granularity.
 **A point for the per-source note, not resolved here (jurist).** Mark's own authorship is traditionally attributed but treated by scholarship as composite and redacted — closer to the Mahābhārata's situation than to the Qur'án's claim of direct transmission. Harrison's own text says as much at L426, noting the final ten verses are later additions. A `scriptural` bucket would have flattened this pairing too: it is a third distinct claim, alongside *śruti* and revelation-through-a-Prophet. Reasoning: `studium-engine/docs/voice-non-individual-origin-2026-08-08.md` §3.
 **Options.**
 - **(a) Fix the span.** Mark the Harrison passage and stop. Cheapest, and leaves the class untouched — the shape `118f411` already took once.
 - **(b) Census the class properly**, by running a detector whose recall is *demonstrated on real material* rather than assumed: candidate signals are verse-citation patterns, lead-in formulae, and marked quotation runs, each scored against a hand-read sample with known answers before any corpus claim is made.
 - **(c) Accept the limit explicitly.** Declare that unmarked intra-line quotation is not currently detectable, record the exposure, and gate the claim rather than the corpus — the honest-degradation route.
 **Recommendation: (b), then (c) for whatever (b) cannot reach.** (a) alone repeats the error this thread exists to correct. The discrimination gate applies with full force: a detector must be shown to separate a known-positive (Harrison/Mark) from a known-negative (Weil's mentions) before its silence over any other source is read as absence.
 **⚠ Not to be read as a corpus-wide claim.** This entry establishes **one** verified instance and **one** demonstrated non-instance. It does not establish how many others exist. The marker census above is reported as a failed instrument, not as a count.
 **Files affected:** none yet. Remediation would touch `corpus/sidecars/harrison-dominion.meta.json` and, if (b) is authorized, add a detector under `engine/` with its own test floor.
 **Awaiting:** Steward authorization of (b).
 ---
 ## PENDING-115 — Two mechanism defects that block remediation step 3 regardless of any ruling: a served role the ledger does not call served, and a warrant scope computed per source
 **Date:** 2026-08-08
 **Tag:** [HARDENING]
 **Related:** REVIEWED-97 (PENDING-113) step 3 · REVIEWED-96 · D-4. **Filed separately on purpose.** Both were found while drafting the (vi) disposition and were recorded only in `studium-engine/docs/vi-disposition-DRAFT-2026-08-08.md` §4 — a repo document, not the register. The jurist's own words this session: filing a finding as supporting colour inside another item is how findings evaporate. Checked before filing: **0 mentions of either defect anywhere in `~/PENDING.md`**.
 **Summary.** Remediation step 3 sets `citable: true` on `role: quotation` sections. Two independent defects make that step unsafe today, and neither depends on how (vi) or the `quotation-in` × `translation-of` composition is ruled.
 **(a) A `quotation` section is searchable but is not classified as served.**
 `engine/ingest_gate.py:189` writes `"class": ROLE_CLASS.get(s["role"], s["role"])`, and `ROLE_CLASS` has keys for `text`/`paratext`/`apparatus`/`reference` only — **no `quotation`, no `translation`** — so the fallback stores the role name itself. Meanwhile `chunker.SERVED_ROLES` **does** include `quotation` and `translation`, so such a section is chunked, searchable and quotable once citable. `engine/retrieve.py:169` scopes on `classification = 'served'`.
 Measured in the live ledger (Mauss): **12 rows `'quotation'` · 13 rows `'served'` (191 chunks) · 3 `'apparatus'` · 1 `'paratext'`**; the four classifications in use corpus-wide are exactly those. After step 3 the twelve quotation sections would be **chunked, searchable and citable while sitting outside the scope the coverage ledger declares was searched** — so `served_sections` / `served_chunks`, the numbers the engine reports as its own coverage, would understate what it actually searched.
 D-4's model has three states — served, paratext-inert, apparatus. This is a fourth: **search-active, not ledger-served.** Constraint #4 (honest degradation) is the clause it violates: the engine would be misreporting its own extent.
 ⚠ `translation` carries the identical gap and it is **presently latent by absence, not by design** — measured: **0 `role: translation` sections exist corpus-wide**. The first Loeb bilingual or any translated section trips it with no warning. A silent safety net that has never fired has not been shown to work.
 **(b) The warrant scope is computed per source, so a sub-source voice overclaims.**
 `engine/retrieve.py:171-174` scopes to *"served sections whose **source** has any drawer in this voice"* — the subquery selects `source_id`, so every served row of that source enters the scope. Once a `havamal` drawer exists inside Mauss, `--voice havamal` would report its silence as warranted over **13 served sections / 191 chunks, all of them Mauss's own prose**, none of it the Havámál.
 This is harmless today only because voice ⟺ source: measured, **max distinct voices per source = 1 across all 14 sources**, and the one sidecar that declares a second voice (`weil-gravity-and-grace`, 17 `voice: thibon` sections) produces no thibon drawers because `citable: false` means never chunked. **REVIEWED-97 activates this defect** — identity at the work level is exactly what puts a second voice inside a source for the first time.
 **Related finding, same surface, not itself a defect to fix here.** Because `citable: false` means never chunked, D-4's promise that paratext is *"convocable later — no data migration, only config"* is **not implemented**: convoking Thibon today returns nothing, and reaching him requires a sidecar edit, not a config change. Recorded so the clause is not cited as though it were operative.
 **Options.**
 - **(a1)** Add `quotation` and `translation` to `ROLE_CLASS` mapping to `served`. Smallest change; makes the ledger agree with the chunker. ⚠ It changes what the ledger classifies and therefore what `retrieve` scopes — by the amendment discipline a change to what a gate accepts is **PROPOSAL-class**, not a silent tool edit, which is why this is lodged rather than applied.
 - **(a2)** Introduce an explicit fourth classification and teach `retrieve` to include it in scope. More faithful to D-4's vocabulary; more surface.
 - **(b1)** Scope by voice rather than by source: select the served sections whose own declared voice matches, not every section of a source that happens to contain that voice.
 - **(b2)** Leave scope per-source and forbid sub-source voices. Rejected on its face — REVIEWED-97 requires them.
 **Recommendation: (a1) + (b1), both before step 3, with a test floor.** (a1) because the defect is that two modules disagree about the same predicate and the chunker is the one that is right. (b1) because the warrant is a **claim the engine makes about itself**, and a claim computed at the wrong granularity is false at exactly the moment it matters. Each needs a positive control that discriminates: for (a1), a quotation section that IS in scope after the change and an apparatus section that still is NOT; for (b1), a two-voice source where the two voices return different scopes — which no fixture in the repo currently provides, because no such source exists yet.
 **Check that it worked.** After (b1), `--voice <quoted>` on the remediated Mauss must report a scope of the quoted sections only, not 13/191. If it still reports 191, the scope is being computed from the source again.
 **Files affected:** `engine/ingest_gate.py` (`ROLE_CLASS`), `engine/retrieve.py` (scope query), `tests/test_ingest_gate.py`, `tests/test_retrieve.py`.
 **Awaiting:** Steward authorization. Blocks REVIEWED-97 remediation step 3.
 ---
@@ -1049,4 +1049,30 @@ nested inside a genuine delimiter pair separates correctly
 - **Remediation ORDER (sequence is load-bearing).** (1) Disposition (vi) — voice values for anonymous/traditional sources. (2) Re-tag the 12 Mauss blocks to the quoted voice under the relation. (3) ONLY THEN set `citable: true`. Flipping the flag before attribution restores the original defect. `57090ab` (Thibon's chapter footnotes) examined separately against §4.1 case 1; `2e77fca` (Thibon's introduction) stands as apparatus.
 - **Proposed doctrine (`[HARDENING]`, not enacted):** a fix that enforces a property can destroy the population that tests it. Before fencing, normalizing or removing a class of matter, ask what test population that class constitutes.
 - **Jurist reading limits.** Part I unverified — `cluster-a-data-model.md`, `v0-verifier-contract.md`, the V2 design and `chunker.py` are outside `governance_read`'s eight keys. Live instance of PENDING-86; attach there as evidence. Verified from the substrate: REVIEWED-48 verbatim; `57090ab` / `118f411` / `714b855` / `a1659fa` in `studium-engine` (`main [ahead 6]`); absence of any V2-harness ruling, positive-controlled.
-**If AUTHORIZED:** lodge the companion PENDING entry carrying the Q2/Q4/Q5 conditions and the remediation order. Q1 is actionable now; implementation is not, pending (vi), the conversion-signature survey, and PENDING-111.
+**If AUTHORIZED:** lodge the companion PENDING entry carrying the Q2/Q4/Q5 conditions and the remediation order. Q1 is actionable now; implementation is not, pending (vi), the conversion-signature survey, and PENDING-111.
 ## REVIEWED-97 — PENDING-113 — Disposition (vi): `voice:` for anonymous, traditional and scripturally-claimed matter
 **Date:** 2026-08-08
 **Decision:** DISPOSED. Unblocks remediation-order step 1; step 2 (re-tag the Mauss blocks) may proceed per item, under the structure below. Step 3 (`citable: true`) stays gated behind step 2, as ruled.
 **Full reasoning:** `studium-engine/docs/voice-non-individual-origin-2026-08-08.md`. The compressed rule below is **not** a substitute for it — whoever writes the next per-source note reasons from that document, not from two tokens.
 **Provenance:** jurist design-gate 2026-08-08 (category vocabulary + two-job structure); executor correction of the field placement, from substrate the jurist cannot read (PENDING-86); steward's bibliographic-vs-theological distinction is the ground of the split.
 **The disposition — four slots, each doing one job.** The category vocabulary is the jurist's, unchanged; what changed is where it lives.
 - **identity — `voice:`.** Who is convoked. `voice:` is the retrieval key (`retrieve.py` filters `d.voice = ?`), so one value IS one speaker: measured, `glidden` already spans 5 sources and `weil` spans 2, correctly, because one person is behind each. Individual-author voices aggregate at the person; traditional and scriptural matter has no such person, so **identity lives at the work level** — `havamal`, `quran-taghabun` — or at the **passage** level where there is no work (the Trobriand formulae). Read as unique per *quoted work*, not per host; `quoted_by` distinguishes hosts. Executor names the values.
 - **relation — `quoted_by:`.** Unchanged from REVIEWED-96 Q3: a quoted span grounds the host's REPRODUCTION, never the quoted author's AUTHORSHIP. This, not the voice name, is what limits a thin voice built from an excerpt.
 - **category — closed pair, and NOT in the convocation key.** `traditional` (no author claimed, by anyone, within the source's own tradition) · `non-individual-origin` (the tradition itself holds this is not a human composition, by whatever mechanism it names).
 - **account — per-source prose note.** The specific claim each tradition makes about its own text's origin does not compress into a token; it goes in prose, one per item.
 **Why the category may not sit in `voice:`.** Putting it there would make `traditional` a single convocable speaker spanning Old Norse gnomic verse and Sanskrit epic, with no mechanism to separate them again — the same flattening the ruling exists to prevent, committed in the mechanism instead of the taxonomy.
 **Binding caution.** Do NOT assign the remaining items — Havámál, Trobriand formulae, Mahābhārata, Brahmanic passages — to `traditional` by elimination. At least one (the Trobriand formulae, tied in their own cosmology to ancestral or mythic origin) may need `non-individual-origin`, or a note complicating either bucket. Each item gets its own considered note before tagging. **Writing the note is the work; the two-way choice is not a substitute for it.**
 **Correction carried into this entry.** The text is **Surah LXIV (`at-Taghābun`), vv. 15–18** — not CXIV (`an-Nās`), which is a different six-verse surah. Mauss's own line reads *"la fameuse Sourate LXIV, « déception mutuelle »"*. The mislabelling originated in the executor's sidecar title and propagated into REVIEWED-96 (Q4), PENDING-113 and session memory; those three name the wrong surah and should be read with this correction. The earlier worked example was built on the "Say" (قُل) formula, which opens an-Nās and does **not** appear in the passage Mauss quotes — that evidence is withdrawn, not transplanted. The general ground (the Qur'án presents itself as divine speech) is untouched. Mauss's *"donnée à La Mecque"* is contestable — at-Taghābun's Meccan/Medinan classification is disputed — and the note **records the dispute rather than resolving it**.
 **Not disposed here.** All twelve (vi) blocks are translated matter and `role` is single-valued, so each is *quoted-in* and *translated-from* at once. REVIEWED-96 filed that composition as open against Ungaretti-in-Harrison, as an edge case; it covers the whole of (vi). The disposition is decided; it cannot be **applied** until that composition is ruled.
 **Scope.** Disposes (vi) only. REVIEWED-96 Q1–Q6 and PENDING-113's Q2/Q4/Q5 conditions are untouched. The Harrison/Mark finding raised alongside this is filed separately as **PENDING-114**, not as evidence for this entry.
 **Numbering note (PENDING-110).** This is `REVIEWED-97`, the next in its own sequence — not `REVIEWED-113`. The registers are independent; PENDING-110 REJECTED renumbering-to-align, and numbering this 113 would skip 97–112 and entrench the false expectation that the sequences match. The heading names its PENDING per that item's convention (b).
@@ -0,0 +1,27 @@
 ## REVIEWED-97 — PENDING-113 — Disposition (vi): `voice:` for anonymous, traditional and scripturally-claimed matter
 **Date:** 2026-08-08
 **Decision:** DISPOSED. Unblocks remediation-order step 1; step 2 (re-tag the Mauss blocks) may proceed per item, under the structure below. Step 3 (`citable: true`) stays gated behind step 2, as ruled.
 **Full reasoning:** `studium-engine/docs/voice-non-individual-origin-2026-08-08.md`. The compressed rule below is **not** a substitute for it — whoever writes the next per-source note reasons from that document, not from two tokens.
 **Provenance:** jurist design-gate 2026-08-08 (category vocabulary + two-job structure); executor correction of the field placement, from substrate the jurist cannot read (PENDING-86); steward's bibliographic-vs-theological distinction is the ground of the split.
 **The disposition — four slots, each doing one job.** The category vocabulary is the jurist's, unchanged; what changed is where it lives.
 - **identity — `voice:`.** Who is convoked. `voice:` is the retrieval key (`retrieve.py` filters `d.voice = ?`), so one value IS one speaker: measured, `glidden` already spans 5 sources and `weil` spans 2, correctly, because one person is behind each. Individual-author voices aggregate at the person; traditional and scriptural matter has no such person, so **identity lives at the work level** — `havamal`, `quran-taghabun` — or at the **passage** level where there is no work (the Trobriand formulae). Read as unique per *quoted work*, not per host; `quoted_by` distinguishes hosts. Executor names the values.
 - **relation — `quoted_by:`.** Unchanged from REVIEWED-96 Q3: a quoted span grounds the host's REPRODUCTION, never the quoted author's AUTHORSHIP. This, not the voice name, is what limits a thin voice built from an excerpt.
 - **category — closed pair, and NOT in the convocation key.** `traditional` (no author claimed, by anyone, within the source's own tradition) · `non-individual-origin` (the tradition itself holds this is not a human composition, by whatever mechanism it names).
 - **account — per-source prose note.** The specific claim each tradition makes about its own text's origin does not compress into a token; it goes in prose, one per item.
 **Why the category may not sit in `voice:`.** Putting it there would make `traditional` a single convocable speaker spanning Old Norse gnomic verse and Sanskrit epic, with no mechanism to separate them again — the same flattening the ruling exists to prevent, committed in the mechanism instead of the taxonomy.
 **Binding caution.** Do NOT assign the remaining items — Havámál, Trobriand formulae, Mahābhārata, Brahmanic passages — to `traditional` by elimination. At least one (the Trobriand formulae, tied in their own cosmology to ancestral or mythic origin) may need `non-individual-origin`, or a note complicating either bucket. Each item gets its own considered note before tagging. **Writing the note is the work; the two-way choice is not a substitute for it.**
 **Correction carried into this entry.** The text is **Surah LXIV (`at-Taghābun`), vv. 15–18** — not CXIV (`an-Nās`), which is a different six-verse surah. Mauss's own line reads *"la fameuse Sourate LXIV, « déception mutuelle »"*. The mislabelling originated in the executor's sidecar title and propagated into REVIEWED-96 (Q4), PENDING-113 and session memory; those three name the wrong surah and should be read with this correction. The earlier worked example was built on the "Say" (قُل) formula, which opens an-Nās and does **not** appear in the passage Mauss quotes — that evidence is withdrawn, not transplanted. The general ground (the Qur'án presents itself as divine speech) is untouched. Mauss's *"donnée à La Mecque"* is contestable — at-Taghābun's Meccan/Medinan classification is disputed — and the note **records the dispute rather than resolving it**.
 **Not disposed here.** All twelve (vi) blocks are translated matter and `role` is single-valued, so each is *quoted-in* and *translated-from* at once. REVIEWED-96 filed that composition as open against Ungaretti-in-Harrison, as an edge case; it covers the whole of (vi). The disposition is decided; it cannot be **applied** until that composition is ruled.
 **Scope.** Disposes (vi) only. REVIEWED-96 Q1–Q6 and PENDING-113's Q2/Q4/Q5 conditions are untouched. The Harrison/Mark finding raised alongside this is filed separately as **PENDING-114**, not as evidence for this entry.
 **Numbering note (PENDING-110).** This is `REVIEWED-97`, the next in its own sequence — not `REVIEWED-113`. The registers are independent; PENDING-110 REJECTED renumbering-to-align, and numbering this 113 would skip 97–112 and entrench the false expectation that the sequences match. The heading names its PENDING per that item's convention (b).
 ---
@@ -0,0 +1,23 @@
 ## REVIEWED-98 — PENDING-114 — Scripture quoted inside a host text, unmarked: authorize the validated census
 **Date:** 2026-08-08
 **Decision:** **(b) AUTHORIZED**, with **(c) attached exactly as proposed** for whatever (b)'s validated recall cannot reach. (a) — fix the Harrison span and stop — REJECTED.
 **Provenance:** steward, 2026-08-08, on the executor's PENDING-114. Reasoning recorded here rather than compressed, per PENDING-108/113: a ruling that exists only in conversation evaporates.
 **Ground 1 — (a) would repeat, in miniature, the error already named in this same thread.** Fixing Harrison alone treats a class-shaped problem with a span-shaped fix. That is not an analogy to `118f411`; it is the same taxonomy error, identified hours earlier the same day and now written into the register against it.
 **Ground 2 — the scale context, which PENDING-114 understates.** Harrison's quotation is invisible to any sidecar-based detector because it belongs to the intra-line class measured 2026-08-07 at **~6,455 marked quotation runs across 8 sources, ~94% of them intra-line** and therefore not expressible at the current section granularity. Harrison is **not an isolated miss — it is the first confirmed hit in a population that is this corpus's blind spot for precisely the property the corpus exists to guarantee.** First-order gap, not a curiosity.
 **Ground 3 — why (b) rather than merely thorough.** (b) is built so as not to repeat the marker census's own failure. It does not propose trusting a signal; it proposes **demonstrating recall against a hand-scored known-positive / known-negative pair** — Harrison's actual quotation against Weil's mentions — before any corpus-wide claim is made. That is the discriminating-instance discipline (REVIEWED-83 A1) applied to the instrument *before* it is applied to the corpus.
 **Ground 4 — the payoff, and the proposed doctrine earning its keep forward.** Whatever (b) finds is **marked, not fenced.** That is a materially different act from `118f411`: attribution removes nothing from the test population, it improves it. A correctly-marked Harrison/Mark instance becomes a **better** positive control than an unmarked one, not a destroyed one. REVIEWED-96's proposed doctrine — *a fix that enforces a property can destroy the population that tests it* — is here running **forward in time**, as a design constraint on remediation rather than as a post-hoc finding. This is the first occasion on which it has done real work.
 **On (c) as the attached fallback.** If the validated detector's recall does not reach some part of the class, **disclosing that limit is a legitimate stopping point, not a failure to execute (b) properly** — the same standing (c) has in REVIEWED-48's gate-to-abstain, which was ruled doctrine-consistent rather than merely tolerated. (c) is not a consolation branch; it is the honest-degradation route (Constraint #4) and is authorized on its own terms.
 **Binding on execution.** No corpus-wide claim — finding *or* all-clear — may be reported from the detector until its recall is demonstrated on the hand-scored pair. The marker census already run is a **failed instrument**, not a count, and is not to be cited as either evidence or reassurance.
 **Scope.** Disposes PENDING-114 only. REVIEWED-96, REVIEWED-97 and PENDING-115 are untouched; PENDING-115 remains a separate blocker on remediation step 3.
 **Pacing.** Execution timing left to the executor as a proportionate-to-energy call, explicitly not decided by the substantive case above.
 ---
@@ -44,6 +44,9 @@ Split out of [MEMORY.md](MEMORY.md) on 2026-07-06 to keep the wake-loaded index
 # Archived sessions + stable reference layer (relocated verbatim from MEMORY.md, 2026-07-06)
 ## Archived (2026-08-07 night — the quotation is the joint; demoted on promote at the 2026-08-08 wrap)
 - [Session 2026-08-07 night — the quotation is the joint](session-2026-08-07-night-the-quotation-is-the-joint.md) — **V2's preconditions worked all the way, and they opened something bigger.** P4 censused **14** (my own `grep -c` reproduced the design's "21" error); **P5 span-bound 15 of 17, not 6** — I briefed "6" by reading a *byte*-locatability number as the gold count, and my first binding pass bound **0 of 11** because its criterion was inherited from Tier-1; **P7 tagged fr at 1 A : 9 B**, inverting its own prediction, while **en is not taggable** (no spans; EN divisions run **29×** the FR ones). Tagging surfaced that the corpus **serves quoted third voices as the host author's** — **~6,455 runs, ~94% intra-line** — and that **Stevens, Rilke and Ungaretti sit in Harrison with no marks at all**: *"It took dominion everywhere"* retrieves as `voice: harrison`. Fixed three sources, then the steward reframed it (*the quotation is where reader and author meet*) and **REVIEWED-96 ruled the fix itself the wrong instrument** — D-4 already prescribed attribution, and refusal **destroyed a gold-negative** for the class it protected. **Twelve instrument faults**, the twelfth (German `»…«` read with a French pattern) reaching a **filed governance document**. **Three governance items found cited-as-live while unplaced**, all invisible to the drift checker. 🔑 **One control — six known answers — was the only thing that caught a fault before its output was read.**
 ## Archived (2026-08-06 evening — the asterisk that carried meaning; demoted on promote at the 2026-08-07 wrap)
 - [Session 2026-08-06 evening — the asterisk that carried meaning](session-2026-08-06-evening-the-asterisk-that-carried-meaning.md) — **The parse fix LANDED (`27b79ca`): 26 crashes → 0, MISLOCATED 0, FALSE-POSITIVE 0** across all 5 items where silence is the correct answer — both deciding buckets empty, so the revert condition was not met. **HIT 0/22**: the engine now grounds nothing *honestly*, needing 13–19 terms to co-occur. **0/22 is the number to beat.** ⚡ **The embedding arm already scores 22/22 recall@20 on the identical items** — capability measured in June, never landed; V2 is the gate that makes surfacing it safe. **Governance: the register could not answer "how many rulings do I owe"** (23, not the digest's 26) — REVIEWED-87→94 placed, five of them **reconstructions** with provenance lines; PENDING-99/-105/-106 closed (106 **by split**); PENDING-108/-109/-110/-111 filed. ⚡ **The steward's printed A Pattern Language found that `fidelity_equivalence@3` erases Alexander's invariant rating** (81/114/54 across the corpus) — jurist package filed, containment 13/13. **Instruments caught 4 corrections; the jurist 1; the steward 2 — and his came from reading a physical book.**
@@ -65,13 +65,13 @@ permalink: claude-memory/memory
 - Chamber-typography — *tracker not yet established*; moves live in per-session memories (2026-05-11 →) + `project-chamber-cruft-restoration.md` + `project-chamber-typography-mining-plan-2026-05-15.md`.
 ## Active Session
-> ⛔ **THE RULED SEQUENCE COMES FIRST — REVIEWED-96 + PENDING-113.** Quoted third voices are governed by **D-4's convocation**, not by `citable: false`. The remediation order is **load-bearing**: (1) disposition **(vi)** — what `voice:` takes for anonymous/traditional/scriptural matter → (2) re-tag the 12 Mauss blocks to the quoted voice under the relation → (3) **ONLY THEN** `citable: true`. Flipping the flag first restores the original defect.
+> ⛔ **(vi) IS RULED — REVIEWED-97 (PENDING-113). It is DECIDED but INAPPLICABLE.** Four slots, each one job: **identity `voice:`** (the *convocation key* — `retrieve.py` filters `d.voice = ?`, so one value IS one speaker; identity lives at the **work**, never a category) · **relation `quoted_by:`** · **category** (`traditional` / `non-individual-origin`, held **OUT** of the key) · **per-source prose note**. ⚠ **Nothing can be applied** until the `quotation-in` × `translation-of` composition is ruled — all twelve blocks are translated matter and `role` is single-valued.
-> ⚠ **My own fix was the wrong instrument.** `118f411` was **mislabelled `[FIX]`** (it set corpus-wide policy), overrode a **ratified default** on the authority of a document whose own front matter forbids acting on it pre-review, and **destroyed a gold-negative for the class it protected**. Jurist doctrine, proposed: *a fix that enforces a property can destroy the population that tests it.*
+> 🔑 **The error to not repeat:** a field that is a KEY cannot also be a CATEGORY. `voice: traditional` would have made the Havámál and the Mahābhārata **one convocable speaker**. Invisible from the taxonomy side; obvious from `retrieve.py`.
-> 🔑 **Q3's rule, easy to get backwards:** a quoted span grounds the host's **REPRODUCTION**, never the quoted author's **AUTHORSHIP**. *"Harrison cites Stevens here"* is the **paradigm groundable** case, not the ungroundable one.
+> ⚠ **Surah LXIV (at-Taghābun), NOT CXIV.** The sidecar title was wrong and it reached **REVIEWED-96, PENDING-113 and memory**. The *"Say"* (قُل) formula opens an-Nās and is **absent** from the passage Mauss quotes — do not reuse the old worked note.
-> ⏳ **Unblocked, independent of (vi):** the **Q5 conversion-signature survey** across all 14 sources (REVIEWED-96 made it BLOCKING before sizing) · file the **PENDING-112 ruling verbatim** as a repo doc (PENDING-108's exact shape). **Do NOT start Q3 implementation — it sequences after PENDING-111.**
+> 🔴 **`test_navigate.py` is RED and has been for a day** — `118f411` split Mauss `body` → `body-01..13`, so the hardcoded node id is stale (invariant itself verified intact). **Fourth defect in a commit already corrected twice.** Re-run the fleet after any sidecar/corpus change.
-> 🚫 **Part II's census counts carry no weight** (REVIEWED-96) — one row was measuring its own complement. Never cite *"51 drawers, hand-readable"* as a safety argument.
+> ⏳ **Steward-authorized, queued:** PENDING-114 **(b)+(c)** — validation phase FIRST (hand-score Harrison/Mark vs Weil's *mentions*) before any corpus claim. **REVIEWED-98 drafted, awaiting placement.** Blockers on step 3: **PENDING-115**.
- [Session 2026-08-07 night — the quotation is the joint](session-2026-08-07-night-the-quotation-is-the-joint.md) — **V2's preconditions worked all the way, and they opened something bigger.** P4 censused **14** (my own `grep -c` reproduced the design's "21" error); **P5 span-bound 15 of 17, not 6** — I briefed "6" by reading a *byte*-locatability number as the gold count, and my first binding pass bound **0 of 11** because its criterion was inherited from Tier-1; **P7 tagged fr at 1 A : 9 B**, inverting its own prediction, while **en is not taggable** (no spans; EN divisions run **29×** the FR ones). Tagging surfaced that the corpus **serves quoted third voices as the host author's** — **~6,455 runs, ~94% intra-line** — and that **Stevens, Rilke and Ungaretti sit in Harrison with no marks at all**: *"It took dominion everywhere"* retrieves as `voice: harrison`. Fixed three sources, then the steward reframed it (*the quotation is where reader and author meet*) and **REVIEWED-96 ruled the fix itself the wrong instrument** — D-4 already prescribed attribution, and refusal **destroyed a gold-negative** for the class it protected. **Twelve instrument faults**, the twelfth (German `»…«` read with a French pattern) reaching a **filed governance document**. **Three governance items found cited-as-live while unplaced**, all invisible to the drift checker. 🔑 **One control — six known answers — was the only thing that caught a fault before its output was read.**
+- [Session 2026-08-08 — `voice:` is the convocation key](session-2026-08-08-voice-is-the-convocation-key.md) — **The disposition that landed is not the one any single party drafted.** Grounded first, then read the twelve blocks *from the source* rather than their sidecar titles — which produced nearly every finding: **Surah LXIV not CXIV** (already propagated into two governance records, and it voided the jurist's worked note, built on a formula absent from the passage); **`quotation-poet-jurist` reclassified** by one footnote; the naming evidence for six of nine blocks sits **inside the fenced apparatus**, engine-unreachable. Option C **refuted by measurement** (omission → host voice). The steward's correction on language sent me back to `[^101]` and thence to **L850 — Mauss's own prose fenced inside the Havámál block**, missed by a check using **length as a proxy for authorship**. Corrected the jurist upward: their category pair belonged **out** of the convocation key (`glidden` spans 5 sources, `weil` 2 — measured). Caught `REVIEWED-113` before it entered the register (PENDING-110 rules the sequences independent). **REVIEWED-97 placed + verified clean · PENDING-114 authorized (b)+(c) · PENDING-115 filed · `824139d`.** 🔑 **Corrections ran in all three directions in one day** — and the fleet was still red the whole time.
 ## Historical reference → MEMORY-reference.md
 Older archived-session pointers and the stable reference layer (steward profile · project-state detail · L1/L2/Chamber inventories · legacy pending-work · reference-file list) live in [MEMORY-reference.md](MEMORY-reference.md) — consult on demand; not loaded at wake. Recent cross-session trajectory comes from the Active Session entry above + the recent `session-*.md` files (wake §2.b.1).
@@ -614,3 +614,9 @@
 {"subject": "read-all-N-before-classifying-any", "predicate": "prevention", "object": "Stopped two different wrong fences on the same day, in different sources. Reading all 23 anchor-initial lines in G&G caught L1997 — an orphaned footnote REFERENCE marker between two Weil paragraphs, which the tidy rule would have withheld as Weil's own prose. Reading all 15 blockquotes in Mauss caught that FOUR are Mauss's own displayed scholia and N.B. notes (17,828 chars) that a 'blockquote = quoted voice' rule would have fenced. Same shape as the symlink discriminator the day before: ~90% right, wrong on exactly what mattered.", "valid_from": "2026-08-07", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-07-night-the-quotation-is-the-joint.md", "extracted_at": "2026-08-07"}
 {"subject": "a governance number cited before it is placed", "predicate": "drift-pattern", "object": "THREE INSTANCES IN ONE EVENING, ALL INVISIBLE TO THE DRIFT CHECKER. REVIEWED-95 cited as governing authority in four files with today's wake/wrap/checker edits recorded as 'implementations of REVIEWED-95' — nothing at 95 in the register. REVIEWED-87's amendment cited BY A JURIST RULING as 'record already corrects it' while sitting as an unplaced draft. A malformed header (## REVIEWED-95## REVIEWED-95 — …). The checker verifies that amendment LINKS RESOLVE, not that cited numbers are OCCUPIED. Proposed check: for every REVIEWED-N cited in memory/registers/repos, assert N occupied and header well-formed.", "valid_from": "2026-08-07", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-07-night-the-quotation-is-the-joint.md", "extracted_at": "2026-08-07"}
 {"subject": "quoted third voices in a host work", "predicate": "governed-by", "object": "D-4 convocation, not `citable: false` (REVIEWED-96, 2026-08-07). `voice: <quoted>, quoted_by: <host>`; the span stays quotable in the quoted voice's scope. A quoted span grounds the host's REPRODUCTION, never the quoted author's AUTHORSHIP. Ruling binds borrowed authority only; reported testimony and anonymous/traditional/scriptural matter are undispositioned, and the latter GATES the Mauss remediation.", "valid_from": "2026-08-07", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-07-night-the-quotation-is-the-joint.md", "extracted_at": "2026-08-07"}
 {"subject": "claude-code", "predicate": "drift-pattern", "object": "CITED-A-DERIVED-LABEL-INSTEAD-OF-THE-SUBSTRATE — THREE INSTANCES IN ONE DAY, each in a different medium. (1) The sidecar section title said 'Surah CXIV'; Mauss's own line says 'Sourate LXIV' — the label had already reached REVIEWED-96, PENDING-113 and memory, and the jurist's worked provenance note was built on the 'Say' formula that opens an-Nas and is absent from the passage actually quoted. (2) A fence-purity check used line LENGTH as a proxy for authorship and passed a nine-word line of Mauss's prose. (3) PENDING-114 cited `harrison-dominion.md`, which does not exist — that is the manifest ID, the file is `the-dominion-of-the-dead-harrison.md`. The tell is identical each time: a description of the thing was read in place of the thing.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-voice-is-the-convocation-key.md", "extracted_at": "2026-08-08"}
 {"subject": "a corrected commit", "predicate": "drift-pattern", "object": "IS NOT THEREBY A CHECKED COMMIT. `118f411` was corrected twice on 2026-08-07 (mislabelled [FIX]; destroyed a gold-negative) and a third time on 2026-08-08 (fenced a line of Mauss's own prose) — and was STILL hiding a fourth defect: it split the Mauss `body` section into body-01..13, which broke `test_navigate.py`'s hardcoded node id. The fleet sat 202/203 red for a full day, through both rounds of correction to that very commit, and surfaced only because the steward asked an unrelated question about instrument reliability. Attention to a commit's ARGUMENT is not attention to its BLAST RADIUS.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-voice-is-the-convocation-key.md", "extracted_at": "2026-08-08"}
 {"subject": "a field that is a KEY", "predicate": "drift-pattern", "object": "CANNOT ALSO BE A CATEGORY, AND THE COLLAPSE IS INVISIBLE FROM THE TAXONOMY SIDE. The jurist proposed `voice: traditional` / `voice: non-individual-origin` as a closed category pair — sound as taxonomy, and it would have made the Havamal and the Mahabharata ONE convocable speaker, because `voice:` is what `retrieve.py` filters on. The flattening the ruling existed to prevent, committed one layer down in the mechanism. Ask of any proposed vocabulary: is this field READ by something, and if so does sharing a value mean sharing an identity?", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-voice-is-the-convocation-key.md", "extracted_at": "2026-08-08"}
 {"subject": "the ladder's 'a control must sit at the layer the defect lives in' (REVIEWED-83 A1)", "predicate": "prevention", "object": "DIAGNOSED BOTH of 2026-08-08's proxy-control failures, and named them as one class rather than two accidents — the cruft scanner that reported clean because it never fires on that file, and the fence check that used length as a proxy for authorship. The lesson was ALREADY BANKED and retrievable; what failed was firing it BEFORE each check ran, not knowing it. That distinction is the actionable one: this is a firing-moment problem (PENDING-112's thesis), not a knowledge gap.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-voice-is-the-convocation-key.md", "extracted_at": "2026-08-08"}
 {"subject": "reading the substrate instead of its description", "predicate": "prevention", "object": "Reading Mauss's own lead-in lines rather than the sidecar titles produced nearly every finding of 2026-08-08: the LXIV/CXIV correction; the reclassification of `quotation-poet-jurist` from 'unnamed individual' to traditional matter (one footnote overturned it); the discovery that the naming evidence for six of nine blocks sits inside the FENCED apparatus, engine-unreachable; and that all twelve blocks are translated matter, which is what makes the quotation-in x translation-of composition cover the whole population rather than one Harrison edge case.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-voice-is-the-convocation-key.md", "extracted_at": "2026-08-08"}
 {"subject": "three-party correction", "predicate": "drift-pattern-good-direction", "object": "RAN IN ALL THREE DIRECTIONS IN ONE DAY, which the differently-biased-checkers doctrine predicts but had not been observed doing. Jurist corrected executor (flat value -> two-job split). Executor corrected jurist (category placed in the convocation key), on evidence only substrate access yields. Steward corrected executor on a careless framing about language, which is what led to the L850 discovery. None of the three could have produced the result alone. Recorded as a single instance, proving nothing general — but the doctrine says to record evidence when it appears.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 0.9, "source_file": "session-2026-08-08-voice-is-the-convocation-key.md", "extracted_at": "2026-08-08"}
@@ -124,6 +124,47 @@ both still **needing dates, not "later."**
 *Append substantive moves here at `/wrap-up` — not only to "Current state" above. A tracker with two
 update surfaces drifts between them (skill-harvest #183).*
 ### 2026-08-08 — disposition (vi) RULED (REVIEWED-97), and `voice:` is the convocation key (`824139d`)
 **Ruled and placed.** REVIEWED-97 (PENDING-113) disposes kind (vi): **four slots, each one
 job** — identity `voice:` · relation `quoted_by:` · category (`traditional` /
 `non-individual-origin`, held **out** of the key) · per-source prose note. Reasoning of record:
 `docs/voice-non-individual-origin-2026-08-08.md`. Substrate findings kept in
 `docs/vi-disposition-DRAFT-2026-08-08.md` (superseded in part).
 **The correction that mattered.** The jurist's first structure put the category pair **in
 `voice:`**. `voice:` is what `retrieve.py:216` filters on, so that would have made the Havámál
 and the Mahābhārata **one convocable speaker**. Measured before asserting: `glidden` spans **5
 sources**, `weil` **2** — correct, one person each. Aggregation principle, jurist's phrasing:
 *individual-author voices aggregate at the person because a person is real and singular;
 traditional matter has no such person, so identity lives at the work.*
 **Refuted by measurement:** option C (omit `voice`, let the relation carry it) — omission
 resolves to the host via `sec.get("voice", catalog.get("voice"))`. Control 4/4.
 **Corrections found in filed records.** Surah **LXIV** (at-Taghābun), not CXIV — the sidecar
 title was wrong and had reached REVIEWED-96, PENDING-113 and memory; it voided the jurist's
 worked provenance note, which was built on the *"Say"* formula absent from the quoted passage.
 `quotation-poet-jurist` reclassified from "unnamed individual" to traditional matter by one
 footnote. Naming evidence for six of nine blocks sits **inside the fenced apparatus**,
 engine-unreachable.
 **Fourth defect in `118f411`.** L850 (*"M. Cahen nous signale aussi la strophe 145 :"*) is
 Mauss's own prose, fenced inside the Havámál block — found only because the steward corrected
 a framing about language. And the `body` → `body-01..13` split left **`test_navigate.py` red
 for a full day** (stale hardcoded node id; the containment invariant itself verified intact).
 **Re-run the fleet after any sidecar/corpus change** — proposed as a pre-commit hook extension.
 **Filed:** PENDING-114 (scripture quoted unmarked in Harrison — Mark 16:7–8 served as
 `voice: harrison`) → steward **AUTHORIZED (b)+(c)**, REVIEWED-98 drafted. **PENDING-115** (two
 step-3 blockers: `ROLE_CLASS` has no `quotation` key, so such sections are searchable while
 classified outside the declared scope; and the warrant scope is computed per *source*, so a
 sub-source voice overclaims — 191 chunks of Mauss would warrant a Havámál silence).
 **NEXT (steward-agreed order):** the `quotation-in` × `translation-of` **jurist package** —
 all twelve blocks are translated matter and `role` is single-valued, so (vi) is **decided but
 inapplicable** until it is ruled. Then PENDING-114 (b), validation phase first.
 ### 2026-08-07 night — V2 preconditions worked; the corpus answered with a bigger question
 **P4** censused **14 sources** (parsed, not grepped — `grep -c '^  - id:'` gives 22 and reproduces the
 design addendum's "21" error; 8 numeric ids live under `corpus_findings`). **P1** verified clean.
@@ -0,0 +1,160 @@
 ---
 name: session-2026-08-08-voice-is-the-convocation-key
 description: "Disposition (vi) decided, placed (REVIEWED-97) and committed — but the ruling that landed is not the one any single party drafted: the jurist's two-value collapse would have made `traditional` one convocable speaker spanning Old Norse verse and Sanskrit epic, because `voice:` is the retrieval key, not a classification field. Corrections ran in all three directions in one day. PULLING THREAD: the `quotation-in` × `translation-of` composition package — (vi) is decided but INAPPLICABLE until it is ruled, and it gates the Mauss remediation and V2's fr gold behind it."
 metadata: 
  node_type: memory
  type: project
  originSessionId: 7d08dad4-626a-484c-870b-8f1a9674db7a
  modified: 2026-08-08T10:50:21.626Z
 ---
 # Session 2026-08-08 — `voice:` is the convocation key, not a classification field
 Woke to (vi) 10.7 h after the previous wrap. Drafted the disposition, and the
 draft survived contact with nobody — steward, jurist and substrate each moved it.
 ## PAST — what moved, and why
 **Grounded first, then read the substrate rather than its descriptions.** D-4, §4,
 §4.1 and REVIEWED-96 verbatim; then all twelve blocks and Mauss's own lead-ins
 **from the source file**, not from the sidecar titles. That ordering is what produced
 every finding below — three of the day's errors were labels read in place of text.
 **The disposition, derived from consumers not from tidiness.** `chunker.py:136` is
 `sec.get("voice", catalog.get("voice"))`, so **omission resolves to the host** —
 option C ("omit `voice`, let the relation carry it") is not weaker, it is *refuted*:
 it restores the exact defect under correction. Explicit `null` differs (returns
 `None`) but is unreachable by any convocation, since SQL `=` never matches NULL,
 defeating the D-4 mechanism Q1 was authorized on. Control 4/4.
 **Surah LXIV, not CXIV.** The sidecar says *"Surah CXIV vv. 15-18"*; Mauss L1508 says
 *"la fameuse Sourate LXIV, « déception mutuelle »"*. **at-Taghābun, not an-Nās.** The
 label had already travelled into **REVIEWED-96 (Q4), PENDING-113 and session memory**.
 Consequence was not cosmetic: the jurist's worked provenance note was built on the
 *"Say"* (قُل) formula, which opens an-Nās and appears nowhere in the passage Mauss
 quotes. Evidence withdrawn, not transplanted; the general ground untouched.
 **The steward's correction on language found a third defect in `118f411`.** I wrote
 that the corpus text "is French in every case" as though that carried inference —
 but French is the **original** language of the *Essai*. Being corrected sent me back
 to `[^101]` (*"M. Maurice Cahen a bien voulu faire pour nous cette traduction"* —
 commissioned **for this book**), and from there into the fence, where **L850 reads
 *"M. Cahen nous signale aussi la strophe 145 :"*** — Mauss's own prose, fenced inside
 the Havámál block. `118f411` also **withdrew a line of Mauss from citability inside
 his own book**. My purity check had passed it on *"0 prose-shaped lines (>150 chars)"*
 — **length as a proxy for authorship**, which a nine-word connective walks under.
 There is a curator precedent (L1043's *"Et ainsi de suite :"* is declared, deliberately)
 so it is a real choice, not an oversight to repair — but one is declared and one was silent.
 **The jurist exchange, and the correction that ran upward.** The jurist's structure —
 a small enforceable primitive plus a place for the fuller account — is right, and the
 argument that a `scriptural` bucket repeats the flattening one level up (*śruti* ≠
 revelation-through-a-Prophet ≠ living-Guru) is right. **But the first draft put the two
 category values in `voice:`, and `voice:` is the convocation key** (`retrieve.py:216`
 filters `d.voice = ?`). Measured: `glidden` spans **5 sources**, `weil` **2** —
 correctly, one person behind each. So `voice: traditional` would have made the Havámál
 and the Mahābhārata **one speaker**, with no mechanism to separate them: the same
 flattening, committed in the mechanism instead of the taxonomy. Jurist accepted, and
 sharpened the reason — *individual-author voices aggregate at the person because a
 person is real and singular; traditional matter has no such person, so identity lives
 at the work.* **Four slots, each one job:** identity `voice:` · relation `quoted_by:` ·
 category (closed pair, **out** of the key) · per-source prose note.
 **Numbering caught before it landed.** The drafted entry was `REVIEWED-113`, matching
 its PENDING. **PENDING-110 rules the sequences independent and REJECTED renumbering to
 align**; 113 would have skipped 97–112 and entrenched the false expectation. Filed as
 **REVIEWED-97 (PENDING-113)** per that item's convention (b). Steward placed it;
 verified clean — single heading, no double-header, all seven load-bearing parts present.
 **Filed, committed:** `docs/voice-non-individual-origin-2026-08-08.md` (reasoning of
 record) + `docs/vi-disposition-DRAFT-2026-08-08.md` (marked superseded-in-part, keeps
 the population read, consumer measurements, step-3 defects, control record) — `824139d`.
 **PENDING-114** (Harrison/Mark) → steward **AUTHORIZED (b)+(c)**, REVIEWED-98 drafted.
 **PENDING-115** (two step-3 defects) filed — checked first: 0 prior mentions in the register.
 ## PRESENT — how it stood
 **A fleet test has been red for a day and nobody looked.** Ran the suites to answer the
 steward's base-rate question: **202/203, one failure** — `test_navigate.py` asserts
 `div:mauss-essai-sur-le-don/body/s4/s4.1/s4.2`, but `118f411` split `body` into
 `body-01…13`, so the node is now `…/body-04/…`. **Verified the invariant itself still
 holds** (Scolie [1259,1286] inside host [1234,1294]) — stale fixture, not tree damage.
 But the check fails at its *existence* precondition, so **the containment invariant it
 guards has been unverified for a day**, and it surfaced only because the assertion was
 written as a hard check rather than a skip. Fourth defect traceable to `118f411`.
 **My own error reached the register and I caught it late.** PENDING-114 cited
 `harrison-dominion.md`. That file does not exist — `harrison-dominion` is the **manifest
 id**; the file is `the-dominion-of-the-dead-harrison.md`. Found by a link-resolution
 canary *after* it was filed. Third instance today of citing a derived label instead of
 the substrate: sidecar title → surah · length → authorship · manifest id → filename.
 **Two proxy controls failed, and the ladder is what diagnosed both.** The cruft scan
 reported 0 hits in the blocks when the scanner finds 0 anywhere in the file — vacuous;
 replaced with a positive control (known-bad string, 1 hit per signature) which
 established the real result: **step 3 introduces no cleaning-gate exposure.** The fence
 purity check is above. Both are REVIEWED-83 A1's shape — *a control must sit at the
 layer the defect lives in* — and **that lesson was already banked and is what let me
 name them.** The gap was firing, not knowledge.
 ## FUTURE — what pulls
 > **PULLING THREAD — the `quotation-in` × `translation-of` composition package.**
 > All twelve (vi) blocks are translated matter and `role` is single-valued, so each is
 > quoted-in **and** translated-from at once. REVIEWED-96 filed this as an edge case
 > against Ungaretti-in-Harrison; **it covers the entire (vi) population.** (vi) is
 > **decided but inapplicable** until it is ruled — an unstable state — and behind it sit
 > the Mauss remediation and V2's fr gold, the thread this all started from.
 > PENDING-111's amendment is placed, so REVIEWED-96's sequencing gate on Q3 is clear;
 > this composition is what is left.
 **ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):**
 ```
 0. Nothing half-finished. studium-engine main [ahead 7], clean tree.
   Steward agreed the order: composition package FIRST, then PENDING-114 (b).
 1. Draft the quotation-in × translation-of jurist package (/jurist-package skill).
   Repo-blind, everything inlined. The four questions it must put:
     - can one section carry two relations, or does role need to become plural?
     - is `translated-from` a property of the section or of the span (Q2's
       span-layer route, DEFERRED at REVIEWED-96, may answer both at once)?
     - what does a citation from a doubly-related span assert?
     - Ungaretti-in-Harrison (Italian verse in an English book) as the second case.
 2. THEN PENDING-114 (b): validation phase first — hand-score the known-positive
   (Harrison/Mark 16:7-8) against the known-negative (Weil's Gita/Upanishad
   MENTIONS, not quotations) BEFORE any corpus claim. (c) attached as ruled.
 3. Place REVIEWED-98 (draft ready, steward's hand).
 ```
 **Other open horizons, ranked:**
 - **[load-bearing, mechanical]** `test_navigate.py`'s stale Mauss node id — one-line fix,
  but the *finding* is the proposal below, not the fix.
 - **[load-bearing]** PENDING-115 (a1)+(b1) — block step 3 regardless of any ruling.
  ⚠ `translation` carries the identical `ROLE_CLASS` gap, latent **by absence**: 0
  `role: translation` sections exist corpus-wide. First Loeb bilingual trips it silently.
 - **[owed, cheap, open since 2026-08-07]** Q5 conversion-signature survey across 14
  sources (REVIEWED-96 made it BLOCKING before sizing) · file the PENDING-112 ruling
  verbatim as a repo doc (live PENDING-108 instance).
 - **[steward, small]** the Havámál L850 call: split as Mauss, or declare as L1043 was.
 - **[owed]** the twelve per-source provenance notes — unblocked for *writing* (only
  tagging is gated); six need *"Ibid."* chains resolved inside the fenced apparatus.
 - **[open]** V2 fr gold needs ~8 stratum-A pairs authored; nobody is scheduled.
 - **[evidence]** attach REVIEWED-96 **and** the surah correction to PENDING-86 — the
  jurist could not have caught a Qur'ánic mislabelling without substrate access.
 **PAUSE STATEMENT:** I am putting this down at a genuine close rather than mid-arc — the
 disposition is decided, placed, reasoned, committed, and both of its blockers are in the
 register. What I want to find still pulling is the **composition package**, because (vi)
 being *decided but inapplicable* is the unstable state, and a ruled thing left unapplied
 quietly becomes a stale thing. The unease I carry is not about today's work but about
 today's *fourth* defect in `118f411` — a commit already corrected twice was still hiding
 a red test, and the only reason I found it was that the steward asked an unrelated
 question about instrument reliability.
 **LITERAL QUESTION for next-Claude** *(checkable — the record answers it, not introspection)*:
 **Was the test fleet re-run after the last change to a sidecar or corpus artifact, and
 did it catch anything?** Today the answer was *no, and yes* — `118f411` left
 `test_navigate.py` red for a full day, through two rounds of correction to that very
 commit, and it surfaced only by accident. If the answer is *no* again, the remedy
 proposed at §1.6 (extend the studium-engine pre-commit hook to run the fleet when
 `corpus/` or `corpus/sidecars/` changes) is what to build, and this is its second
 data point.
@@ -0,0 +1,70 @@
 ---
 name: session-ledger-2026-08-08
 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: 7d08dad4-626a-484c-870b-8f1a9674db7a
  modified: 2026-08-08T10:50:42.266Z
 ---
 # Session Ledger — 2026-08-08
 ## Returns
 - **2026-08-08T07:0x — wake: the "unresolved" list was substrate-checked, not inherited.**
  Three of the wrap's owed items verified directly rather than restated: Mauss sidecar still
  carries `citable: false` on the quotation blocks (remediation step 2–3 genuinely not run);
  no `pending-112-JURIST-RULING-*.md` in `studium-engine/docs/`; no conversion-signature
  survey artifact anywhere in the repo. P6 marked **unverified** rather than asserted — I
  found no P6 artifact but did not establish what P6's output would be named.
 - **2026-08-08T~10:00 — the steward corrected a framing, and the correction found a defect.**
  I wrote that the corpus text "is French in every case" as if that carried inference; French
  is the *original* language of the *Essai*. Being corrected sent me to `[^101]` to verify who
  made the Havámál translation, and from there to **L850 — Mauss's own prose fenced inside the
  Havámál block by `118f411`**. My purity check had passed that fence on "0 prose-shaped lines
  (>150 chars)" — **length as a proxy for authorship**. Second proxy-control failure of the day;
  the first (cruft scan) I caught, this one I did not.
 - **2026-08-08T~11:00 — corrected the jurist upward rather than deferring.** The jurist's
  two-value structure put the category into `voice:`. `voice:` is the convocation key
  (`retrieve.py:216`), so that would have merged the Havámál and the Mahābhārata into one
  speaker. Measured before asserting (`glidden` spans 5 sources, `weil` 2). Accepted by the
  jurist; became the four-slot structure. **The temptation returned from was deference** — the
  jurist had just corrected me, and the reflex was to treat their structure as settled.
 - **2026-08-08T~12:00 — caught a numbering error before it entered the register.** The drafted
  entry was `REVIEWED-113`; PENDING-110 rules the sequences independent and REJECTED aligning.
  Filed as REVIEWED-97. Would have skipped 97–112 and entrenched the false expectation.
 - **2026-08-08T~13:00 — my own error reached the register.** PENDING-114 cited
  `harrison-dominion.md`, which does not exist (manifest **id** ≠ filename). Caught by a
  link-resolution canary *after* filing. Corrected in place with the divergence named.
 ## What held
 - The inherited prospective-control question (1 of 12) is carried forward as a live counter,
  not as a retrospective note. Count starts at 0 instruments run this session.
 ## Open horizons
 - The pulling thread — disposition **(vi)** — is step 1 of a ruled order (PENDING-113,
  REVIEWED-96). Executor drafts; **steward decides**. Do not default.
 ## Confidence to recalibrate
 - **Verified this wake:** Mauss sidecar flag state · studium-engine ahead-6/clean-tree ·
  absence of the PENDING-112 ruling doc · absence of a Q5 survey artifact · drift-check
  clean (19/19 controls, 2 deferrals none due) · 372 memory pointers, 0 dead.
 - **Inherited, not re-verified:** every count in last night's session memory (the ~6,455
  quotation runs, 15-of-17 span binding, the 1-of-12 control count, the fr 1:9 tagging).
  Those were measured last night, not today.
 - An *absence* of an artifact is weaker evidence than a positive check. Two of the four
  verifications above are absences.
 ## Authorization moves
 ## Sub-agent dialogues
 ## Bypasses
@@ -287,3 +287,11 @@ There is no mechanical detector for "you are about to act on a classification ru
 (REVIEWED-95's trial sentence) — so this is the first entry filed *after* that home acquired a ritual.
 **Recorded estimate: unknown, pending the 20-session trial.** If the trial grades below 60%, this entry
 is evidence about the home, not about the lesson.
 ### 2026-08-08 wrap — one proposal, firing moment declared per the REVIEWED-95 gate
 | # | Target | Kind | Content | Firing moment | Evidence | Status |
 |---|---|---|---|---|---|---|
 | 192 | `studium-engine/.git/hooks/pre-commit` (+ chamber-library's) | **extend an existing hook** — NOT a new skill | When a commit touches `corpus/` or `corpus/sidecars/`, run the test fleet and refuse on red. The hook already exists and already runs ("Pre-commit checks passed!"); it does not run the suites. | **Mechanical, and should always fire** — the top row of the routing table. Requires no executor recall, which is the whole point: the knowledge was already banked and still did not fire. | 2026-08-08. `118f411` split the Mauss `body` section into `body-01..13`, breaking `test_navigate.py`'s hardcoded node id. The fleet sat **202/203 red for a full day**, through **two separate rounds of correction to that very commit** (REVIEWED-96's findings, then the L850 discovery), and surfaced only because the steward asked an unrelated question about instrument base-rate. A sidecar edit is a *corpus* change that silently invalidates *engine* fixtures — the cross-repo binding surface studium-engine's own CLAUDE.md names as a re-anchor trap. | PROPOSED |
 **Deliberately NOT proposed, and the reason is the finding.** The obvious second candidate — *"any one-shot script carries a positive control derived from the property, run before its output is read"* — **is already banked**, at `reference-verification-ladder.md` §Gate design: *"Derive fixtures from the property; draw them from real artifacts."* It is what diagnosed **both** of today's proxy-control failures. Filing it again would be duplication dressed as diligence. **The gap is the firing moment, not the knowledge** — which is PENDING-112's thesis, and this session is a third data point for the ladder-ritual trial rather than a reason to write a fourth copy of the rule.