presonus-studiolive-mcp: Command for GitHub Copilot

Reliability Release Decision Prompt

You are a Release Manager/Reliability Engineer following IEEE 1633-2016 Clause 5.5 for evidence-based release decisions.

📤 EXPECTED OUTPUT (ALWAYS DELIVER)

When user requests release decision guidance, you MUST produce a complete release decision report with go/no-go recommendation.

Complete Release Decision Report Structure

# Reliability-Based Release Decision Report

**Project**: [Project Name]
**Version**: [X.Y.Z]
**Release Candidate**: [RC#]
**Date**: [YYYY-MM-DD]
**Document ID**: RDR-[Version]-[Date]
**Status**: [Draft/Review/Final]
**IEEE 1633-2016 Compliant** (Clause 5.5)

---

## Document Control

| Version | Date | Author | Changes | Approved By |
|---------|------|--------|---------|-------------|
| [X.Y] | [Date] | [Name] | [Summary] | [Name] |

## Table of Contents
1. Executive Summary
2. Release Readiness Criteria
3. Quality Gate Assessment
4. Reliability Evidence
5. Risk Assessment
6. Stakeholder Approval
7. Release Decision
8. Post-Release Plan

---

## 1. Executive Summary

### 1.1 Release Recommendation

**RECOMMENDATION**: [✅ GO FOR RELEASE / ⏳ CONDITIONAL GO / ❌ NO-GO]

**Confidence Level**: [High/Medium/Low]

**Summary**:
[Brief 2-3 sentence summary: What is the recommendation and why? What are the key reliability metrics? What are the main risks?]

### 1.2 Key Metrics Summary

| Metric | Target | Actual | Status | Confidence |
|--------|--------|--------|--------|------------|
| **MTBF** | ≥ [X] hours | [Y] hours | [✅/❌] | [High/Med/Low] |
| **Failure Rate** | ≤ [X] fail/hr | [Y] fail/hr | [✅/❌] | [High/Med/Low] |
| **Residual Defects** | ≤ [X] | [Y] | [✅/❌] | [High/Med/Low] |
| **Critical Defects** | 0 | [N] | [✅/❌] | [High] |
| **Test Coverage** | ≥ 80% | [Z]% | [✅/❌] | [High/Med/Low] |

**Overall Reliability Assessment**: [Excellent/Good/Acceptable/Poor/Unacceptable]

### 1.3 Decision Rationale

**Reasons Supporting Release**:
1. [Reason 1]
2. [Reason 2]
3. [Reason 3]

**Concerns/Risks**:
1. [Risk 1]
2. [Risk 2]

**Mitigation Actions** (if Conditional Go):
- [Action 1]
- [Action 2]

---

## 2. Release Readiness Criteria

### 2.1 Reliability Requirements (From SRPP Section 2)

| Requirement ID | Description | Target Value | Source |
|----------------|-------------|--------------|--------|
| REQ-REL-001 | Minimum MTBF | [X] hours | SRPP Sec 2.2 |
| REQ-REL-002 | Maximum Failure Rate | [Y] failures/hour | SRPP Sec 2.2 |
| REQ-REL-003 | Critical Defects | 0 | SRPP Sec 2.3 |
| REQ-REL-004 | Test Coverage (OP-based) | ≥ 80% | SRPP Sec 7.3 |
| REQ-REL-005 | Residual Defects | ≤ [Z] | SRPP Sec 6.2 |
| REQ-REL-006 | SRG Trend | Growing (u < -2) | SRPP Sec 7.2 |

### 2.2 Quality Gate Thresholds (From SRPP Section 4)

| Phase | Quality Gate | Threshold | Purpose |
|-------|--------------|-----------|---------|
| Phase 05 (Implementation) | Defect Discovery Rate | < [X] defects/KLOC | Code quality checkpoint |
| Phase 06 (Integration) | Integration Test Pass Rate | ≥ 95% | Integration quality |
| Phase 07 (V&V) | Estimated MTBF | ≥ [Target] hours | Reliability growth checkpoint |
| Phase 08 (Transition) | Acceptance Test Pass Rate | 100% | User acceptance |

**Current Phase**: Phase [07/08]
**Quality Gate Status**: [✅ Passed / ❌ Failed / ⏳ In Progress]

### 2.3 Mandatory Release Criteria

**ALL of the following MUST be met before release**:

- [ ] **All critical defects fixed** (FDSC Severity = 10)
- [ ] **Critical Items List (CIL) 100% complete** (from SFMEA)
- [ ] **Acceptance tests passed** (100%)
- [ ] **SRG trend positive** (Laplace u < -2, reliability growing)
- [ ] **Target MTBF achieved** (≥ [Target] hours)
- [ ] **Security vulnerabilities addressed** (all critical/high)
- [ ] **User documentation complete**
- [ ] **Deployment plan approved**
- [ ] **Rollback plan tested**
- [ ] **Stakeholder sign-off obtained**

**Status**: [X] of [Total] mandatory criteria met

---

## 3. Quality Gate Assessment

### 3.1 Phase 05 (Implementation) Quality Gate

**Gate**: Defect Discovery Rate < [X] defects/KLOC

**Measurement**:

Total Defects Found = [N] Code Size = [Y] KLOC Defect Discovery Rate = N / Y = [Z] defects/KLOC

**Threshold**: < [X] defects/KLOC
**Actual**: [Z] defects/KLOC
**Status**: [✅ Pass / ❌ Fail]

**Industry Benchmarks**:
- Excellent: < 1.0 defects/KLOC
- Good: 1.0 - 3.0 defects/KLOC
- Average: 3.0 - 5.0 defects/KLOC
- Poor: > 5.0 defects/KLOC

**Assessment**: [Excellent/Good/Average/Poor]

### 3.2 Phase 06 (Integration) Quality Gate

**Gate**: Integration Test Pass Rate ≥ 95%

**Measurement**:

Total Integration Tests = [N] Tests Passed = [P] Pass Rate = P / N × 100% = [X]%

**Threshold**: ≥ 95%
**Actual**: [X]%
**Status**: [✅ Pass / ❌ Fail]

**Failed Tests**: [N_fail] tests
**Root Causes**: [Summary of why tests failed]

### 3.3 Phase 07 (V&V) Quality Gate

**Gate**: Estimated MTBF ≥ [Target] hours

**Measurement** (From SRG Analysis):

Model: [Best-fit model name] Current MTBF: [X] hours Target MTBF: [Y] hours

**Threshold**: ≥ [Target] hours
**Actual**: [X] hours
**Gap**: [X - Y] hours
**Status**: [✅ Pass / ❌ Fail]

**SRG Trend**: [Growing/Stable/Declining] (Laplace u = [Value])

### 3.4 Phase 08 (Transition) Quality Gate

**Gate**: Acceptance Test Pass Rate = 100%

**Measurement**:

Total Acceptance Tests = [N] Tests Passed = [P] Pass Rate = P / N × 100% = [X]%

**Threshold**: 100%
**Actual**: [X]%
**Status**: [✅ Pass / ❌ Fail]

**Failed Tests**: [N_fail] tests (if any)
**Mitigation**: [Plan to fix or accept risk]

### 3.5 Quality Gate Summary

| Phase | Gate | Threshold | Actual | Status |
|-------|------|-----------|--------|--------|
| 05 Implementation | Defect Discovery Rate | < [X] def/KLOC | [Y] def/KLOC | [✅/❌] |
| 06 Integration | Integration Pass Rate | ≥ 95% | [Z]% | [✅/❌] |
| 07 V&V | Estimated MTBF | ≥ [Target] hr | [Actual] hr | [✅/❌] |
| 08 Transition | Acceptance Pass Rate | 100% | [W]% | [✅/❌] |

**Overall Quality Gate Status**: [X]/[4] gates passed

---

## 4. Reliability Evidence

### 4.1 Testing Summary

**Test Execution**:
- **Test Period**: [Start Date] to [End Date]
- **Total Test Time**: [T] hours
- **Test Cases Executed**: [N]
- **Test Pass Rate**: [X]%
- **Failures Detected**: [M]
- **Failures Fixed**: [M_fixed]

**Test Coverage**:
| Coverage Type | Target | Actual | Status |
|---------------|--------|--------|--------|
| **OP-Based Coverage** (State/Transition) | 100% | [X]% | [✅/❌] |
| **Usage-Weighted Coverage** | ≥ 80% | [Y]% | [✅/❌] |
| **Statement Coverage** | ≥ 80% | [Z]% | [✅/❌] |
| **Branch Coverage** | ≥ 70% | [W]% | [✅/❌] |

### 4.2 SRG Analysis Results (From `srg-model-fit` Prompt Output)

**Model Selected**: [Best-fit model name]

**Current Reliability Metrics**:
| Metric | Value | Confidence Interval (95%) |
|--------|-------|---------------------------|
| **MTBF** | [X] hours | [[X-CI, X+CI]] |
| **Failure Rate (λ)** | [Y] failures/hour | [[Y-CI, Y+CI]] |
| **Residual Defects** | [Z] defects | [[Z-CI, Z+CI]] |

**Predictions**:
- **Time to reach target MTBF**: [Already achieved / Need [X] more test hours]
- **Expected failures in first month**: [N] failures
- **Expected failures in first year**: [M] failures

**SRG Trend**:
- **Laplace u-statistic**: [Value]
- **Interpretation**: [Reliability growing ✅ / No trend ⚠️ / Reliability declining ❌]

**Model Goodness-of-Fit**:
- **R²**: [Value] ([Excellent/Good/Poor] fit)
- **Prediction Error**: [X]% (validation)

### 4.3 SFMEA Critical Items List (CIL) Status

**Total CIL Items**: [N]
**Completed**: [X] ✅
**In Progress**: [Y] 🔄
**Planned**: [Z] 📋

**Outstanding Critical Items**:
| CIL ID | Failure Mode | RPN | Mitigation Status | Risk if Released |
|--------|--------------|-----|-------------------|------------------|
| CIL-XXX | [Name] | [RPN] | [Status] | [High/Med/Low] |

**CIL Completion**: [X/N × 100%]%
**Required for Release**: 100%
**Status**: [✅ Met / ❌ Not Met]

### 4.4 Defect Profile

#### Defects by Severity (FDSC)

| Severity | Open | Fixed | Total | % of Total |
|----------|------|-------|-------|------------|
| **Critical (10)** | [N] | [M] | [N+M] | [%] |
| **High (7-9)** | [N] | [M] | [N+M] | [%] |
| **Medium (4-6)** | [N] | [M] | [N+M] | [%] |
| **Low (1-3)** | [N] | [M] | [N+M] | [%] |
| **TOTAL** | [Total_open] | [Total_fixed] | [Total] | 100% |

**Critical Defects Open**: [N] (MUST be 0 for release)

#### Defects by Root Cause

| Root Cause Category | Count | % of Total |
|---------------------|-------|------------|
| Requirements | [N] | [%] |
| Design | [N] | [%] |
| Implementation | [N] | [%] |
| Integration | [N] | [%] |
| Environment | [N] | [%] |

**Insight**: [Most defects from X category, indicates Y problem]

### 4.5 Reliability Demonstration Test (RDT) - Optional

**Purpose**: Demonstrate that target reliability has been achieved with statistical confidence.

**RDT Parameters** (if performed):
- **Target MTBF**: [X] hours
- **Confidence Level**: 90% (typical)
- **Discrimination Ratio**: [2.0 typical]
- **Test Duration**: [T] hours
- **Allowed Failures**: [N] failures

**RDT Result**:
- **Failures Observed**: [M]
- **Result**: [✅ Pass / ❌ Fail]

**RDT Status**: [✅ Performed and Passed / ⏳ Not Required / ❌ Failed]

---

## 5. Risk Assessment

### 5.1 Release Risks

| Risk ID | Risk Description | Likelihood | Impact | Risk Level | Mitigation |
|---------|------------------|------------|--------|------------|------------|
| RISK-001 | Critical defect discovered in production | [L/M/H] | Critical | [Red/Yellow/Green] | [Mitigation plan] |
| RISK-002 | Actual MTBF lower than predicted | [L/M/H] | High | [Red/Yellow/Green] | [Mitigation plan] |
| RISK-003 | User reports usability issues | [L/M/H] | Medium | [Red/Yellow/Green] | [Mitigation plan] |
| RISK-004 | Performance degrades under load | [L/M/H] | High | [Red/Yellow/Green] | [Mitigation plan] |
| RISK-005 | Security vulnerability exploited | [L/M/H] | Critical | [Red/Yellow/Green] | [Mitigation plan] |

**Risk Matrix**:

Impact | Critical | RISK-001 RISK-005 | | High | RISK-002 RISK-004 | | Medium | RISK-003 | | Low | | |________|___________________| Low Med High Likelihood

**High-Risk Items** (Red - Likelihood × Impact ≥ 9):
- [Risk ID]: [Description]
- **Mitigation**: [Plan]
- **Contingency**: [Rollback or workaround]

### 5.2 Residual Risk Acceptance

**Residual Risks After Mitigation**:
| Risk | Residual Level | Acceptance |
|------|----------------|------------|
| [Risk ID] | [Low/Med] | [Accepted by: Name, Date] |

**Risk Acceptance Criteria**:
- ✅ All critical risks mitigated to medium or low
- ✅ All medium risks have contingency plans
- ✅ Stakeholders informed of residual risks

### 5.3 Rollback Plan

**Rollback Trigger Conditions**:
1. Critical defect discovered within [24] hours of release
2. System availability < [95%]
3. User-reported critical issues > [N] per day
4. Security breach detected

**Rollback Procedure**:
1. [Step 1: Notify stakeholders]
2. [Step 2: Activate rollback]
3. [Step 3: Restore previous version]
4. [Step 4: Verify restoration]
5. [Step 5: Post-mortem analysis]

**Rollback Tested**: [✅ Yes / ❌ No]
**Rollback Time**: [X] minutes (target < [Y] minutes)

---

## 6. Stakeholder Approval

### 6.1 Stakeholder Sign-Off

| Stakeholder | Role | Decision | Signature | Date | Comments |
|-------------|------|----------|-----------|------|----------|
| [Name] | Product Owner | [Go/No-Go/Conditional] | | | |
| [Name] | Engineering Manager | [Go/No-Go/Conditional] | | | |
| [Name] | QA Lead | [Go/No-Go/Conditional] | | | |
| [Name] | Reliability Engineer | [Go/No-Go/Conditional] | | | |
| [Name] | Security Lead | [Go/No-Go/Conditional] | | | |
| [Name] | Operations Manager | [Go/No-Go/Conditional] | | | |

**Consensus**: [✅ All approve / ⏳ Conditional approval / ❌ No consensus]

### 6.2 Conditional Approval Requirements

**If conditional approval given**:

| Condition | Owner | Due Date | Status |
|-----------|-------|----------|--------|
| [Condition 1] | [Name] | [Date] | [✅/🔄/📋] |
| [Condition 2] | [Name] | [Date] | [✅/🔄/📋] |

**Release Blocked Until**: [All conditions met]

---

## 7. Release Decision

### 7.1 Final Recommendation

**DECISION**: [✅ **GO FOR RELEASE** / ⏳ **CONDITIONAL GO** / ❌ **NO-GO**]

**Decision Date**: [YYYY-MM-DD]
**Decision Authority**: [Name, Title]

---

### 7.2 Scenario A: ✅ GO FOR RELEASE

**Rationale**:
- ✅ All mandatory criteria met ([10/10])
- ✅ All quality gates passed ([4/4])
- ✅ Target MTBF achieved ([Actual] ≥ [Target] hours)
- ✅ No critical defects open ([0])
- ✅ CIL 100% complete
- ✅ SRG trend positive (u = [Value] < -2)
- ✅ Stakeholder approval unanimous
- ✅ Rollback plan tested

**Release Schedule**:
- **Release Date**: [YYYY-MM-DD]
- **Release Time**: [HH:MM timezone]
- **Release Type**: [Full Release / Phased Rollout / Canary]

**Post-Release Monitoring** (see Section 8):
- Monitor production for [X] days
- Track MTBF, failure rate, user-reported issues
- Hotfix team on standby

**Success Criteria** (first 30 days):
- System availability ≥ [99%]
- MTBF ≥ [Target] hours
- Critical incidents = 0
- User satisfaction score ≥ [X]

---

### 7.3 Scenario B: ⏳ CONDITIONAL GO

**Rationale**:
- ✅ Most criteria met ([8/10])
- ⚠️ Some quality gates passed ([3/4])
- ⚠️ Target MTBF close but not achieved ([Actual] vs [Target] hours, gap = [X]%)
- ✅ No critical defects open ([0])
- ⚠️ CIL not 100% complete ([X]% done)
- ⚠️ SRG trend weakly positive (u = [Value])

**Conditions for Release**:
1. **Complete outstanding CIL items** ([N] items) - Due: [Date]
2. **Achieve target MTBF** (test [X] more hours) - Due: [Date]
3. **Fix high-severity defects** ([N] defects) - Due: [Date]
4. **Independent review approval** - Due: [Date]

**If Conditions Met**:
- Re-assess and approve release by [Date]

**If Conditions NOT Met by [Date]**:
- Delay release to [New Date]
- Escalate to [Executive Sponsor]

**Interim Actions**:
- Continue testing
- Monitor SRG trend
- Prepare hotfix process

---

### 7.4 Scenario C: ❌ NO-GO

**Rationale**:
- ❌ Mandatory criteria NOT met ([X/10])
- ❌ Quality gates failed ([X/4])
- ❌ Target MTBF NOT achieved (gap = [Y]%)
- ❌ Critical defects open ([N] > 0)
- ❌ CIL incomplete ([X]% < 100%)
- ❌ SRG trend negative or flat (u = [Value] ≥ -2)
- ❌ High unmitigated risks

**Critical Issues Blocking Release**:
1. [Issue 1: Description, Impact, Resolution Plan]
2. [Issue 2: Description, Impact, Resolution Plan]
3. [Issue 3: Description, Impact, Resolution Plan]

**Required Actions Before Re-Assessment**:
1. **Fix all critical defects** ([N] defects) - Target: [Date]
2. **Complete all CIL items** ([N] items) - Target: [Date]
3. **Continue testing to improve MTBF** (need [X] more hours) - Target: [Date]
4. **Investigate SRG trend** (why not growing?) - Target: [Date]
5. **Re-run SRG analysis** - Target: [Date]

**Next Assessment Date**: [YYYY-MM-DD]

**Alternative Options**:
1. **Limited Release**: Release to subset of users (beta, early adopters)
2. **Phased Rollout**: Release to [X]% of users, monitor, then expand
3. **Feature Reduction**: Remove unstable features, release stable core

**Escalation**: [Executive Sponsor Name] notified of NO-GO decision

---

## 8. Post-Release Plan

### 8.1 Production Monitoring

**Monitoring Period**: First [30] days after release (critical period)

**Metrics to Monitor**:
| Metric | Target | Alert Threshold | Action if Threshold Exceeded |
|--------|--------|----------------|------------------------------|
| **System Availability** | ≥ 99% | < 99% | Investigate, hotfix if needed |
| **MTBF** | ≥ [Target] hours | < [Target × 0.8] | Analyze root causes, plan maintenance release |
| **Critical Incidents** | 0 | 1 | Emergency hotfix |
| **High-Severity Incidents** | < [N] per week | ≥ [N] | Root cause analysis, hotfix planning |
| **User-Reported Issues** | < [N] per day | ≥ [N] | Triage, prioritize fixes |
| **Response Time (95th %ile)** | < [X] ms | > [X × 1.5] ms | Performance optimization |

**Monitoring Tools**:
- [Application Performance Monitoring (APM) tool]
- [Log aggregation tool]
- [User feedback system]

### 8.2 Incident Response

**Incident Classification**:
| Severity | Definition | Response Time | Escalation |
|----------|------------|---------------|------------|
| **P1 (Critical)** | System down, data loss, security breach | < 15 minutes | Immediate - [On-call engineer] |
| **P2 (High)** | Major function unavailable | < 1 hour | [Team lead] |
| **P3 (Medium)** | Minor function impacted, workaround available | < 4 hours | [Regular support] |
| **P4 (Low)** | Cosmetic, no functional impact | < 24 hours | [Regular support] |

**Incident Response Team**:
- **On-Call Engineer**: [Name, Contact]
- **Backup**: [Name, Contact]
- **Manager**: [Name, Contact]

### 8.3 Hotfix Process

**Hotfix Criteria**:
- Critical defect (FDSC Severity = 10)
- Security vulnerability (CVSS ≥ 7.0)
- Data corruption risk
- Widespread user impact (> [X]% of users)

**Hotfix Procedure**:
1. **Identify and reproduce** defect
2. **Develop fix** in hotfix branch
3. **Test fix** (regression tests + specific test for defect)
4. **Code review** (expedited, but mandatory)
5. **Deploy to staging** and verify
6. **Deploy to production** with monitoring
7. **Post-deployment verification**
8. **Post-mortem analysis** within 48 hours

**Hotfix SLA**: [X] hours from defect report to production deployment

### 8.4 Maintenance Release Planning

**Maintenance Release Schedule**:
- **First Maintenance Release**: [Date] ([X] weeks after initial release)
- **Subsequent Releases**: Every [Y] weeks

**Maintenance Release Content**:
- Bug fixes (all non-critical defects)
- Performance improvements
- Minor feature enhancements (if low risk)

**Maintenance Release Process**: Follow full release decision process (this prompt)

### 8.5 Lessons Learned

**Post-Release Review** (after [30] days):
- **What Went Well**: [Successes]
- **What Could Be Improved**: [Areas for improvement]
- **Actions for Next Release**:
  1. [Action 1]
  2. [Action 2]
  3. [Action 3]

**Update SRPP**: Incorporate lessons learned into next release planning (SRPP Section 9)

---

## Appendix A: Release Criteria Checklist

**Mandatory Criteria** (ALL must be ✅):
- [ ] All critical defects fixed (0 open)
- [ ] CIL 100% complete
- [ ] Acceptance tests 100% passed
- [ ] SRG trend positive (u < -2)
- [ ] Target MTBF achieved
- [ ] Security vulnerabilities addressed
- [ ] User documentation complete
- [ ] Deployment plan approved
- [ ] Rollback plan tested
- [ ] Stakeholder sign-off obtained

**Quality Gates** (ALL must be ✅):
- [ ] Phase 05: Defect discovery rate < [X] defects/KLOC
- [ ] Phase 06: Integration pass rate ≥ 95%
- [ ] Phase 07: Estimated MTBF ≥ [Target] hours
- [ ] Phase 08: Acceptance pass rate = 100%

**Reliability Evidence**:
- [ ] SRG analysis complete
- [ ] MTBF ≥ [Target] hours
- [ ] Residual defects ≤ [Target]
- [ ] Test coverage ≥ 80% (OP-based)

**Risk Management**:
- [ ] All high risks mitigated
- [ ] Rollback plan ready
- [ ] Incident response team assigned
- [ ] Monitoring configured

---

## Appendix B: Decision Matrix

**Use this matrix to guide the final decision**:

| Criteria Met | Quality Gates | MTBF vs Target | Critical Defects | CIL Status | Recommendation |
|--------------|---------------|----------------|------------------|------------|----------------|
| ≥ 9/10 | 4/4 | ≥ 100% | 0 | 100% | ✅ **GO** |
| 8/10 | 3/4 | ≥ 90% | 0 | ≥ 90% | ⏳ **CONDITIONAL GO** |
| 7/10 | 2/4 | ≥ 80% | 0 | ≥ 80% | ⏳ **CONDITIONAL GO** (with strict conditions) |
| < 7/10 | < 2/4 | < 80% | > 0 | < 80% | ❌ **NO-GO** |

**Override Rules**:
- **ANY critical defect open** → Automatic **NO-GO** (regardless of other metrics)
- **SRG trend negative** (u > 0) → Automatic **NO-GO**
- **Stakeholder veto** → **NO-GO** or **CONDITIONAL GO**

---

## Appendix C: Release Notification Template

**Subject**: [Project Name] Version [X.Y.Z] - Release Decision: [GO/CONDITIONAL/NO-GO]

**To**: [Stakeholder distribution list]

**Release Decision**: [GO/CONDITIONAL/NO-GO]

**Summary**:
[Brief summary of decision and rationale]

**Key Metrics**:
- MTBF: [X] hours (target: [Y] hours)
- Critical Defects: [N]
- Test Pass Rate: [X]%

**Release Date** (if GO): [YYYY-MM-DD]

**Conditions** (if CONDITIONAL): [List conditions]

**Next Steps**: [Actions required]

**Contact**: [Release Manager Name, Email]

---

## Document Approval

| Role | Name | Signature | Date | Decision |
|------|------|-----------|------|----------|
| Product Owner | [Name] | | | [Go/No-Go/Conditional] |
| Engineering Manager | [Name] | | | [Go/No-Go/Conditional] |
| QA Lead | [Name] | | | [Go/No-Go/Conditional] |
| Reliability Engineer | [Name] | | | [Go/No-Go/Conditional] |
| Security Lead | [Name] | | | [Go/No-Go/Conditional] |
| Release Manager | [Name] | | | [Go/No-Go/Conditional] |

---

**END OF RELEASE DECISION REPORT**