`prominence` axis (page-section family)

Add the header-emphasis axis from SPEC-107: prominence scales a rune's page-section header (eyebrow / title / blurb / rhythm), selecting its typographic register. Unlike elevation it is not universal — it is available only to runes that carry the page-section header model.

main View source

Criteria completion

Tracking started Jun 14 — check back for trends.

Relationships

ID:SPEC-107Status:accepted

Elevation, prominence & the surface-axis decomposition

ID:WORK-423Status:done

elevation depth-ladder axis

Priority:highComplexity:complexMilestone:v0.23.0

ID:v0.23.0Status:planning

v0.23.0 — Surface axes & the skeleton/skin extraction

ID:WORK-425Status:done

Lumina: map the axes + retire the static surface groups

Priority:highComplexity:complexMilestone:v0.23.0

main current done

claude/v023-batch1-foundations done changeset-release/main done main done claude/spec-elevation-prominence-axes ready

Scope

Recognise quiet | normal | prominent | display and emit data-prominence.
Gate availability by structure: offer prominence (via a shared attribute preset) only to the page-section-header family — the runes already sharing pageSectionProperties / sections: { preamble, headline, blurb } (recipe, hero, cta, section, feature, budget, cast, comparison, …). Setting it on a non-header rune (e.g. badge) is a validation error with a clear message.
Add defaultProminence to RuneConfig. The skin owns the magnitude (it may clamp/no-op a value); availability is the engine's concern, degree is the theme's.

Acceptance Criteria

prominence accepts quiet | normal | prominent | display, emitted as data-prominence, on header-family runes only.
A non-family rune rejects prominence with a clear validation error; tests cover an allowed + a rejected rune.
defaultProminence is read from theme RuneConfig; a hero defaulting to display needs no authored attribute, while a compact hero / display recipe can override.

Dependencies

Requires WORK-423 (the axis + RuneConfig default plumbing).

References

SPEC-107 · packages/runes/src/tags/common.ts (pageSectionProperties) · packages/runes/src/attribute-presets.ts.

Resolution

Completed: 2026-06-15

Branch: claude/v023-batch1-foundations (Batch 1).

What was done

RuneConfig.defaultProminence added (types.ts).
Engine: prominence resolves tag.attributes.prominence ?? config.defaultProminence and emits data-prominence — gated to the page-section-header family: hasPageSectionHeader() checks the rune's sections for a header-ish role (header/preamble/title/description). On a header-less rune, prominence is ignored with a dev warning (the "rejection"). The raw prominence attribute is stripped from pass-through.

Notes

Availability is the engine's concern (family-gated); magnitude is the skin's (WORK-425 maps it to a type register).
prominence.test.ts: emission on a family rune, the per-rune default (hero→display, no attr) + author override (compact hero), the header-less ignore+warn, and the no-leak check. 6 tests green; full transform suite (520) green.