How does a release review work?
- Choose what should work. Features describe user or business outcomes, such as receiving a partner webhook.
- Define how to verify each feature. A check states the expected behavior and how to test it.
- Record what happened. A result belongs to that check and this exact version, with an observation or supporting link.
- Review the unresolved items. A release owner decides whether to approve or hold the release.
Screens and architecture add context when needed. Components are the services, APIs, jobs, and databases behind features. Start with one feature; AI is optional.
Blocked
1 blocker ยท 3 evidence gaps
Validation ยท staging-euNeeds attention
3 of 4Features5
What must work in this release? Open a feature to define its checks and record results. Release-wide checks also affect the final decision.