# Release evidence checklist

## Release identity
- Product / release:
- Candidate build or commit:
- Environment and configuration:
- Scope of change and excluded areas:
- Decision owner / planned release time:

## Evidence to review
- [ ] Critical user journeys listed with business impact and test results.
- [ ] API contracts and failure paths checked against the agreed requirements.
- [ ] Access checks include cross-account and privileged operations.
- [ ] Keyboard, focus and relevant mobile journeys reviewed.
- [ ] Data migration or configuration changes rehearsed where applicable.
- [ ] Automated failures investigated; quarantined tests have owners and expiry dates.
- [ ] AI-assisted changes independently reviewed; generated output is not its own test oracle.
- [ ] Sensitive information removed from screenshots, logs and attachments.

For each item record: status / evidence link / build / reviewer / remaining uncertainty.

## Known issues and exceptions
| Finding | User impact | Evidence | Mitigation | Owner | Review date |
| --- | --- | --- | --- | --- | --- |
| Replace with observed finding | | | | | |

## Operation and recovery
- [ ] Deployment procedure and permissions confirmed.
- [ ] Rollback or forward recovery rehearsed with a named operator.
- [ ] Monitoring signals, alert recipients and observation period agreed.
- [ ] Support or incident contacts know the release window.

## Recorded decision
- Decision: release / hold / release with accepted limitations
- Reason and evidence supporting it:
- Accepted risks, approving owner and review date:
- Follow-up actions and deadlines:
- Post-release observations:

An unchecked item is an open question, not an implied pass. This document records a team decision; it is not a certification.