WORK-636
ID:WORK-636Status:ready

realm and faction as composed runes

SPEC-147: realm (Place) and faction (Organization) share character's shape, sections plus a preamble, and each has a -section child rune that composition removes. Their media split maps to {% mediatext %}. Both follow WORK-625's pattern:

Priority:mediumComplexity:moderateMilestone:v0.41.0Source:SPEC-147
changeset-release/main View source

Criteria completion

Criteria completion: 0 of 7 (0%) checked; tracking started on Oct 8, no incremental history yet0%25%50%75%100%Oct 8Oct 11

Tracking started Oct 8 — check back for trends.

Relationships

Implements 1
Related 5
Branches 3
changeset-release/main current ready
claude/v041-composed-realm-faction doneclaude/post-v0.38-roadmap-jb7pie donemain done
History 2
  1. f5d1e00
    Created (ready)by github-actions[bot]
  2. fad3ced
    Content editedby Claude
    plan: draft v0.41.0 — Composed runes you can ship

Acceptance Criteria

  • realm and faction are each defined as composed runes with their schema rows, sections placed with each, and their declared meta blocks placed with {% metablock %}
  • Each one's JSON-LD is compared against its fixture's recorded output in contracts/seo-baseline/baseline.json, and every difference is explained (SPEC-147 D2)
  • Each registers the same entity, id, data and aliases as the plugin's rune, asserted against the storytelling registry snapshot
  • Content written alongside sections renders, and no data-field="section" is emitted (SPEC-147 D6)
  • The media split uses {% mediatext %}, or the reason it cannot is recorded
  • SPEC-145 D7's realm example matches the measured definition
  • plugins/storytelling/ is unchanged and still passing its own tests (SPEC-147 D1)