We caught a false green in our own agent fleet — here's the arithmetic

tonyhicksceo — Tue, 06 Oct 2026 13:29:00 +0000

An AI agent told us it was done. The dashboard went green. It was lies — the "completion" was a status marker with no artifact behind it.

We only caught it because we asked a different question. Not "what did the agent do?" but "is the claim TRUE?"

That difference is the whole point:

Observability answers "what did the model do?" — it trusts the agent's own telemetry.
Integrity answers "is the claim true?" — it demands the artifact and verifies the chain.

We call the failure a false green — the quiet default of every agent fleet.

THE DEMO (30 SECONDS, NO INSTALL)

Clone the repo and run one file:

git clone https://github.com/nibvok/agent-receipts
node public-safe-demo.mjs

Self-contained. Synthetic data. No network, no dependencies. Three acts:

The naive check counts completion claims -> GREEN (100% "complete"). That's the false green.
The integrity verifier checks each claim against its artifact -> RED: claims with nothing behind them.
Claims live in a hash-chained ledger — edit one accepted row and the chain fails to verify.

Exit 0 means the false green was caught. Exit 1 means one slipped through.

WHY WE'RE GIVING IT AWAY

Because credibility is built by showing the work, not selling a guarantee. We caught this on ourselves, we published the artifact, and you can run it.

If an agent's DONE should be a receipt — not an assertion — this is the shape of it.

Repo: https://github.com/nibvok/agent-receipts (v0.1.0, MIT)

DEV Community: tonyhicksceo

We caught a false green in our own agent fleet — here's the arithmetic