Files
dotfiles/claude/memory/project-multilingual-typography-refinement-2026-05-14.md
T

73 lines
6.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
name: Multilingual typography spec refinement — path from v0.1 to LOCKED
description: Tracks the work needed to take docs/AldineXXI-Codex/multilingual-typography-specification.md from v0.1 (French only, operational-quality) to v1.0 (LOCKED). Captured 2026-05-14 evening after the jurist's architectural correction landed the spec in its current shape. Steward direction: save the assessment, work it after §2 Spanish is sketched.
type: project
originSessionId: 6cef24d0-242b-474e-b8d4-fd568edf5dc2
---
## State as of 2026-05-14 (evening)
The multilingual-typography-specification.md file is operational-quality for §1 French but labeled v0.1 because §2 Spanish is a one-paragraph placeholder and several validation gaps remain. The path to LOCKED is well-defined.
**Architecture is correct.** The two-document hierarchy (AldineXXI upstream, multilingual downstream) per the jurist's standing instruction 2026-05-14 is correctly realized. No structural changes needed. What "v0.1" tracks is content-extension and validation work, not architectural revision.
## Refinement gaps, by category
### Substantive content (the operational gaps)
1. **§2 Spanish** — the biggest single gap. Chamber library has José Martínez de Sousa, *Ortografía y ortotipografía del español* (~12K lines) at `~/_Dev/chamber-library/converted_texts/collections/typography/ortografia-y-ortotipografia-del-espanol-sousa.md`. Drafting §2 follows the same shape as §1 French: scan for the cluster of named entries (espacios, comillas, acentuación de mayúsculas, guiones, cursiva, citas, versalitas), draft conventions in application order. ~1–2h focused session.
2. **Verbatim authority anchors for §1 French** — currently §1 says "consult Lexique *§guillemets*" but doesn't pin to specific Lexique line numbers or verbatim citations. The superseded rough-draft had richer citations (e.g., the verbatim "L'accent a pleine valeur orthographique" from Lexique line 1205 for §1.3 accentuation). Adding ~10–15 verbatim citation anchors (one or two per convention) grounds the rules in the source rather than just pointing at it. ~30–45 min.
3. **Worked examples per convention** — the frontmatter spec has §2.5 worked examples (A/B/C/D) as canonical illustration; the multilingual spec has none. One worked example per convention (e.g., trace the Brown gloss's `« forme latérale de la critique »` phrase through espaces / guillemets / italique / citations) gives the executor concrete templates. ~45 min.
### Validation gaps
4. **Implementation hooks documentation** — a short §1.10 *Implementation hooks across delivery surfaces* would consolidate the scattered SCSS / polyglossia / pandoc-filter realization into one spec-level summary. Currently distributed across the LaTeX templates, the SCSS, and the skill file.
5. **Verification recipes / tests** — no "to check rule X, render piece Y at setting Z, expected:..." protocols. Future iteration where the typography pass actually runs against a real ARC piece (Brown gloss is the immediate candidate) would surface these.
### Lifecycle gaps
6. **Version lock** — currently v0.1; no path-to-LOCKED defined. Promotion criteria: at least §1 French AND §2 Spanish complete, the pass exercised against at least three real pieces, jurist + steward review pass. Similar to the §V "14 of 14 LOCKED" pattern the typology spec uses.
7. **Anchor IDs** for deep linking from other docs — minor; the doc uses `## §1 French` style which works for navigation but not for `#fr-guillemets` style anchor references from external citations. Cosmetic until external docs need to deep-link.
## What is already at spec-grade
Not "rough" — production-ready as of 2026-05-14 evening:
- The architecture (two-document hierarchy correctly realized per jurist's instruction)
- The preamble (three-context framework A/B/C; hybrid discipline U+00A0 / U+202F; `lang:` activation; "does NOT do" boundaries)
- §1 French's seven conventions and their application order
- §1.8 authorization boundaries (what CC does not decide unilaterally)
- §1.9 preparation note format
- Cross-references to AldineXXI, frontmatter, the skill, chamber-library
## Sequencing recommendation
When the steward returns to this:
1. **First** (current session, in progress): sketch out §2 Spanish via Sousa. Replaces the placeholder with operational-quality content.
2. **Then**: add verbatim authority anchors to §1 French AND §2 Spanish (the superseded rough-draft had Lexique line refs; promote them into §1 sub-sections as authority anchors).
3. **Then**: add worked examples per convention. Brown gloss + the Genette/Borges passages are the source material for French; a Spanish piece from the corpus once one exists for Spanish examples.
4. **Then**: write §1.10 + §2.10 implementation hooks documentation.
5. **First real-piece exercise**: run the typography pass against the Brown gloss. Surface edge cases, refine the rules. This is where rules get tested rather than asserted.
6. **Jurist review + LOCKED tag**: with §1, §2, examples, and one real-piece exercise behind us, the jurist reviews and the spec promotes to v1.0 LOCKED.
Estimated total remaining: ~3–5h focused work across 2–3 sessions, plus the first real-piece exercise.
## Filing discipline
- This memory is the canonical assessment; do not duplicate it into the spec itself
- When §2 Spanish lands, update the spec's version header from `v0.1` to `v0.2` (or as the jurist directs)
- When LOCKED, add a `**[LOCKED YYYY-MM-DD]**` tag in the spec header per the §V typology pattern
## Related memory
- `project-arc-pdf-print-postures-session-plan.md` — the PDF/Print session that surfaced the multilingual typography question
- `project-eb-garamond-update-2026-05-14.md` — font infrastructure that supports French/multilingual rendering
- `project-gloss-vs-commentary-distinction.md` — Genette + Carruthers reading that surfaced the typography work
- `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/multilingual-typography-specification.md` — the spec being refined
- `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/drafts/french-typography-rough-draft-2026-05-14.md` — superseded process record
- `~/.claude/skills/french-typography-pass/SKILL.md` — executor-side invocation of §1 French