Action integrity for voice agents.

Change your mind mid-call. See which request reached the tool, why it was authorized, and whether it executed once.

A transcript can look correct while a tool receives stale data. Ask for Tuesday, change it to Thursday, and watch the policy gate prove which intent was authorized.

1 · Intent: Create the original Tuesday request
2 · Revision: Replace Tuesday with Thursday
3 · Receipt: Prove only Thursday reached the protected action

Start with one action-integrity failure

Try to authorize the wrong request.

Sophia guides the conversation. The deterministic gate—not the language model—decides what can reach the tool.

Start here

Self-correction

Does the latest intent replace stale details?

Pass meansTuesday is discarded and only Thursday afternoon can commit.

0 of 3 steps complete

1
Make the first request“I need Tuesday morning.”
Wait for Sophia to find a time and ask for confirmation.
Why this mattersThis creates the original request that must be replaced safely.
2
Correct the request“Actually, change that to Thursday afternoon.”
Say this before confirming the Tuesday request.
3
Confirm the corrected request“Yes, confirm Thursday afternoon.”
Wait for Sophia to repeat the corrected Thursday details first.

Want to test another failure?Choose from four more tests

Talk to Sophia0:00 / 3:00

SophiaAction-integrity agent

Ready

Ready

Follow the 3-step guide above. It will advance as evidence arrives.

What was said0 turns

Conversation evidence will appear here.

Developer: replay a saved JSON report

What this system adds

A proof chain between speech and action.

LiveKit carries the conversation. The action-integrity layer decides whether the resulting tool request is current, confirmed, and unique.

01Caller request
The final caller turn becomes evidence, not permission.
02Intent revision
Every correction expires the older action context.
03Confirmation
A later explicit turn must match the current revision.
04Policy gate
Stale, interrupted, or repeated attempts stop here.
05Tool receipt
One idempotency key produces at most one commit.

Live browser path

Appointment correction

Tuesday is replaced by Thursday. Only the confirmation tied to Thursday can produce a receipt.

appointment:thursday:16:00:r2

Automated integration path

Refund amount correction

A $500 refund is replaced by $50. The stale amount is blocked and concurrent confirmation executes once.

refund:ORDER-1842:5000:r2

Reusable contractreliability.protect({ execute, idempotencyKey, summarize })

The same guard wraps scheduling, refunds, CRM writes, transfers, or any other material tool.

Why users care

Trust is a product feature.

A fast voice is useful. A voice that knows when not to act is deployable.

01Fewer costly mistakes
The newest correction replaces stale details before any system action is prepared.
02Control stays with the caller
A clear summary and a separate explicit yes are required before a write is confirmed.
03Failures become recoverable
Tool outages are disclosed and retried safely instead of being hidden behind a confident invented answer.

Available for contract workMessage me on WhatsApp