Stage 2: Compound Architecture — Voice-First Agent Architecture

**Decision:** Path A's Mac Ear is the entry point — you need to be able to talk to the mesh from the desk. But Path C's unified router is needed immediately because we don't want a third intent classifier (Mac) alongside iOS VoiceRouter and FleetVoiceRouter. Build the server-side router first, then point the Mac Ear at it. **Client migration path:** - Phase 1: Mac Ear uses unified router directly - Phase 2: OpenClawHub switches from local VoiceRouter/FleetVoiceRouter to HTTP POST - Phase 3: SpeakFlow switches from local VoiceCommandService to HTTP POST - Phase 4: Decommission client-side classifiers (keep as offline fallback) **Decision:** Path B's spoken mesh is essential for bidirectional voice. After Step 1 gives the mesh an ear, it needs a mouth. But Path B's approach of subscribing to ALL events is too noisy. Use a priority filter. **Mute/unmute via voice:** - "Quiet" / "mute" → suppresses normal+low events - "Unmute" / "speak" → resumes - Critical events always spoken regardless of mute state - "What did I miss?" → summarize suppressed events **Decision:** Path D's voice transcript persistence is critical for the mesh's memory model. Voice is currently the only interaction channel that isn't persisted. This creates a gap in the knowledge graph.