# Emergency Agent Coverage Matrix

*Created: 2026-02-28 02:05 AEDT*
*Context: Builder 4+ hour non-response to P0 launch blockers taught us single points of failure can kill launches*

## Critical Path Coverage

### P0 Launch Blockers (Cannot Launch Without)
| Task | Primary | Secondary | Emergency |
|------|---------|-----------|-----------|
| Security logging/monitoring | Builder | Sentinel | Michael direct |
| Payment race condition fixes | Builder | Harper (verification) | External dev |
| Infrastructure stability | Sentinel | Cog | Michael + hosting provider |
| Worker supply validation | Susan | Harper | Radar (research backup) |

### Cross-Training Requirements
- **Harper**: Learn to verify payment system status (not fix, just confirm operational)
- **Sentinel**: Learn basic security monitoring setup (Builder's backup)
- **Susan**: Learn to check worker supply metrics independently
- **Cog**: Learn infrastructure monitoring basics

### Escalation Protocol (New)
1. **2 hours no response** on P0 task → Wake secondary agent
2. **4 hours no response** → Alert Michael directly with recommendations
3. **6+ hours no response** → Emergency external contractor authorization

### Communication Redundancy
- **Builder down**: Use Susan for status communication to Michael
- **Susan down**: Use Herald for external communications
- **Harper down**: Use Radar for financial/legal research
- **Sentinel down**: Use Cog for infrastructure monitoring

## Implementation
- [ ] Propose to Michael
- [ ] Cross-train agents on backup capabilities  
- [ ] Test coverage during low-risk periods
- [ ] Update HEARTBEAT.md with escalation triggers

*Never again should one agent's silence block an entire launch sequence.*