Skip to content
AX Framework
Principle 06

Verifiable Outcomes

Every action should return evidence of what it did, and that evidence should be independently checkable later.

Why it matters

An agent that reports "Done" to a person is making a claim. Verifiable outcomes let that claim be backed by a receipt the person, the agent, or a third party can check.

Verification also catches silent failures, such as a payment that was authorized but never captured.

Examples

Good exampleIllustrative

A booking action returns a receipt with a confirmation number, the exact itinerary booked, the amount charged, and a URL to retrieve the booking.

json
{
  "status": "completed",
  "receipt": {
    "id": "rcpt_77a1",
    "action": "create_booking",
    "resource": "/bookings/BK-55210",
    "charged": { "amount": 412.00, "currency": "USD" },
    "verifyAt": "/receipts/rcpt_77a1"
  }
}
Bad exampleIllustrative

Success is signalled by redirecting to a thank-you page with no order number and no way to look the order up later.

Implementation guidance

  1. 1Return identifiers for everything an action creates or changes.
  2. 2Distinguish accepted, completed, and failed in the response itself.
  3. 3Persist receipts so they can be retrieved after the session ends.

Evaluation criteria

  • Every state-changing action returns a structured receipt.
  • Receipts can be retrieved by ID.
  • Partial success is reported per item, not summarized.