# Verify a release and its rollback path — acceptance checklist

Record evidence for every checked item. Unchecked or untested is not a pass. This checklist does not execute an integration or authorise external actions.

## Required inputs

- [ ] The exact revision/version, packaged artifacts and expected public surfaces.

- [ ] An isolated consumer environment plus the approved activation and rollback procedure.

## Output checks

- [ ] Tested and published artifacts have the same recorded hashes.

- [ ] Public content identifies the expected release rather than merely returning 200.

- [ ] Runtime evidence says who observed it and when.

- [ ] Rollback status distinguishes an executed check from a written procedure.

## Deliverables

- [ ] Immutable artifact manifest

- [ ] Clean-consumer receipt

- [ ] Public semantic-response bundle

- [ ] Rollback readiness record

## Evidence and decision

Evidence links: [fill in]
Untested paths: [fill in]
Unresolved findings: [fill in]
Reviewer: [fill in]
Decision and scope: [fill in]

## Boundaries

- The offline checker validates supplied files and declared runtime evidence; it does not contact the site or establish that an installation happened.

- Verification is not deployment authority. Public queries, installation scripts and rollback operations each need the permission appropriate to their actual effects.

Workflow: https://undominated.ai/workflows/#verify-a-release-and-rollback