# Release candidate checklist

Original template: CC0 1.0. Check an item only after recording evidence for this release candidate.

## Candidate identity

- [ ] Record the source revision, content version and engine version used to build this candidate.
- [ ] Archive the packaged candidate and record its checksum.
- [ ] List supported devices and languages, and explain how players update from an earlier release.

## Gameplay and state

- [ ] Test every ending and the conditions that open or close each major route.
- [ ] Test boundary conditions, such as values at route thresholds, and trigger events repeatedly; check for blocked progress, duplicate rewards or unintended scene repeats.
- [ ] Check a new game, save/load and restart, plus saves from each earlier version you claim to support.
- [ ] Check skip, history, rollback and content controls against their intended behavior, including what happens around adult scenes.
- [ ] Have a tester find routes, choices and menus without coaching; record where they get stuck.

## Delivery and presentation

- [ ] Test a fresh installation or the intended browser-hosting context using the packaged candidate.
- [ ] Check for missing assets, test audio and settings, and observe what happens when focus is lost or play is interrupted.
- [ ] Test the minimum supported physical device and compare results with the actual performance budget.
- [ ] Compare the public description, edition differences and system requirements with the candidate players will receive.
- [ ] Review every public preview against the applicable content rules, including restrictions on nudity and sexual imagery.

## Rights and publishing

- [ ] Compare the license register with the files included in the actual package.
- [ ] Check that the package includes the required credits, attribution and third-party notices.
- [ ] Record the exact AI models used, the rights to their inputs, the applicable output terms and any required disclosures.
- [ ] Resolve content, channel and payment eligibility for the actual edition, and record the basis for each decision.
- [ ] Archive the current policy sources and project-specific agreements used for those decisions.

## Support and recovery

- [ ] Prepare the version details and known-issue notes, including how each issue affects play.
- [ ] Provide a support contact or form and bug-report fields for the version, device, reproduction steps and observed result.
- [ ] Back up editable sources and release artifacts independently of the working copies.
- [ ] Document when to roll back or recover a release, the steps to follow and what players should expect for their saves.