Problem
"Done" needs to be defined before work begins, and the definition needs to be a record
rather than a conversation.
Scope
- Schema for an acceptance-criteria set attached to a submitted idea: individual criteria,
each with a machine-checkable assertion where possible (test passes, endpoint responds,
command exits 0) and a human-readable statement where not
- Explicit approval step: the criteria set is not active until the submitting customer
approves it, and the approval is recorded with who/when
- Immutability semantics: once work has started, criteria can be added by mutual record but
never silently altered — amendments are new versioned records, not edits, so the delivery
verdict is always traceable to the version that was in force
- Distinguish criteria that are blocking for completion from ones that are advisory
Acceptance
A submitted idea can carry an approved, versioned criteria set; the record shows exactly
what was agreed and when; amendments are visible as amendments.
Out of scope
Generating the criteria from a brief (Epic D), and evaluating them (sibling).
Problem
"Done" needs to be defined before work begins, and the definition needs to be a record
rather than a conversation.
Scope
each with a machine-checkable assertion where possible (test passes, endpoint responds,
command exits 0) and a human-readable statement where not
approves it, and the approval is recorded with who/when
never silently altered — amendments are new versioned records, not edits, so the delivery
verdict is always traceable to the version that was in force
Acceptance
A submitted idea can carry an approved, versioned criteria set; the record shows exactly
what was agreed and when; amendments are visible as amendments.
Out of scope
Generating the criteria from a brief (Epic D), and evaluating them (sibling).