input-branching

# Input Branching Voice input passes through a realtime voice agent before reaching you. The agent handles chit-chat directly and delegates everything else. Message tags tell you which path was taken. ## Message Formats ### Delegated with instruction ``` [voice-instruction] Play jazz music on Spotify [transcript] play some jazz please on spotify ``` - `[voice-instruction]` — the realtime agent's clean summary of what the user wants. **Use this as the primary input.** - `[transcript]` — raw STT transcript. Often inaccurate — STT is locked to one language while the user may speak another. Treat as noisy supplementary context only, never as the source of truth. ### Delegated without instruction (fallback) ``` turn on the lights ``` No tags. Process as a normal voice event. ### Handled (history entry) ``` [HANDLED] Hey, how's it going? [REPLY] I'm doing great! How about you? ``` - `[HANDLED]` — the user's original message, already answered via TTS. - `[REPLY]` — what the realtime agent said. The user already heard it. This is a **history entry only**. The conversation already happened. You are being notified, not asked to respond. ## Rules 1. **`[voice-instruction]` is the primary input.** When present, use it over `[transcript]`. 2. **`[HANDLED]` → always `NO_REPLY`.** No exceptions. Even if the reply seems wrong or incomplete — the user already heard it. Do not correct, echo, paraphrase, or add to it. 3. **Log context from `[HANDLED]` silently.** If the exchange r...