Release Templates¶
Purpose¶
These templates support ES-110 — Release Readiness.
Use this family after ES-109 testing has produced verification evidence. ES-110 is the release decision point. The goal is not to make a release look safe; the goal is to decide honestly whether the evidence supports release, limited pilot, conditional release, deferral, or rejection.
Recommended workflow¶
Testing Readiness Summary
↓
Release Candidate Summary
↓
Release Scope
↓
Release Evidence Index
↓
Defect and Risk Assessment
↓
Guardrail Release Review
↓
AI Release Review
↓
Release Conditions
↓
Release Readiness Review
↓
Release Decision Record
↓
Release Readiness Summary
↓
ES-111 Operational ReadinessCopy location¶
Do not edit the reusable templates directly. Copy completed project versions into:
docs/project-workspace/release/
Template set¶
Release Candidate Summary
Identify candidate, baseline, commit, tag, type, capabilities, exclusions, and decision question.
02Release Scope
Define release type, in-scope items, out-of-scope items, disabled capabilities, limits, and rationale.
03Release Evidence Index
Index requirements, architecture, design, implementation, integration, testing, defect, guardrail, and AI evidence.
04Defect and Risk Assessment
Assess open defects, release risks, must-fix issues, accepted risks, deferred items, and release impact.
05Guardrail Release Review
Review guardrail status, verification evidence, release impact, blocking issues, and conditional issues.
06AI Release Review
Review AI capability status, verification evidence, controls, release decision, and restrictions.
07Release Conditions
Document required conditions, monitoring, rollback, stop criteria, communication, and post-release review.
08Release Readiness Review
Conduct formal release readiness review, checklist, findings, action items, and ES-111 considerations.
09Release Decision Record
Record release decision, rationale, evidence considered, accepted risks, follow-up, and authority.
10Release Readiness Summary
Summarize ES-110 readiness and decide whether ES-111 operational readiness can begin.
Completion expectations¶
| Question | Evidence |
|---|---|
| What release candidate is being considered? | release_candidate_summary.md |
| What exactly is in or out of release scope? | release_scope.md |
| What evidence supports the release decision? | release_evidence_index.md |
| What defects and risks remain? | defect_and_risk_assessment.md |
| Do guardrails support release? | guardrail_release_review.md |
| Is AI safe, disabled, deferred, or conditional? | ai_release_review.md |
| What conditions must govern release? | release_conditions.md |
| Has release readiness been formally reviewed? | release_readiness_review.md |
| What decision was made and by whom? | release_decision_record.md |
| Can ES-111 operational readiness begin? | release_readiness_summary.md |
Do not treat release readiness as a celebration of completed work. Release readiness is a decision under uncertainty based on evidence, risks, guardrails, AI controls, defects, and operational consequences.
A trustworthy release decision is not just a yes. It records what evidence was considered, what risks were accepted, what conditions apply, who accepted responsibility, and what must be watched next.