Update coordination timeouts to 10 seconds

- Faster response hierarchy for better coordination
- Beast (0s) > 5070 (10s) > Mac (10s)
- Specialty override rules unchanged (immediate response)
- More responsive fleet coordination

COORDINATION-PROTOCOL.md

@@ -4,8 +4,8 @@
 
 ### Response Hierarchy
 1. **Beast** (Primary) - First responder for general queries
-2. **5070** (Secondary) - Responds if Beast silent >30s OR dev-related
-3. **Mac** (Tertiary) - Responds if both silent >60s OR audio/mobile
+2. **5070** (Secondary) - Responds if Beast silent >10s OR dev-related
+3. **Mac** (Tertiary) - Responds if both silent >10s OR audio/mobile
 
 ### Specialty Override Rules
 **These bypass hierarchy - immediate response required:**
@@ -49,7 +49,7 @@
 **Multiple Bots Want to Respond:**
 1. Check if it's your specialty → Respond immediately
 2. Complex cross-domain → Call deliberation
-3. Simple hierarchy → Defer to higher tier unless they're silent
+3. Simple hierarchy → Defer to higher tier unless they're silent >10s
 4. When in doubt → Let primary respond, offer follow-up if needed
 
 **Response Coordination:**
@@ -70,7 +70,7 @@
 **When to Break Silence:**
 - Direct @mention or question to you
 - Your specialty area needs input
-- Primaries have been silent too long (per hierarchy timeouts)
+- Primaries have been silent >10s (per hierarchy timeouts)
 - Error correction needed
 - Mike needs immediate help
 
@@ -101,5 +101,5 @@
 ---
 
 *Implementation Date: 2026-03-25*
-*Updated: Added deliberation integration*
+*Updated: 10-second timeout for all hierarchy levels*
 *Next Review: When coordination issues arise*