Know Your AgenticAI

The evidence layer that sits under an agent platform. A platform decides what an agent may do. This is the record of what it tried and was refused, sealed so the other side can check it without trusting whoever ran the agent.

Has this record been edited?

A receipts file is the record of every action an agent attempted: the ones that went through and the ones a rule stopped. A disclosure is the same record with the refusals shown and the rest held back, which is what you hand a regulator. Drop either below. It is read in your browser: nothing is uploaded, nothing is stored, and this works with no internet connection at all.

No file? See what the answer looks like:
Where did this file come from?

Every seal verifying proves nothing was edited. It does not prove this file came from anybody — a wholly forged chain verifies just as green, and that is a property of a hash chain, not a fault in this page. Only the ledger settles origin, and this page is deliberately offline.

So do the comparison here. Ask anyone with Canton access to run python3 tests/devnet_anchor.py --check, and paste what it prints into the box. This page will tell you whether the ledger is holding this chain.

This file's chain head, receipts
Not checked. On its own, this file is only self-consistent.
And whether it should have been allowed at all

A verifying chain proves the record is intact. It does not say whether this agent may hold a wallet, what it is permitted to decide without a human, or who answers when it spends on the wrong thing. That is a judgement, and somebody has to sign and date it.

This page, the format and the library stay free: a record you have to pay to read is a record you cannot check. The assessment is the paid part — rumedominic.com/assurance.

Demo honesty: scripted replay of a real agent run. Every receipt names the ledger that produced it — real DevNet or MOCKED — and that label is inside the seal. Works fully offline.
K
Operatormandate active · float 5 CC
✓
✓
✓
Mandate checkedEnforced on ledgerReceipt sealed

Principal's Statement · read from anywhere

Every payout the operator attempted, and the rule that allowed or refused it.

receipts: 0
The mandate: float ≤ 5 CC · only VerifiedRecipient & SettlementPartner · expires · principal may revoke from anywhere, any time · all four enforced in the Daml choice body, not in Python.
Why the rule lives in Daml, not Python. A cap in your backend is the operator checking itself — edit the file, or talk the operator past its own check, and the float is gone. A cap in the Daml choice body is checked by Canton before the transaction can exist. There is nothing to roll back and nothing to detect afterwards, because the spend never happens. The operator cannot skip it: it tried to raise its own cap and the ledger answered “missing authorization from owner”.