dotfiles/claude/memory/session-2026-06-03-arc-ik-french-spacing-translation-doctrine-phase2-listing-generator.md

---
name: session-2026-06-03-arc-i-k-french-spacing-translation-renderings-doctrine-pending-25-stage-f-phase-2-listing-generator-shipped
description: A long ARC build day, three threads all completed & the last deployed
  live. Pulling thread is ARC Stage N (spec-conformance + dead-code prune), now loaded
  with concrete Phase-2 dead-glyph fallout; the bounded Compass-§VI-as-data follow-on
  is the satisfying adjacent re-entry. CapableMind explicitly deferred.
metadata:
  node_type: memory
  type: project
  originSessionId: 2b72c971-bfea-499e-b483-651782a182c3
permalink: claude-memory/session-2026-06-03-arc-ik-french-spacing-translation-doctrine-phase2-listing-generator
---

# Session 2026-06-03 — ARC: §I.k · translation doctrine · Phase-2 listing generator (shipped)

A long, productive ARC day. Three threads, all carried to completion; the last deployed live with the steward's eyes on it (desktop + physical phone). CapableMind deferred by the steward ("not sure I'll work on CapableMind today… after a break maybe continue with ARC").

## Past — what we did

### Opening: MemPalace fork hygiene (not workstream)
- Committed the `embedding.py` device-report log-fix `f25f767` on `local/bge-m3-on-3.3.6`, pushed to **fork** (davidglidden/mempalace), NOT origin (third-party upstream). Steward corrected my morning over-elevation of this — it's local-fork hygiene on a tool we didn't build, not a workstream item. Cold-start fix (from 06-02) **confirmed holding** — MemPalace alive all session.

