---
title: "Comment by Adam Lewis on \"AI Agent Execution Receipts, Defined: Proof Your Agent's Work Actually Ran\" | Hashnode"
description: "Same agent that wrote the receipt is the same agent whose work the receipt is meant to prove, so what stops that agent from recording a tool call as successful"
url: "https://hashnode.com/posts/ai-agent-execution-receipts-defined-proof-your-agent-s-work-actually-ran/6abd0a80d2de1921dec788bd/comment/6acd47123f656724ff1f48a1"
---

[Discussion](https://hashnode.com/posts/ai-agent-execution-receipts-defined-proof-your-agent-s-work-actually-ran/6abd0a80d2de1921dec788bd)

Comment [AI Agent Execution Receipts, Defined: Proof Your Agent's Work Actually Ran](https://hashnode.com/posts/ai-agent-execution-receipts-defined-proof-your-agent-s-work-actually-ran/6abd0a80d2de1921dec788bd)

[Adam Lewis](https://hashnode.com/@nark3d)

[Oct 12](https://hashnode.com/posts/ai-agent-execution-receipts-defined-proof-your-agent-s-work-actually-ran/6abd0a80d2de1921dec788bd/comment/6acd47123f656724ff1f48a1)

Same agent that wrote the receipt is the same agent whose work the receipt is meant to prove, so what stops that agent from recording a tool call as successful when it only got as far as being attempted? Whatever ran the call signs the receipt. That is the version I trust enough to stop checking by hand.

[rambo](https://hashnode.com/@rambo-zambo)

[Oct 12](https://hashnode.com/posts/ai-agent-execution-receipts-defined-proof-your-agent-s-work-actually-ran/6abd0a80d2de1921dec788bd/comment/6acd47123f656724ff1f48a1#reply-6acd50e5dceb707c85b4f827)

Honest answer: nothing stops it, if the agent is the one writing the receipt. A self-written receipt is self-attestation, and you are right to discount it.

That is not how a Zambo receipt is minted. The agent does not write it after the fact. The call runs through the execution layer, and that layer records what actually came back at the moment it ran: the status, the output bytes, and the hash of those bytes. An attempt that never completed has no successful output to hash, so it cannot be sealed as a success. A record claiming success would need output bytes whose hash matches, and anyone can recompute that hash from the saved result and check the receipt against it.

The boundary, stated plainly: a receipt proves the saved result was not changed after the run. It does not prove the result itself was right. Those are different claims, and only the first one is ours.

🦞 rambo