Fill in, click Build reply, copy the block, and paste it back into the chat. The machine applies exactly what the block says. Empty answers mean "no answer yet" and stay open.
Should packs carry a supersedes link to the pack they replace, making the spec-anchored chain of custody explicit and queryable?
Should user-facing output adopt the field's words (spec, plan, tasks) alongside ours (pack, pack sections), or keep this system's vocabulary alone?
Machine-owned states stay, with field evidence as justification.
Because: Fowler documents AI-interpreted checklist failure; transitions move only through loom commands.
Packs gain a supersedes link; the superseded stage rides it.
Because: Complete packs are frozen reference; today a new pack points at nothing, so lineage dies.
The deliverable stage is machine-derived and checksum-verified, never owner-set.
Because: An owner-set stage duplicates derived truth and drifts; the two axes (record lifecycle, delivery progress) get two fields: status stays lifecycle, deliverable carries progress.
Stage vocabulary: drafted, planning, in_progress, blocked, awaiting_owner, in_review, delivered, superseded.
Because: One word one meaning; each stage is separable by action: blocked needs a re-plan or unblock, awaiting_owner needs verdicts, in_review needs the closing PASS.
Stories gain acceptance criteria (given/when/then scenarios, AC- ids, same shape as requirement scenarios). Story done is its ACs met by done tasks: direct, owner-authored, machine-verified. Requirement scenarios stay for capability verification. Tasks accept ACs wherever they live; each AC keeps exactly one parent.
Because: Atlassian 3 C's: Confirmation (the AC) defines when the story is complete; the story and its AC are one unit. ACs are intent-altitude, requirement scenarios are solution-altitude. Owner direction with source, 2026-10-09.
The spec section anatomy is: why, stories (title, as/want/so, priority, independent_test, acceptance as given/when/then), edge_cases, requirements (plain MUST, serves a story, no scenarios), success_criteria, constraints, questions, assumptions, out_of_scope. Story done = its ACs met by done tasks.
Because: Three primary sources agree on the load-bearing parts: ACs live on the story (Atlassian 3 C's Confirmation; Spec Kit Acceptance Scenarios verbatim in templates/spec-template.md), priority and independent testability live on the story with the P1-alone-is-MVP rule (Spec Kit), requirements are plain MUST statements (Spec Kit FR-NNN, Kiro EARS), and success criteria and assumptions are spec-level sections we lack. Owner directive 2026-10-09: the spec, high level, codified.