David F GliddenandClaude Opus 4.8
3f9a89b00c
Basic Memory v0.21.6 first sync over the live memory dir (steward-authorized live-dir trial, Option A 2026-06-06): adds permalink: to frontmatter, refolds long YAML description lines, strips final newlines. Bodies untouched — verified via full diff classification. From this commit forward, any diff in claude/memory shows only what Basic Memory or the session writes. Trial design: MemPalace untouched as incumbent; git status check on this dir at every wrap; end-of-day evaluation (recall quality, sync robustness, rebuild-from-files, malformed-file behavior). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
128 lines
8.1 KiB
Markdown
128 lines
8.1 KiB
Markdown
---
|
||
name: ARC §IV ornament classes — spec vs content mismatch (substantive future work)
|
||
description: Surfaced 2026-05-03 during _utilities.scss SCSS audit. §IV explicitly
|
||
retires the seven ornament classes (.ornament.completion, .asterism, .marginalia,
|
||
.lozenge, .gloss, .glimpse, .photo-essay). Content corpus actually uses .ornament
|
||
classes ~213 times (mostly the retired ones plus 8 additional informal extensions
|
||
never in the spec). Either the spec needs to be updated to reflect content reality,
|
||
OR the content needs migration to whatever the spec considers the replacement. Decision
|
||
is steward's; the work is substantial either way. Tied closely to project-arc-pause-close-ornament-and-hr-audit-pending.
|
||
type: project
|
||
originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
|
||
permalink: claude-memory/project-arc-ornament-spec-vs-content-mismatch-pending
|
||
---
|
||
|
||
# ARC §IV ornament classes — spec vs content mismatch (pending)
|
||
|
||
**Surfaced:** 2026-05-03 during `_utilities.scss` SCSS audit (commit `95a48df`-adjacent). The audit revealed substantial mismatch between what spec §IV says and what content actually uses.
|
||
|
||
## The mismatch
|
||
|
||
Spec §IV (line 781) explicitly retires the seven ornament classes:
|
||
|
||
> *"Previously the taxonomy named seven ornaments: `.ornament.completion` (❦), `.ornament.asterism` (⁂), `.ornament.marginalia` (❧), `.ornament.lozenge` (◊), `.ornament.gloss` (✎), `.ornament.glimpse` (◉), `.ornament.photo-essay` (⊙⊙⊙). All seven are retired. The semantic roles they served – turn-in-thought, journey, gloss, glimpse, photo-essay, major transitions, default hr-replacement – are now either (a) carried by the type system via `class:` frontmatter, or (b) handled structurally by the silence taxonomy in §II."*
|
||
|
||
Content reality (audited 2026-05-03):
|
||
|
||
| Variant | Source uses | Rendered | Spec status |
|
||
|---|---|---|---|
|
||
| `.ornament.completion` | **76** | 28 | spec-retired |
|
||
| `.ornament.section` | 52 | 0 | not in original 7; CSS-only extension |
|
||
| `.ornament.glimpse` | 46 | 0 | spec-retired |
|
||
| `.ornament.chamber` | 13 | 10 | not in original 7 |
|
||
| `.ornament.musical` | 12 | 5 | not in original 7 |
|
||
| `.ornament.travel` | 7 | 3 | not in original 7 |
|
||
| `.ornament.hermetic` | 5 | 4 | not in original 7 |
|
||
| `.ornament.chapter` | 1 | 1 | not in original 7 |
|
||
| `.ornament.asterism` | 1 | 1 | spec-retired |
|
||
| `.ornament.marginalia` / `.lozenge` / `.triple` / `.article` / `.photo-essay` | 0 | 0 | spec-retired (or never used extensions) |
|
||
|
||
**Total: ~213 ornament uses in content source, ~57 in rendered HTML.** The discrepancy between source and rendered counts itself is interesting — many `.ornament.section` and `.ornament.glimpse` source uses (98 combined) don't appear in rendered HTML, suggesting Pandoc/Hakyll strips these in some path. Worth investigating separately.
|
||
|
||
`.ornament` (181 total source uses) is the heavily-used apparatus the corpus depends on. Removing the SCSS rules would break rendered content immediately.
|
||
|
||
## The architectural question
|
||
|
||
Two genuine paths, each substantive:
|
||
|
||
### Option A: Spec is right; content needs migration
|
||
|
||
Honor the §IV retirement. Audit all ~213 `.ornament.*` uses in content; replace each with the appropriate replacement per §IV's stated resolution (`class:` frontmatter for content-type-specific marks; §II silence for structural transitions; the future Pause/Close ornament for piece-end and major within-piece breaks).
|
||
|
||
Cost:
|
||
- Read each ornament use in context to determine which replacement is appropriate
|
||
- Edit ~213 markdown files (or fewer; multiple uses per file)
|
||
- Verify rendered output for each
|
||
- Update spec to reflect that the retirement is now actually complete
|
||
- Likely 4-6 hours of focused work
|
||
|
||
Benefit:
|
||
- Spec and content coherent
|
||
- Alexandrian "alive" goal met — system is generative from spec
|
||
- Future ornament work (Pause/Close design) lands cleanly into a system that doesn't have legacy ornament uses everywhere
|
||
|
||
### Option B: Content is right; spec needs update
|
||
|
||
Revise §IV to acknowledge the seven aren't actually retired in current practice. The .ornament class system is in active use across the corpus; the "retirement" was aspirational without follow-through. Update §IV to:
|
||
- Document the actually-used variants (the 7 spec'd plus 8 informal extensions)
|
||
- Define each ornament's semantic occasion clearly
|
||
- Decide which of the informal extensions deserve formal spec status vs which should retire
|
||
- Reconcile the spec's "(a) class: frontmatter, (b) silence taxonomy" framing with the persistent ornament use
|
||
|
||
Cost:
|
||
- Substantial spec rewrite of §IV
|
||
- Per-ornament semantic articulation
|
||
- Possibly some content cleanup of rare/accidental uses
|
||
- 2-3 hours of focused spec work
|
||
|
||
Benefit:
|
||
- Spec matches reality immediately
|
||
- No content migration risk
|
||
- Acknowledges that the "seven ornaments retired" was never enforced
|
||
|
||
### Steward decision 2026-05-03: Option A — content migration
|
||
|
||
> *"The ornaments are retired, but the content needs to be cleaned up as well, not just the scss."*
|
||
|
||
Spec is right; content needs migration. The .ornament class system is genuinely retired per §IV; the ~213 content uses are legacy that need cleanup. The Alexandrian generative-system commitment is honored: spec is the source from which content flows.
|
||
|
||
Migration work scope:
|
||
|
||
- Read each `.ornament.*` use in context to determine which §IV-stated replacement applies:
|
||
- **`class:` frontmatter** for content-type-specific marks (e.g., a glimpse-style mark on a glimpse post becomes the Glimpse type-glyph in Reading Compass, not an apparatus ornament)
|
||
- **§II silence** for structural transitions where whitespace alone serves
|
||
- **Future Pause/Close ornament** for piece-end and major within-piece transitions (depends on the Pause/Close design landing — see `project-arc-pause-close-ornament-and-hr-audit-pending.md`)
|
||
- Edit affected markdown files (~50-100 files, multiple uses each)
|
||
- After content migration complete: SCSS `.ornament` rules retire entirely from `_utilities.scss`
|
||
- Update §IV spec to confirm retirement is now actually complete, not aspirational
|
||
|
||
Cost estimate: 4-6 hours of focused work spanning content audit + per-file editing + verification + spec close.
|
||
|
||
Realistic order:
|
||
|
||
1. (FIRST) Pause/Close ornament design + hr audit work lands per the related project memory — establishes what the .completion / piece-end uses migrate INTO
|
||
2. (THEN) Per-file content audit: classify each ornament use; perform replacement
|
||
3. (THEN) Retire .ornament SCSS from `_utilities.scss`
|
||
4. (THEN) Update §IV to confirm retirement is operative not aspirational
|
||
|
||
## Tied to: Pause/Close ornament design
|
||
|
||
This question is *intimately tied* to `project-arc-pause-close-ornament-and-hr-audit-pending.md`. The Pause/Close ornament design specifies a *replacement* for the retired-ornament functions. If the broader ornament system is being kept (Option B), the Pause/Close work happens within the existing .ornament architecture. If the broader ornament system is being retired (Option A), the Pause/Close work happens in a *new* mechanism (likely .ornament.pause and .ornament.close as the canonical pair).
|
||
|
||
These two project memories should be considered together when the steward sits down to do this work. Realistically: half-day to full-day focused session covering both questions. Not urgent.
|
||
|
||
## What's NOT changing as a result of this surface
|
||
|
||
- `.ornament` SCSS rules in `_utilities.scss` STAY intact for now (rendering content depends on them)
|
||
- The seven retired ornaments + 8 informal extensions all keep their CSS
|
||
- Spec §IV stays as-written (with the open-question subsection added today)
|
||
- Content stays as-is (no migration started)
|
||
|
||
This is a SURFACE for steward decision, not a fix to ship.
|
||
|
||
## Cross-references
|
||
|
||
- **Spec §IV Ornament Taxonomy** — current retirement language at line 781
|
||
- **`project-arc-pause-close-ornament-and-hr-audit-pending.md`** — the related Pause/Close design + hr content audit (consider together)
|
||
- **`project-arc-spec-master-typographer-audit-pending.md`** — the broader Bringhurst/Rutter/Tschichold compliance audit (this ornament question is one specific item)
|
||
- **_utilities.scss audit commit** — `95a48df` (stage 1 dead-code purge that surfaced this) |