A release review should make it possible to trace the proposed behavior to its design, controls, and evaluation results. Use this pack to collect the evidence needed for a named owner to make a release decision.
1. Identify exactly what is changing
Record release scope, artifact versions, accountable owners, and the review date. Include the model configuration, harness, tool inventory, skills, knowledge sources, and memory policy.
- Pin the versions covered by the review.
- List changed permissions and dependencies.
- Describe effects on existing workflows.
2. Review behavior and boundaries
Evaluate task outcomes alongside inappropriate tool use, untrusted inputs, information retention, failure handling, and recovery. Link observed results to their underlying evidence.
- Test normal, boundary, and failure scenarios.
- Verify that approvals occur before consequential actions.
- Inspect interruption and resumption behavior.
3. Make an accountable release decision
Capture remaining threats, conditions, exceptions, and follow-up dates. Every release criterion needs evidence or a documented exception with an owner.
- Name the decision maker and operational owner.
- Record stop conditions and escalation paths.
- Schedule review of any accepted exception.
Bring the decisions together.
Connect this record to your specifications, controls, evaluations, and operational evidence. Revisit it when the workflow changes.
Explore the complete lifecycle