# Runwise first-release checklist

Use this checklist to prepare a first release. Tailor the checks to your actual data, product, users, and delivery agreement. A checked box needs supporting evidence and an owner.

## Customer value
- [ ] A specific user and buyer are named.
- [ ] The primary workflow solves an observed problem.
- [ ] The expected result and baseline are recorded.
- [ ] MVP stories have observable acceptance criteria.
- [ ] Deferred work is recorded separately.

## Product behavior
- [ ] The main journey is tested from start to completion.
- [ ] Empty, error, duplicate, and retry states are reviewed.
- [ ] Mobile and keyboard access are checked.
- [ ] Onboarding and help explain the next useful action.
- [ ] Customer feedback has an owner and review cadence.

## Production engineering
- [ ] Authentication, roles, and tenant boundaries are verified where required.
- [ ] Data sources and integration permissions are authorized.
- [ ] Backup and restore are tested with a representative recovery case.
- [ ] Secrets are kept out of client code and exported documents.
- [ ] Monitoring, incident ownership, and rollback are defined.
- [ ] Performance is tested against an agreed usage target.
- [ ] Hosting and external-service costs have budgets and owners.

## Release and support
- [ ] Release notes and known limitations are documented.
- [ ] A reviewer accepts the defined scope using evidence.
- [ ] Source, access, and operations documentation are handed over.
- [ ] Support responsibilities and response expectations are agreed.
- [ ] The first outcome review has a date and decision-maker.

Next: prepare the user, scope, and constraints at https://runwise.agency/contact.html.