Use case
Planned
QA & testing
Verify the work against the original acceptance criteria before it's signed off.
What it is
The stage, and what it produces
A delivery agent derives a QA checklist from the acceptance criteria written earlier in the run, so verification maps straight back to what was agreed — not a generic checklist bolted on at the end.
In a run
How it works, step by step
01
Derive checks from the original acceptance criteria
02
Verify the delivered work against them
03
Flag gaps for a human to judge
04
Sign off against the criteria the run started from
QA · from acceptance criteria
- Declined card shows a retry path
- Double-submit stays idempotent
- Expired card handled mid-checkout
- Receipt emailed on success
Illustrative — produced, reviewed and approved before the next step.
Works with
The parts of the platform it leans on
Where it stands. Part of the Planned orchestration — it depends on the earlier checkpoints producing the acceptance criteria.
Turn this stage into a governed output
Start with what ships today, and grow into the full run as it lands.