A composition's narrative field is checked at definition load

ADR-047 lets a rune declare one narrative field that accepts only the editorial runes textblock and mediatext, and says the field is never published as structured data. As amended, the field is inferred from its match, and both rules are checked.

claude/post-v0.43-roadmap-mf1ngx View source

Criteria completion

Tracking started Oct 28 — check back for trends.

Relationships

ID:ADR-047Status:proposed

A rune may take editorial runes as a narrative field

Date:2026-10-23

ID:ADR-046Status:accepted

Section's header grammar is anchored and explicit

Date:2026-10-23

ID:v0.46.0Status:complete

v0.46.0 — The theme contract

ID:WORK-675Status:done

The content-boundaries guide documents the narrative field

Priority:lowComplexity:simpleMilestone:v0.46.0

claude/post-v0.43-roadmap-mf1ngx current ready

claude/milestone-v0-44-0-ism7ni done main done claude/value-primitives-and-grid ready

Oct 28, 03:15 PM0ec343f
Content editedby bjornolofandersson
Oct 28, 03:01 PM8c20651
Created (ready)by bjornolofandersson

Acceptance Criteria

A content-model field whose match names editorial runes (tag:textblock, tag:mediatext) and nothing else is recognised as the narrative field
A definition declaring more than one narrative field is rejected at load, naming the fields
A definition whose schema table maps a narrative field is rejected at load, naming the field and the property
A field that mixes editorial runes with other matches is not a narrative field and is not checked as one
reference and inspect show which field is the narrative field
A fixture composition with a story field renders the story between two template parts, publishes no part of it in JSON-LD, and raises no slot-role warning (ADR-046)

References

ADR-047: decisions 1 and 2, as amended.