🔧 Auto-commit from sysupdate on 2026-06-03 21:09

PENDING.md

@@ -765,4 +765,28 @@ The Jurist's six-phase authorization map governs sequencing. Cross-cutting succe
 
 **Audit update (2026-05-28):** four-pass pre-build audit completed (`pre-build-audit-2026-05-28.md`). Findings (a)/(b)/(c)/(d) were re-tested against substrate; A1's persistence-finding (no schema for `means_of_knowing`; only numeric value of `EarnedConfidence` persisted) corrected; B1's "prior-only constraint" borrow ruled redundant (BMF enforces by construction); B1's `_cap_links_per_unit` borrow validated as 1–3 lines; the parent amendment's items 9 (numeric confidence in recall response) and 10 (epistemic state in health) found NOT shipped, reshaping A1's scope. Co-author branch deferred. Audit document is part of the Monday package.
 
-**Awaiting:** steward review of the audit; jurist review of A1/A2/B1; co-author engineering review of B1/C1/C2/D1 (Seb on resumption from Peter block 2026-06-01+; steward + executor continued joint work during).
+---
+
+## PENDING-25 — Translated renderings in the ARC corpus
+**Date:** 2026-06-03
+**Tag:** [PROPOSAL]
+**Summary:** A doctrine + frontmatter convention for translated/multilingual works — ARC holds *works*, of which languages are non-canonical *renderings*; the work (not any rendering) holds the corpus slot.
+**Rationale:** Lune will translate *After the Reply* into French — the first translation in the corpus, and a first instance of intergenerational stewardship in ARC. The corpus had no settled mechanism (only a tentative `related_texts` line in frontmatter-spec §8, and one accidental Context-C legacy piece). Jurist's Opinion (2026-06-03) ruled: Option B *reframed ontologically* — neither rendering is canonical, both express one work; Context C legitimate-but-gated; `translator:` a **required** field (intergenerational dimension carried structurally); amend frontmatter-spec (no new companion).
+**Options:** Work-level corpus-slot representation — W1 (`primary_rendering` flag; rejected, re-smuggles privilege), W2 (work-stub object; faithful but heavy), **W3 (group by `work:` at build; AUTHORIZED)**. Sub-questions resolved 2026-06-03: routing = asymmetric (root slug stays, additional renderings `/<lang>/<slug>`); rendering-date = each rendering's own publication date; Context-C-placement = frontmatter-spec §8 + §I.j pointer (settled). **Only toggle affordance remains open** (deferred to implementation, to be rendered not specified blind).
+**Recommendation:** Adopt the jurist's rulings; implement via W3. Full proposal: `docs/AldineXXI-Codex/drafts/translated-renderings-proposal-2026-06-03.md` (jurist brief at `multilingual-translation-handling-jurist-brief-2026-06-03.md`).
+**Files affected (on implementation):** `frontmatter-specification.md` (§2 new subsection, §4 recipe, §8 ruling); `site.hs` (listing dedupe by `work:` + representative-selection); piece template (rendering toggle); routing rule. None touched yet.
+**Status:** AUTHORIZED-with-conditions by steward+jurist 2026-06-03; the four conditions are addressed in the proposal document (date resolved, `work:` omission corrected, §7.3 settled, routing decided). Formal REVIEWED entry is the steward's to file. Implementation **split along its natural seam** (executor analysis 2026-06-03, steward-accepted): (a) the `work:` listing-dedupe awareness folds into **F-Phase 2** (the Hakyll listing generator — same `site.hs` listing surface; build it work-aware from the start so the generator is never reopened; dormant until a `work:` field exists, like §I.k); (b) the rest — frontmatter-spec amendments, toggle template, routing, heteronym decompose — is its own focused session **after Stage G** (stable typology), with the toggle *rendered for the steward*, not specified blind. **Decoupled from the Vignette** (independent — touches neither listing nor rendering). **Test vehicle = the Matthieu Taliesin heteronym refactor** (steward 2026-06-03): decompose the trilingual piece to en/fr/es renderings as the proving ground for the toggle+`work:` machinery (first application of the §5 Context-C gate, not a reversal of jurist's no-force-decompose ruling). Also incoming as renderings: steward's bio/CV + About pages (little-by-little). **Readiness target: late August 2026**, ahead of Lune's *Après la réponse* (expected late Aug/Sept). Independent of §I.k.
+
+**Awaiting:** steward review of the audit; jurist review of A1/A2/B1; co-author engineering review of B1/C1/C2/D1 (Seb on resumption from Peter block 2026-06-01+; steward + executor continued joint work during).
+## PENDING-26 — `.whisper` retirement: §XIV name-lock + dedicated migration pass
+**Date:** 2026-06-03
+**Tag:** [HARDENING]
+**Summary:** Retire the unsanctioned `.whisper` class (apparatus-spec 462–464; AldineXXI Selector Index 2801) via a dedicated, gated migration pass — after steward/jurist lock the target apparatus class names per §XIV.
+**Rationale:** Stage N's deep read corrected the scope: the closing plan recorded "27 template usages"; ground truth is **~156 line-usages — 11 templates (~14) plus 100+ content markdown files (~140)**. This is a corpus-wide migration, not a residual deletion. `.whisper` conflates two semantic roles that must not land in one class: **(a) apparatus prose** (footer text, list metadata) and **(b) list-context qualifier glyphs** (`✦`/`⟐` — the same marks that render via `.chamber-mark`/`.encounter-mark` on post pages). Stage M left a non-regressing holding value (`_utilities.scss:32`, `var(--gray)`); the §VII.e batch (commit `20019ba`) did not touch it. The jurist's Stage-N review requires this carry to be a named PENDING item with commit-gate, not a verbal deferral.
+**Name candidates (surfaced from the specs, for the lock):**
+- Role (a) apparatus prose → **`.apparatus-meta`** (AldineXXI Selector Index 2801 "migrate to `.apparatus-meta` or equivalent").
+- Role (b) list-context glyphs → **`.register-mark-inline`** (apparatus-spec 464) **or unification with the existing `.chamber-mark`/`.encounter-mark`** (arguably the same mark in a quieter context — `_post.scss` historical note: ⟐ rendered via `.chamber-mark` on pages, `.whisper` in lists; one mark, one class, context handles register).
+**Options:** (1) Jurist rules on the names in a focused review; executor then runs the migration as its own pass — scripted edit across templates + content, render-verified per type per viewport, sequenced **before** the full re-partition. (2) Steward locks names directly in REVIEWED-26 annotation; same execution path.
+**Recommendation:** Option 1 — the role-(b) choice (new class vs unification) is a genuine taxonomy question the jurist should rule on; unification is the leaner answer but touches the qualifier-mark grammar (§V).
+**Files affected:** ~11 templates, 100+ content files, `_utilities.scss` + `_layout.scss` (the holding rules), apparatus-spec + Selector Index cross-references.
+**Awaiting:** Steward authorization + jurist name-lock. Until then the holding value stands; no migration work proceeds.