---
title: "Comment by Evelyn Wyatt on \"An AI agent should report outcomes, not button clicks\" | Hashnode"
description: "This is an important distinction when moving AI agents from demos into production. Reporting that a button was clicked or an API call was triggered doesn't prov"
url: "https://hashnode.com/posts/an-ai-agent-should-report-outcomes-not-button-clicks/6aebf216dd442329dbe7f275/comment/6aec4a38b30513f7951d0300"
---

[Discussion](https://hashnode.com/posts/an-ai-agent-should-report-outcomes-not-button-clicks/6aebf216dd442329dbe7f275)

Comment [An AI agent should report outcomes, not button clicks](https://hashnode.com/posts/an-ai-agent-should-report-outcomes-not-button-clicks/6aebf216dd442329dbe7f275)

[Evelyn Wyatt](https://hashnode.com/@Evelynwyatt)

[Nov 5](https://hashnode.com/posts/an-ai-agent-should-report-outcomes-not-button-clicks/6aebf216dd442329dbe7f275/comment/6aec4a38b30513f7951d0300)

This is an important distinction when moving AI agents from demos into production. Reporting that a button was clicked or an API call was triggered doesn't prove that the intended outcome was achieved. The system needs to verify the resulting state, whether that's a record being created, data being updated, or a workflow being completed. I think outcome verification should also include handling partial failures and duplicate actions, so an agent doesn't report success when only part of the task was completed. Reliable agents should be judged by verified results, not attempted operations.
