Dad Joke Visualizer

# 🚨 ERROR COORDINATION PROTOCOL **CRITICAL**: This protocol prevents multiple developers from conflicting when errors are detected. --- ## 🎯 CORE PRINCIPLE **ONE DEVELOPER OWNS THE ERROR RESOLUTION AT A TIME** When errors appear, exactly ONE developer takes ownership and resolves. Others pause and wait. --- ## 📋 DETECTION PROTOCOL ### **When You Detect Errors** 1. **Run Validation** ```bash # After editing your file, run validation: npx tsc --noEmit npm run lint # or your project's validation command ``` 2. **Check Error Ownership** ```bash # Check if the error file is the one YOU just edited git diff --name-only # If error file matches your recent edit: YOUR ERROR # If error file is different: SOMEONE ELSE'S ERROR ``` --- ## 🔴 SCENARIO A: IT'S YOUR ERROR ### **Response (Immediate)** 1. **Announce Error** (update shared context or project status) 2. **Attempt Quick Fix** (5 minutes max) 3. **If Fixed**: Clear announcement and continue 4. **If NOT Fixed in 5 Minutes**: Revert changes and move to next file --- ## 🟡 SCENARIO B: IT'S SOMEONE ELSE'S ERROR ### **Response (Wait and Monitor)** 1. **Check if Another Developer Announced It** 2. **If Yes**: Wait and monitor every 2 minutes 3. **If No**: Alert project lead for orphaned error --- ## 🟢 SCENARIO C: PROJECT LEAD RESOLUTION If multiple developers report conflicting status OR error persists >10 minutes: 1. **All Developers HALT** work immediately 2. **Project Lead Investigates** and resolves 3. **Resume Work** after resolution --- ## ✅ SUMMARY CHECKLIST ### **Before Editing Any File** - [ ] Check project validation (must be clean) - [ ] Verify no other developer has error status ### **After Editing Your File** - [ ] Run validation immediately - [ ] If errors: Determine ownership - [ ] Follow appropriate scenario protocol ### **Error Prevention** - [ ] Always validate before committing - [ ] Announce errors immediately - [ ] Fix within 5 minutes OR revert --- **This protocol ensures ZERO WORK LOSS and maintains project quality.**