My AI Agent Did Not Do What I Asked: Proof

Last updated: 2026-09-24

Short answer: When an AI agent did not do what you asked, compare the request with the recorded tool calls, observed results, and final state. A receipt can show whether the call ran and what it observed, while a read-back can show whether the intended outside change exists.

Last reviewed: 2026-09-23. This page describes a reviewable evidence pattern and does not claim an outside result without upstream confirmation.

Compare said and done

Put the original request, agent summary, receipt, and current system state side by side.

Find the boundary

Identify whether the issue was a missing call, invalid input, provider failure, blocked permission, or unconfirmed outcome.

Choose the next action

Retry only safe operations, ask for approval when needed, and preserve the failed record for review. Link the related said versus done guide.

Live verification example

Open a public execution receipt or call its verifier. The example reports verification_status: verified for the stored record. It is not proof of an unobserved external outcome.

Frequently asked questions

AI agent did not do what I asked proof

When an AI agent did not do what you asked, compare the request with the recorded tool calls, observed results, and final state. A receipt can show whether the call ran and what it observed, while a read-back can show whether the intended outside change exists.

What can a verifiable receipt prove?

It can show what the execution layer recorded and what its integrity checks verify. It cannot prove an unobserved outside outcome.

How can another reviewer check the record?

Open the public receipt, compare the tool, time, result, and status, then call the verifier. Keep outside confirmations separate from the execution record.