Acceptance criteria
The checks in a delivery's plan that say what done means, and how they decide when the delivery is ready for review.
Acceptance criteria are the short list in a delivery’s plan that says how you will know the outcome is met. The app calls them acceptance checks. Each is one sentence about the result, plus the type of test that proves it. Agree them before any code is written.
Criteria in the plan
The agent writes the checks into the plan file, from outcomes you stated:
## Acceptance checks
- A refunded order shows its refund and the amount left -- e2e: refund-flow `#refund-shown`
- The refund email reads well -- manual `#refund-email`
- The check: what must be true, in your words.
- The type: unit, integration, end-to-end, manual, agent evaluation or custom. A check with no type is read as manual.
- An id: a short stable name, so the check survives a rewording.
In the app, the checks are on the delivery’s Plan tab under Acceptance criteria.


When a check is met
A check is met when evidence of its type passed at the current code.
- A failure after a pass leaves the check unmet.
- Evidence from older code does not count. When the code changes, the test must run again.
How criteria gate review
- Before the outcome review, the agent passes every check at the current code.
- At the outcome review, you can approve with a check unmet. Blume records that it was open.
- After approval, a check that fails at the approved code withdraws your approval. See Outcome review.
- Before a merge, the agent runs the checks even if you said to ship it, and does not merge if one fails.
- A plan without checks falls back to any passing test evidence at the current code.
Change the criteria
Tell the agent, and it edits the plan file. Changing a check after plan approval ends that approval where the project reviews plans. Changing the plan after outcome approval means the outcome review is asked again.