playbooklisted

# Building a SuperDialog Playbook A playbook is a Director+Talker voice-agent script: the **Director** (usually a fast/cheap LLM) reads the transcript each turn and decides whether to advance to a new checkpoint or fire an interrupt; the **Talker** (usually a stronger LLM) speaks based on whatever checkpoint the Director landed on. Almost every hard bug in a playbook traces back to one specific thing being left to Director/Talker *judgment* when it should have been made *structural* — a real slot, a real `judge: expr` rule, or a real code-side guard. This skill exists because that lesson kept getting relearned the hard way across three production playbooks — a slot-booking agent, a high-value-item sales agent, and a programme-enrolment agent — before it got written down here. That claim now has a number behind it. A later campaign against two of those playbooks — 5 production incident traces, 3 ratified call transcripts, ~20 live eval runs with assertions grounded in real API payloads — produced ~45 fixes. Split by mechanism: deterministic renders, deterministic guards, routing completeness and *deleting* example values from instructions held every time. Prose rules of the form "never invent a price" went **0 for 8**, twice being violated in the same paragraph that forbade the behaviour. Reach for prose last; if a number matters, the engine must speak it. See `references/grounding.md`. ## Before writing anything: read the real schema Don't guess field names. Read `referen