Verification checklist
Define the outcome.
Establish the evidence.
A shared acceptance checklist for product, engineering and domain owners. No email required.
Work and ownership
- Name the workflow and release decision owner.
- Define legitimate completion, permitted scope and prohibited effects.
- Version the business rules, initial state and required checks.
- Agree acceptance thresholds and the reviewer’s decision process.
Environment and data
- Use approved fixtures and declared test-system adapters.
- Specify reset, tenant isolation, clock and tool versions.
- Agree interruption, reconciliation, cleanup and quarantine behavior for supported effects.
- Identify authoritative observation sources and their consistency limits.
- Define data rights, redaction, access and retention.
Checks and failures
- Separate checker identity, code and expected outcomes from the agent.
- Include deliberately incorrect results and a valid completion case.
- Exercise retries, changed records, concurrency and unknown effects.
- Verify that missing evidence and checker crashes remain inconclusive.
Comparison and evidence
- Compare baseline and candidate under the same accepted setup.
- Use repeated runs and held-out cases; report sample size and variation.
- Retain source observations, versions, verdicts and coverage.
- Replay the checker decision and record the customer review.
- Measure installation, review, compute and maintenance costs; repeat after model, tool and policy changes.
Make autonomous work verifiable
Define the outcome. Verify the work.
Connect your autonomous workflows to clear acceptance criteria, independent checks and reproducible evidence.