Repository navigation
Specify campaign composition: Kind compose operation, story-graph include and module declarations #561
Description
Follow-up to the 2026-10-07 decision in design/90-decisions.md (Content crosses a campaign boundary by composition at load), which settles #293 and #292.
Contract work in design/ before any code:
- the optional, pure
Kindcomposition operation and where the registry fold dispatches it (before tiered validation) - story-graph include declaration (alias, pinned
{id, version}, input/output bindings, exit → host node/ending map) - story-graph module declaration (entry node, exits, declared inputs and outputs)
- prefixing rules for node ids, variables and achievements; reason codes composition raises
- a slice in
design/30-slices.md
Boundary semantics are fixed by the decision entry; this issue is the contract, not a re-decision.
Activity
Contract #561 — campaign composition: includes, attachments, copy
Contract #561 — campaign composition: includes, attachments, copy (#563)
The-Running-Dev commentedon Oct 7, 2026
Contracted in #563: 04 §10.4, 03 §1.1, 11 §3a; the decision entry is in 90-decisions.md, 2026-10-07. The build is slice W120 in design/30-slices.md. The portable format carrying includes is left open.
W120 — One Campaign Can Include Another (#568)