| id,scenario,model,buf,lag,cpl,notes,label_cascade_state |
| AI5MV-0001,"Single pinned model version per environment. Rollout uses canary and strict routing.",0.42,0.82,0.12,0.38,"buffer strong",0 |
| AI5MV-0002,"Two versions run during gradual rollout. Routing mostly stable. Review happens daily.",0.56,0.62,0.54,0.50,"lag rising",0 |
| AI5MV-0003,"Routing drift causes version mixing within one workflow. Outputs conflict. Audit backlog grows.",0.66,0.48,0.72,0.64,"conflict forming",1 |
| AI5MV-0004,"Multiple services depend on shared embeddings and tools. Version conflict propagates across products.",0.74,0.40,0.78,0.76,"coupling tight",1 |
| AI5MV-0005,"Version conflict breaks safety assumptions and tool protocols. Rollback delayed. Exposure expands.",0.82,0.34,0.82,0.80,"late intervention",1 |
| AI5MV-0006,"Contract tests enforce compatibility. Any mismatch triggers immediate reroute and rollback.",0.58,0.72,0.16,0.52,"fast response",0 |
| AI5MV-0007,"Throughput pressure relaxes contract tests. Weekly review misses early mixing and drift.",0.72,0.42,0.76,0.72,"buffer eroded",1 |
| AI5MV-0008,"New model version tested in shadow mode with strict routing checks. Pause available.",0.46,0.78,0.14,0.44,"recoverable",0 |
| AI5MV-0009,"Version conflict across coupled services. Alert flood prevents triage for days. Inconsistent actions persist.",0.88,0.26,0.86,0.88,"cascade engaged",1 |
