Stage 1 Path F: The Voice Mesh Protocol — Every Node Gets a Mouth and an Ear

> Grounded in: Stage 0 finding that 4 Mac machines exist in the mesh but only phones have voice I/O. The mesh nodes are deaf and mute. Don't centralize voice. Distribute it. Every node in the mesh (Mac1, Mac4, Mac5, cloud-vm) gets a microphone daemon (ear) and a TTS daemon (mouth). Inter-node voice happens over the existing NUMU/Mesh Event Bus. The mesh doesn't need a voice server — it needs voice as a native capability of every node, like networking. **4. Spatial Voice (multi-room):** If machines are in different rooms/locations: - Mac1 (office desk) = primary interaction point - Mac4 (server rack area) = status announcements only - Mac5 (beside Mac4) = paired with Mac4 for compute status - Each machine's TTS volume and frequency tuned to its physical context - Every machine becomes voice-interactive, not just the phone - Cross-machine voice relay enables "talk to Mac4 through Mac1" - Distributed voice means no single point of failure - Each node's voice daemon is independent — works offline for local commands - Builds on existing NUMU event bus and mesh architecture - Physical presence at any machine = voice access to entire mesh - Mac4 and Mac5 may not have microphones (headless compute nodes) - Audio hardware management across 4+ machines is complex - Echo/feedback loops if two machines are near each other (Mac4+Mac5 side by side) - Whisper model on every node = memory overhead per machine - NUMU event bus latency for voice relay (~50-200ms) adds to response time - No authentication for voice commands — anyone near a mic can issue commands (mitigate: speaker ID)