Stage 1 Path B: The Spoken Mesh — Agents That Talk Back

> Grounded in: Stage 0 finding that agents return results as text to Discord/terminal. No mesh-level TTS exists. The mesh is mute. A voice-first architecture isn't just about listening — it's about speaking. When a Prefect flow completes, when a pane finishes a pulse task, when Evolution World triggers a mutation, when a security alert fires — these events should be spoken aloud. Not all of them. The critical ones. The mesh should have a voice. **2. Priority and Suppression:** - Critical events (security, build failure, absorbing panes) always spoken - Normal events spoken only when no active voice conversation - Suppress during "focus mode" (user says "quiet" or "mute mesh") - Rate limiting: max 1 spoken event per 30 seconds for non-critical - Queue events during suppression, summarize when un-muted: "While you were focused, 3 builds completed and 1 flow failed" **3. Voice Personality:** - ElevenLabs voice ID already configured: `TmSgyk1vGAD9YzdtJV3V` - Consistent voice across all mesh announcements - Tone varies by severity: neutral for status, urgent cadence for alerts - Optional: different voices for different subsystems (infra = deep voice, creative = lighter) **4. Spatial Audio (future):** - Mac speakers can do stereo positioning - Left speaker = build/deploy events, right speaker = creative/content events - Or: volume correlates with priority (whisper for info, full volume for critical)