presonus-studiolive-mcp: Command for GitHub Copilot

🔁 Corrective-Action Loop Prompt

Use this prompt when a verified gap / anomaly / defect is discovered during any Verification & Validation (V&V) activity and must be cycled back through the lifecycle (requirements → architecture → design → implementation → integration → V&V) to ensure the fix is correctly applied, re‑integrated, and re‑verified without introducing regressions.

This workflow aligns with:

• IEEE 1012-2016 (Verification & Validation)
• ISO/IEC/IEEE 12207:2017 (Technical & Maintenance Processes)
• ISO/IEC/IEEE 29148:2018 (Requirements traceability)
• IEEE 1044 (Anomaly classification) (conceptual reference)
• Repository conventions (traceability IDs, lifecycle phases, reliability gates)

📤 EXPECTED OUTPUT

Produce a Corrective Action Package (CAP) markdown document with the following structure:

# Corrective Action Package (CAP)
ID: CAP-[YYYYMMDD]-[SEQ]
Anomaly ID(s): ANOM-[ID], DEF-[ID]
Date Opened: [YYYY-MM-DD]
Owner: [Name]
Integrity Level: [Level 1–4]
Status: {OPEN|IN_PROGRESS|AWAITING_REVERIFY|CLOSED}

## 1. Summary
- Detected In Phase: [06-integration / 07-verification-validation / etc.]
- Detection Activity / Test ID: [TEST-INT-APIAuthFlow]
- Defect Description (Concise):
- User Impact (If Released):
- Severity (FDSC Scale / Business Impact):
- Integrity Level Affected Components:

## 2. Objective Evidence of Failure
| Evidence Type | Reference | Notes |
|--------------|-----------|-------|
| Failing Test | TEST-INT-APIAuthFlow | Reproduces handshake mismatch |
| Log Extract | log-2025-11-08T12:45Z | 500 during token refresh |
| Screenshot (if UI) | evidence/img/auth-refresh.png |  |
| Metrics Spike | METRIC-AUTH-ERROR-RATE | Error rate > gate |

## 3. Root Cause Analysis
- Originating Lifecycle Phase: [Design Definition / Requirements / Implementation]
- Fault Class (e.g., Interface mismatch, Timing, Logic, Data contract):
- Why Introduced? (5-Whys or causal chain)
- Why Not Detected Earlier? (Gap in test / review / spec)
- Contributing Conditions (environmental, concurrency, configuration):

## 4. Impact & Change Scope
| Dimension | Assessment |
|-----------|------------|
| Affected Components | [List modules / services] |
| Coupled Elements | [Interfaces / downstream consumers] |
| Requirements Impacted | REQ-F-021, REQ-NF-005 |
| Design Elements | DES-C-014 (AuthAdapter), DES-IF-007 |
| Architecture Views | Logical, Interface View (update needed?) |
| SFMEA Impact | FM-012 RPN re-evaluation required |
| Reliability Gates | Integration pass rate, MTBF trend unaffected / affected |
| Security / Safety | [If applicable] |

## 5. Change Plan
| Action ID | Type | Description | Owner | Phase Routed To | Preconditions |
|----------|------|-------------|-------|-----------------|---------------|
| ACT-01 | Requirement Update | Clarify token refresh timeout semantics | BA Lead | 02-requirements | Stakeholder approval |
| ACT-02 | Interface Adjustment | Align AuthService refresh contract | Dev Lead | 04-design | ACT-01 complete |
| ACT-03 | Code Fix | Implement adjusted retry / backoff | Dev Team | 05-implementation | ACT-02 merged |
| ACT-04 | Test Additions | Add failing test (system + unit) | QA | 06-integration | Code fix PR open |

## 6. Verification & Validation Iteration Strategy
- Task Iteration Policy Triggered? [Yes/No]
- Re-Verification Scope Determination Method: [Risk-based / Full Regression / Impact-based]
- Regression Test Set Selected: [List test IDs]
- Integrity Level Adjustment? [If Yes → justification]

## 7. Test Artifacts Added / Updated
| Test ID | Type | Purpose | New/Updated | Linked Requirement(s) |
|---------|------|---------|-------------|-----------------------|
| TEST-UNIT-AuthRefreshTimeout | Unit | Reproduce boundary condition | New | REQ-F-021 |
| TEST-INT-APIAuthFlow | Integration | Validate multi-step token renewal | Updated (added scenario) | REQ-F-021 |
| TEST-SYS-SessionResilience | System | Validate session persistence under failures | New | REQ-NF-005 |

## 8. Execution & Evidence
| Step | Description | Result | Evidence Ref |
|------|-------------|--------|--------------|
| 1 | Added failing unit test | FAIL (expected) | TEST-UNIT log |
| 2 | Implemented fix (PR 123) | Build PASS | CI-Run-456 |
| 3 | Unit + Integration Regression | PASS (98 tests) | CI-Run-457 |
| 4 | System Reliability Metrics | Stable (λ decreasing) | Metrics snapshot |

## 9. Traceability Updates
| Artifact Type | ID | Updated? | Link |
|--------------|----|----------|------|
| Requirement | REQ-F-021 | Yes | commit abc123 |
| Design | DES-IF-007 | Yes | ADR-023 |
| Code | src/auth/RefreshService.ts | Yes | PR 123 |
| Test | TEST-UNIT-AuthRefreshTimeout | New | /tests/unit/auth/... |
| SFMEA | FM-012 | RPN revised 180→120 | SFMEA-Auth.md |

## 10. Risk & Integrity Review
- Residual Risk Rating: [Low/Medium/High]
- SFMEA Adjusted? [Yes/No]
- CIL Item Created/Closed? [ID]
- New Hazards Introduced? [If yes → Hazard Log ref]

## 11. Closure Criteria
| Criterion | Status |
|-----------|--------|
| All planned actions complete | ✅ |
| All new/updated tests passing | ✅ |
| Regression suite green | ✅ |
| Traceability matrix updated | ✅ |
| Integrity level re-assessed | ✅ / N/A |
| Stakeholder sign-off obtained | Pending / ✅ |

## 12. Lessons Learned
- Prevention Opportunity:
- Missing Control Identified:
- Action to Institutionalize Learning (e.g., checklist update):

## 13. Sign-Off
| Role | Name | Date | Approval |
|------|------|------|----------|
| QA Lead | | | |
| Reliability Engineer | | | |
| Product Owner | | | |
| Security (if applicable) | | | |

Status: CLOSED / (auto-close after verification)