When an AI agent spends money, two artifacts exist. The first is the transaction: a hash on a chain, visible to anyone. The second is the decision to allow it β and when the decision was no , almost nobody keeps the second one.
Ask a team what their agent refused last month and you usually get a dashboard, a screenshot, or a log where every row says allowed . A dashboard is a claim made by the same system that is being questioned. That is why the interesting artifact is not the allow list. It is the refusal, written down in a form someone else can check.
What a refusal record has to contain
The record has to answer four questions without help from the service that produced it: what was asked, which policy decided, who asked, and can this file be changed after the fact.
{ "v" : 1 , "prev" : "<sha256 of the previous record>" , "ts" : "2026-10-29T09:14:02+00:00" , "decision" : "deny" , "reason" : "payee not in allowlist" , "policy_id" : "E03-allowlist" , "task_id" : "task_7f21" , "artifact_hash" :β¦