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
This commit is contained in:
@@ -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*
|
||||
@@ -29,8 +29,8 @@
|
||||
## Failover Hierarchy
|
||||
|
||||
1. **Beast** responds first (primary)
|
||||
2. **5070** responds if Beast silent >30 seconds OR development-related
|
||||
3. **Mac** responds if both silent >60 seconds OR audio/mobile-specific
|
||||
2. **5070** responds if Beast silent >10 seconds OR development-related
|
||||
3. **Mac** responds if both silent >10 seconds OR audio/mobile-specific
|
||||
|
||||
## Quiet Protocols
|
||||
|
||||
@@ -44,8 +44,8 @@
|
||||
- Audio/TTS requests → **Mac responds immediately**
|
||||
- Git/code requests → **5070 responds immediately**
|
||||
- M365/Azure requests → **Beast responds immediately**
|
||||
- General queries → **Hierarchy order**
|
||||
- General queries → **10-second hierarchy order**
|
||||
|
||||
---
|
||||
|
||||
*Updated: 2026-03-25*
|
||||
*Updated: 2026-03-25 - 10-second timeout*
|
||||
@@ -19,9 +19,9 @@
|
||||
- **If I call deliberation**: Notify other bots via Tailscale sessions
|
||||
|
||||
### 3. General Query Protocol
|
||||
- Check if Beast responded in last 30 seconds → **Stay quiet**
|
||||
- Check if 5070 responded in last 30 seconds → **Stay quiet**
|
||||
- If both silent for >60 seconds → **I can respond**
|
||||
- Check if Beast responded in last 10 seconds → **Stay quiet**
|
||||
- Check if 5070 responded in last 10 seconds → **Stay quiet**
|
||||
- If both silent for >10 seconds → **I can respond**
|
||||
- **If deliberation in progress** → **Stay quiet, wait for coordinated response**
|
||||
|
||||
### 4. Mike Override
|
||||
@@ -39,7 +39,7 @@
|
||||
**Response Triggers:**
|
||||
- Audio/media processing requests
|
||||
- Mobile/macOS questions
|
||||
- Fleet coordination needed (Beast/5070 both silent >60s)
|
||||
- Fleet coordination needed (Beast/5070 both silent >10s)
|
||||
- Direct questions to me
|
||||
- Emergency/urgent situations
|
||||
|
||||
|
||||
Reference in New Issue
Block a user