AI Model Rollback Decision Matrix Generator

Immediate rollback: 5 | Conditional rollback: 0

1. Model response quality regression - Immediate rollback (20)
2. Latency breach on customer-facing workflows - Immediate rollback (18)
3. Prompt-injection exposure in retrieval path - Immediate rollback (18)
4. Cost-per-success spike after routing change - Immediate rollback (18)
5. Tool-call failure amplification - Immediate rollback (17)

# AI Model Rollback Decision Matrix - AI Assistant Platform

## Incident context
- Incident severity: SEV-2
- Customer impact: Medium
- Release stage: Partial rollout
- Fallback readiness: Moderate
- Change failure rate trend: Medium
- Review cadence: 30 minutes

## Decision matrix
| Rank | Decision line | Rollback owner | Blast radius | Detection confidence | Recovery effort | Rollback index | Recommendation | Rollback action | Validation signal |
|---|---|---|---:|---:|---:|---:|---|---|---|
| 1 | Model response quality regression | AI Platform Lead | 5 | 4 | 2 | 20 | Immediate rollback | Rollback to previous stable model version and freeze prompt updates | Task success rate recovers above baseline within 2 review windows |
| 2 | Latency breach on customer-facing workflows | SRE + API Operations | 4 | 4 | 3 | 18 | Immediate rollback | Shift traffic to lower-latency fallback route and disable heavy tool calls | P95 latency returns below SLA threshold and queue depth normalizes |
| 3 | Prompt-injection exposure in retrieval path | Security Engineering | 5 | 3 | 3 | 18 | Immediate rollback | Rollback retrieval configuration and enable strict safe-mode prompt policy | Adversarial test suite passes and exploit logs drop to zero |
| 4 | Cost-per-success spike after routing change | FinOps + Product | 3 | 4 | 2 | 18 | Immediate rollback | Revert routing policy to prior mix and cap premium model traffic | Cost-per-success returns within target band for two consecutive checks |
| 5 | Tool-call failure amplification | Platform Engineering | 4 | 3 | 3 | 17 | Immediate rollback | Disable failing tool chain and route to no-tool fallback response mode | Tool error rate stays below threshold and incident queue stabilizes |

## Rollback execution checklist
1. Confirm incident commander, rollback owner, and communications owner before executing rollback actions.
2. Record rollback decision time, affected traffic scope, and expected verification signal in the incident log.
3. Run two post-rollback validation checks before declaring incident stability.
4. Switch to war-room cadence and review unresolved Immediate rollback lines every 15 minutes.

## Meeting close controls
1. Confirm unresolved rollback lines with owner and next validation timestamp.
2. Capture customer-impact status and communication output before close.
3. Publish next-cycle decision summary with explicit go/hold/rollback rationale.