# Receipts Over Claims

> A working posture: prove it with an artifact, then say it. Evidence beats assertion every time.

Category: observability

Receipts over claims is a default posture: an assertion is only as good as the artifact attached to it.

## Why it matters
Teams ship narrative. "Our agents are safe." "It works in prod." Nobody can check any of it. The posture flips the default: a claim with no receipt is a rumor. A claim with a trace, an eval score, or a signed artifact is a fact you can hand to someone who does not trust you.

## In practice
Every assertion of safety, quality, or completion ships with something linkable: a trace, a passing check, a runtime receipt, a deploy. No artifact, no claim. The burden sits on the one making the claim, not the one doubting it.

## Where it shows up in my work
This is the spine of governable-ai and the principle agentic-u states directly. The decision certificates on this site are receipts for the site itself.

---
Source: https://ryanhunter.io/lexicon/receipts-over-claims
Part of the Agent Infrastructure Lexicon by Ryan Hunter. https://ryanhunter.io/lexicon