### Thread 1 — §I.k Build-time Typographic Enforcement (F4), SHIPPED
- Wrote AldineXXI **§I.k** (spec, +48) + implemented `frenchSpacing` Pandoc AST transform in `site.hs` (gated on `lang: fr` in the Compiler monad via `getMetadataField`; a `walk` over `Inline`s). Exposed `pandoc-types` in the cabal for `Text.Pandoc.Walk`.
- **Rule:** uniform **U+202F** before `; : ! ? »` and after `«`; **upgrades an existing space, never inserts into glued punctuation** (URLs/times safe); idempotent.
- **Governance fork hit & resolved:** the Lexique distinguishes *espace fine* (`; ! ?`) from *espace mot* (`:`, guillemets), but the operative companion §1 locks uniform U+202F — a two-document-hierarchy conflict I surfaced rather than resolved. **Jurist ruled** uniform U+202F (web-transposition of the Lexique's hot-metal intent; Lacroux backing; companion stands). §I.k records it as steward-ratified.
- **Verified** on a synthetic Context-B corpus + English gate-test (8 cases incl. glued-colon-untouched, idempotency, U+00A0-upgrade); clean rebuild green; test files removed.
- Committed `02373fd`. Dormant until a `lang: fr` piece exists. Context-B-only scope (steward chose); Context A named as a deferred increment.

### Thread 2 — Translated-renderings doctrine (PENDING-25), AUTHORIZED
- Trigger: **Lune will translate *After the Reply* into French** (~late Aug/Sept). The heteronym (*Matthieu Taliesin*, trilingual-in-one-file) is a pre-convention legacy artifact, NOT a competing convention.
- Drafted a **jurist brief** → **jurist's Opinion** ruled: **Option B reframed ontologically** — ARC holds *works*; languages are non-canonical *renderings*; **the work (not any rendering) holds the corpus slot**; `translation_of` = source-rendering provenance, never primacy. `translator:` a **required** field (intergenerational carried structurally). Context C legitimate-but-gated. Amend frontmatter-spec; **no new companion**.
- Drafted **PENDING-25 [PROPOSAL]** (`docs/AldineXXI-Codex/drafts/translated-renderings-proposal-2026-06-03.md` + jurist brief alongside). Work-level corpus slot = **W3** (group by neutral `work:` at build; listing-representative = site-default-lang as a *presentation* choice, not canonicity). Steward **AUTHORIZED-with-4-conditions**, all addressed in the doc (rendering carries own publication date; `work:` omitted-for-single-rendering; Context-C placement settled = frontmatter-spec §8 + §I.j pointer; routing = asymmetric, root slug stays + additional renderings `/<lang>/<slug>`).
- **Sequencing decided:** impl split along its seam — the `work:`-dedupe listing logic **folds into F-Phase 2** (do-once), the rest (frontmatter/toggle/routing/heteronym) is its own session **after Stage G**; **decoupled from the vignette** (independent). **Heteronym refactor = the proving ground / test vehicle** for the toggle (steward's call; first application of the §5 Context-C gate). Formal REVIEWED entry is the steward's to file.
- Committed `e1dbf4c` + `885914f` (doctrine docs + sequencing). PENDING-25 entry in `~/dotfiles/PENDING.md` (uncommitted — steward's governance repo).

### Thread 3 — Stage-F Phase 2: listing generator + triptych retirement, SHIPPED LIVE
- **The generator:** 11 near-identical per-type `create` blocks → **one `forM_`** over new **`data/listings.yml`** (presentation facts: page/title/classes/show_post_type/include_sequences). Companion to `content-types.yml` (typology). Every listing class **validated against `class_enumeration` → unknown class = build error** (content-typology §5 cl.3; proven by probe). Dormant `dedupeByWork` hook for PENDING-25 (no-op, no `work:` exists).
- **THE STEWARD'S TWO QUESTIONS RE-SHAPED IT** (verify-before-assert caught stale assumptions): (1) *"does SVG change glyph associations?"* → found `currentSymbol` is **DEAD** (since the 2026-05-26 SVG migration the rendered sigil is the `<symbol>` per-slug in `reading-compass-points.html`); the generator therefore touches **no glyphs**, just validates classes — saved wiring a dead field from a now-secondary source. (2) *"add SVG / update spec?"* → **No** (SVG is artwork keyed by slug = presentation, not typology; stays out of jurist-pending §2).
- **"Do it once well"** judged as **two right-sized once's, not one mega-change**: listing generator now; Compass-§VI-as-data as a separate bounded follow-on. `listings.yml` built as the **forward seed** for it (avoids do-it-twice), documented as such.
- **Triptych/glyph dead-system retired:** `<script>bootTriptychs()</script>` (loaded dead JS on every page) + `post.html` markup (never rendered — `has_glyph` always false) + the shipped ~100-file `assets/js/glyphs/` tree. Only output change = dead JS gone from every page's `<head>`.
- **Byte-diff gate PASSED:** all 11 listing pages + annals byte-IDENTICAL to baseline (generator replicates compound/sequences/show-post-type exactly). Combined final gate: essays.html differs from original baseline by ONLY the intended dead-JS removal.
- Committed `4303df0` (generator) + `6851367` (triptych) + `41fc030` (horizon). Documented `listings.yml` in CLAUDE.md.
- **DEPLOYED** (`make rebuild` → CloudFlare + GitHub mirror) after steward viewed locally on desktop + **physical phone** (LAN via `--host 0.0.0.0` @ 192.168.1.52:8000) → "looks fantastic." **Live-verified** at animalrationiscapax.org: listings 200, 0 bootTriptychs/glyphs refs, compass SVG intact. §I.k shipped alongside (dormant). Honest catch: dead-JS file returned 200 live → diagnosed as **CloudFlare edge-cache remnant** (cf-cache-status REVALIDATED, max-age 14400; cache-busted → 404; absent from origin; referenced by zero pages → harmless, self-expires ~4h).

### Also produced
- **`arc-horizon-2026-06-03.md`** — one-place consolidated view of remaining ARC work (a reading-aid pointing to the canonical closing-plan + tracker; the steward had "lost sight of the horizon"). Remaining sequence: **#1 Phase-2 DONE** → Stage N → re-partition → Stage G → vignette; + translation-(b) after Stage G; + bounded Compass-data follow-on.

## Present — mood / returns
- **The steward's probing questions were the engine of quality this session.** Three times (BBF this morning per prior session; SVG-glyph; add-SVG-to-yml) a steward question caught a now-stale assumption before it shipped. The through-line: *the spec/code/world may have moved since the design was written — verify the current state, render-and-LOOK, don't reason from the remembered model.*
- **Governance instinct held:** surfaced the fine-vs-mots conflict to the jurist rather than resolving it unilaterally (two-document hierarchy); drafted the translation doctrine as a jurist brief → PROPOSAL rather than just building. The loop stayed load-bearing.
- **Proportion held:** judged "do it once well" as *not* over-reaching into the Compass-data mega-change; kept Phase 2 bounded + byte-verified. τὸ πρόσφορον.
- Time/energy: a long session, much accomplished, all threads closed (nothing mid-flight). Steward chose to defer CapableMind and take a break.

## Future

### Pulling thread (singular)
**ARC Stage N — the spec-conformance + dead-code-prune deep read** — now loaded with concrete, fresh fuel from Phase 2: the dead-glyph residue (rename the misnamed-but-LIVE `needsGlyph` post-selector; remove dead `has_glyph`/`glyph_id` field defs + the unused `renderGlyph.html` & `partials/triptych.html` templates; drop the vestigial `currentSymbol` in the annals/index blocks; write the SVG-vs-unicode spec-conformance note for §VI/typology). Stage N gates re-partition → Stage G → vignette, so it's the next macro-sequence step. The **bounded Compass-§VI-as-data follow-on** (generate the nav `<a>` rows from `listings.yml` + a tiny Annals/About specials list; artwork stays hand-authored; closes the (slug,title) overlap Phase 2 opened) is the satisfying adjacent re-entry if energy favors a small win over the big SCSS read.

### Actionable resumption point (as of wrap — re-judge against what changed)
ARC `main` @ `41fc030`, clean, pushed both remotes, **deployed + live-verified**. Nothing mid-flight. **First move toward the thread:** either (a) the Phase-2 dead-glyph fallout — start by renaming `needsGlyph` (it's a post.html-vs-default.html selector now, not glyph-related; `site.hs` ~616/633) and deleting the two dead templates + dead field defs (`site.hs` ~1195-1218), each a pure subtraction; or (b) the Compass-§VI-as-data follow-on (read `reading-compass-points.html` + build a `$for(compass)$` loop over `listings.yml` + specials, site-wide compass byte-diff as the gate). Both are children of today's Phase 2. Recommend (a) first (smaller, purely subtractive, no site-wide byte-diff) then (b).

### Other open horizons (ranked)
- *Load-bearing (ARC):* Stage N (above) → full re-partition → Stage G (jurist) → vignette (F+1). The macro-sequence to "ARC = just write and publish" (target before late Aug, ahead of Lune's translation).
- *Authorization-pending:* PENDING-25 — steward to file the formal REVIEWED entry; implementation (b) is post-Stage-G.
- *Governance hygiene:* `~/dotfiles/PENDING.md` carries PENDING-25 **uncommitted** (steward's repo; I don't commit dotfiles unilaterally — steward may want to commit it).
- *Deferred-with-reason (CapableMind, parked today):* the morning-wake housekeeping remainder — 8 untracked CM-AI thinking files (since 05-18), PENDING.md bloat, stale L1 tracker (2026-05-28), Seb's gate-question (did D1–D10 move the four Hindsight findings). Steward deferred CapableMind entirely today.
- *Parked:* L2 (past end-of-May park; not reopened).

### Pause statement
I'm about to be away from this. The day's three ARC threads are all complete and the last is live — nothing is mid-edit, so I won't return to a half-finished state. What I want to find still pulling is the ARC sequence toward Stage F's full close: Stage N's dead-glyph fallout (today's loose tail) and the Compass-data follow-on, both bounded children of Phase 2, leading on toward re-partition → Stage G → vignette. If the steward picked up CapableMind in the meantime, that's a re-pick, not a loss.

### Literal question for next-Claude
After the break: does the steward want the **smaller purely-subtractive Stage-N dead-glyph cleanup** (rename `needsGlyph`, delete dead templates + field defs + `currentSymbol`) first, or the **Compass-§VI-as-data follow-on** (which closes the (slug,title) overlap Phase 2 opened but needs a site-wide compass byte-diff)? And: has the steward filed the REVIEWED entry for PENDING-25?

## Decisions deferred (and why)
- **CapableMind, entirely** — steward deferred ("not sure I'll work on CapableMind today"). The housekeeping remainder stays open.
- **Compass-§VI-as-data** — deliberately NOT folded into Phase 2 (it's a differently-shaped concern: site-wide byte-diff, Annals/About specials, Compass-order/surfacing governance). Its own bounded pass.
- **Stage-N dead-glyph residue** — deferred from Phase 2 (the JS-load + post-markup live cost was removed; the remaining items are zero-runtime-cost dead code that wants the careful rule-by-rule Stage-N pass, not a tired-tail-end removal).
- **`needsGlyph` rename** — left as-is in Phase 2 (it's live logic; renaming is a Stage-N cosmetic/clarity task, not worth risking output mid-Phase-2).
- **Deploying §I.k separately** — it rode the Phase-2 deploy (dormant; harmless).
- **Committing `~/dotfiles`** — not done unilaterally (steward's governance/memory repo).

## Skill harvest (proposals — steward authorization required)
- **Extend the proposed SCSS-render-equivalence verification-ladder into a general "build-output byte-equivalence gate for refactors"** — the pattern proved itself a *third* time today (after SCSS refactors and §I.k's synthetic-corpus gate): snapshot baseline output → refactor → per-output byte-diff to prove a no-op, isolating intended changes. Covers SCSS, `site.hs` generators (Phase 2), and Pandoc AST transforms (§I.k). Candidate: fold into the existing verification-ladder candidate in the skill-harvest register rather than a new skill. Carry the prior unauthorized register entries (`/spec-code-audit`, `bmf-diagnose`, `/arc-typeset`, `/pre-build-audit`, `/vignette`, `trust-prior-pass-frame`, `anchoring-on-stale-snapshot`).