Voice Truth Guard — Decision

PROPOSED — PENDING FEDE'S PICK

How to stop Clara asserting things on phone calls that didn't happen ("You're all set — tour rescheduled" for a pending, conflicted slot — the Aug 22 Camellia incident), without paying for it in dead air. Commissioned by Fede 2026-08-22. Standing rule: nothing voice-related merges without his explicit approval.

The evidence (all measured, none estimated)

The options

ATruthful tools + no-talking-during-toolsRECOMMENDED+15 ms worst-case

Three zero-latency pieces shipped together:

Limit acknowledged: this constrains what the model is told, it doesn't inspect what it says. The detector is the accountability layer. Industry note: no vendor documents the tool-dictated-sentence pattern — this is novel work, not borrowed practice.

BOption A + pilot ElevenLabs Guardrails 2.0 as a second layer+200–500 ms (their number)

ElevenLabs' new (alpha) guardrail can run a custom natural-language rule over each reply before audio plays — the only true pre-speech hook they offer. Blocking mode costs 200–500 ms per their docs; its only remediations are retry or end-call. Worth piloting behind Option A on a test line, never as the only defense — alpha status and semantic (a second model's judgment, not deterministic).

COwn the model boundary (platform change)~846 ms measured for verify-before-speak

Host the LLM call ourselves and hand ElevenLabs only the voice — the architecture where real interception and mid-stream correction become possible (how LiveKit/OpenAI Realtime do it; even they admit some audio can escape). Big migration, and the measured cost of a verify step (~0.85 s) eats the latency budget. Park as the long-term conversation, incl. a feature request to ElevenLabs for a deeper hook.

DDetection only (status quo + wider detector)0 ms

Keep speaking from ambiguous tool results and catch lies after the call. Rejected as the primary answer: the 20/20 result shows the caller hears the lie every time the state is ambiguous — and we now know a 0-latency prevention exists.

Your pick

ChoiceWhat shipsLatency cost
A (recommended)Truthful tool wording + no-talk-during-tools + wider detector≤ 28 ms
BA, plus a Guardrails 2.0 pilot on a test lineA + 200–500 ms on the piloted line only
CScope the platform-boundary migration as its own projectn/a (design phase)
DNothing preventive0

All artifacts: wording eval (merged), latency prototype PR #6114 (held), research catalog in the session record. Whatever the pick, every voice change stays merge-held for Fede's explicit approval. Related fix already correcting the design record: the turn-integrity architecture note assumed a pre-speech buffer voice cannot have on this platform.

PropFlow Docs