dotfiles/claude/memory/project-arc-pause-close-ornament-and-hr-audit-pending.md

name, description, type, originSessionId, permalink, superseded_by, superseded_on

name	description	type	originSessionId	permalink	superseded_by	superseded_on
ARC §IV Pause/Close ornament design + hr content audit — substantive future work	Two interlocking pieces of work that should be undertaken together — designing the Pause/Close ornament asset (currently described in §IV but yet-to-be-designed), and auditing existing markdown <hr> usage for which instances should retire (replaced by `.ornament.pause`, removed entirely, or kept as legitimate Pause anchors). Not urgent; important. Requires steward design attention + content-audit time.	project	8d9ac240-47df-4578-aec1-a9dd32965027	claude-memory/project-arc-pause-close-ornament-and-hr-audit-pending	project-arc-open-work-register.md	2026-08-17

SUPERSEDED 2026-08-17. Register A2 → [DONE 2026-06-17] — the cul-de-lampe is designed, first-instanced, rolled out to 7 essays, spec resolved. The CONTENT half continues as register B3, which is live work.

Current record: project-arc-open-work-register.md. Kept for detail and provenance — do not read the status below as live.

ARC §IV Pause/Close ornament + <hr> content audit — pending

Origin date: 2026-05-03 — surfaced during the SCSS audit pass. Steward direction: "this needs serious study and thought (and may need to change the Md content files themselves if hr was used incorrectly). Not terribly urgent, but important and should be considered at the same time as the pause/close ornament."

What this is

Two interlocking pieces of work that constitute one unit:

1. Design the §IV Pause + Close ornament asset itself — the designed SVG cul-de-lampe paired-or-twinned that §IV describes functionally but doesn't yet specify visually.

2. Audit existing <hr> usage in content — markdown content uses <hr> (rendered from --- source) at various points; some uses are legitimate Pause anchors (after epigraph, before dateline — within-piece transitions §IV calls "Pause"), some may be incorrect carryover from earlier conventions. Audit identifies which retire and which become .ornament.pause markup.

These two pieces are interdependent: the ornament design informs which content uses are legitimate (because the visible ornament makes some uses intentional that previously felt accidental); the content audit informs which ornament treatments matter most (frequency + position + register-context).

Current interim state (2026-05-03)

<hr> renders as three centered middle-dots · · · (Tschichold-Penguin restrained section-break notation) per _typography.scss hr rule:

hr {
  border: none;
  margin: $space-xl auto;
  text-align: center;
  color: var(--gray);
  &::before {
    content: "· · ·";
    letter-spacing: 0.5em;
    font-size: 1.1em;
    opacity: 0.6;
  }
}

Honestly interim: quiet, typographic, no glyph-conflict with governed characters (none of the seven retired ornaments per §IV; not § Sources marker; not type glyphs ❦ ⁂ ✎ ◉). Signals "this is where the designed Pause ornament will go" without pretending to be the designed ornament.

Pure silence (display: none) was considered and rejected — Bringhurst, Tschichold, Hochuli, and Rutter all argue within-piece transitions need something visible because reader's flow doesn't naturally pause without a cue, especially in long-scroll web context (Rutter is firm on this).

Pending decisions on the ornament design

1. Glyph or motif — culture-of-origin matters:

   • Aldine cul-de-lampe lineage (current §IV framing)?
   • Roman/Pompeian motif aligning with broader palette decisions (Pompeian red, Pompeian green for code)?
   • Something contemporary-but-classical?
   • Off-limits: the seven retired ornaments (❦ ⁂ ❧ ◊ ✎ ◉ ⊙⊙⊙); ❦ reserved Hommage; ⁂ Heteronym; ✎ Gloss; ◉ Glimpse.

2. Asset format — designed SVG strongly preferred (vector, scales crisply across Pause/Close two-scale deployment, hand-drawn character preserved per current §IV.Rendering). Could be a small carefully-drawn raster but vector matches existing §IV intent.

3. Pause/Close relationship — current §IV (line 758): "One designed ornament, two scales." Visual consistency across the site; semantic distinction by scale: smaller = breath within (Pause), larger = end (Close). Could be revised if a paired-but-distinct treatment proves more honest. Bringhurst-Tschichold-Hochuli precedent: usually paired-and-related but not always identical.

4. Implementation mechanism — once designed:

   • Inline SVG (sharp, theme-color-aware via currentColor)
   • Background-image SVG (smaller HTML, less flexible color)
   • Icon font (overkill for one ornament)
   • Inline preferred; current _typography.scss hr ::before mechanism extends naturally.

Pending decisions on the <hr> content audit

For each existing <hr> (markdown ---) instance in content:

• Keep as Pause — legitimate within-piece transition where the visible mark serves the reader (epigraph → body, body → dateline, mid-section register-shift not warranting heading)
• Remove entirely — accidental, carryover from earlier conventions, or structural marker that §II silence + register-markers (§XII.b) handle better
• Convert to .ornament.pause markup — explicit Pause-class HTML so the rendering is intentional rather than HTML-fallback

Audit method:

1. List all <hr> instances in content/ (markdown source: lines starting with --- that are NOT YAML frontmatter delimiters)
2. For each: read surrounding context to classify
3. Apply changes per classification
4. After audit complete + ornament designed: SCSS hr rule retires (or becomes pure-silence fallback for any orphan <hr>)

Why both together

If the ornament design lands first without the content audit: legitimate Pause anchors become more visible (good), but accidental/incorrect uses also become more visible (bad — visual noise where structure should be silent).

If the content audit lands first without the ornament design: legitimate Pause anchors stay at the three-dot interim (acceptable but signals "still pending"), accidental uses are cleaned (good).

Optimal: do both as one focused session — design the ornament with reference to actual usage frequency + register-context the audit reveals; audit content with the designed ornament in mind so the classification reflects how each instance will render.

Cross-references

• Spec §IV Ornament Taxonomy in docs/AldineXXI-Codex/AldineXXI-specification.md — current Pause/Close framing + open question
• Spec §II Spacing Scale — silence taxonomy that handles many transitions without ornament
• Spec §XII.b Register Markers — handles register-naming transitions in left-margin column
• _typography.scss hr rule — current three-dot interim
• Project memory project-arc-spec-master-typographer-audit-pending.md — broader spec-vs-masters compliance audit (this Pause/Close question is one specific item within that broader audit)

Sequencing relative to other work

Not urgent. Sequenced after:

• Current SCSS audit pass completes (the immediate cleanup work)
• v1 chamber collection migration (chamber pages currently render <hr> per their own conventions; auditing their <hr> instances now is wasted work since chamber moves to its own collection)
• Steward has bandwidth for design attention specifically (this isn't a quick fix)

Best moment: a focused half-day session combining ornament design exploration + corpus content audit. Could be steward-led with my support on the audit mechanics, or collaborative throughout.