Useful automation has a verifiable outcome.

Follow the action to its destination

An internal success message may confirm that a request was sent without establishing what exists in the receiving system. A record identifier or destination readback can provide stronger evidence of the completed action. That evidence should remain connected to the original task.

The first step is to inspect one action that changes another system and define the available completion evidence. A missing receipt needs an explicit unresolved state and a reconciliation path. A later retry should consider the possibility that the original action succeeded.

Make evidence part of acceptance

A Production AI Lighthouse can test whether operators can verify results without reconstructing internal logs. Acceptance measures should separate attempts, confirmed outcomes, and unresolved actions. This distinction also makes cost per successful outcome more useful than cost per attempted request.