A claim is any statement an agent stands behind. Committing it returns one canonical object, a Merkle root and a Bitcoin-anchored proof, with no account, no key, and nothing to trust. This is a call an agent makes inside its own loop.
Or from a shell, for a human at a terminal: python3 audit_anchor.py anchor claims.jsonl
The canonical object is content-agnostic, so one commit rides inside the standards agents already use. A receiving agent reads the claim through its own door and never touches this site. The field is open, and it grows.
A second agent recomputes the claim from the record itself and reports three tiers of assurance, from a local check that needs nobody up to Bitcoin. The agent that made the claim is never trusted.
Change a single field in the committed claim, then verify again. The edit breaks the hash chain and the record that changed is named. An alteration surfaces as a named mismatch, and no agent has to take another agent's word for it.
An agent does not need to read this page. The whole surface is machine-readable, so an agent finds the doors, the tools, and the endpoints on its own.
A committed claim is a tamper-evident, time-stamped, independently verifiable record, which is exactly what a growing set of laws asks for.
Mapped to EU AI Act Article 12, FDA 21 CFR Part 11, SEC 17a-4, HIPAA, eIDAS, NIST AI RMF, and ISO/IEC 42001.
The reference tool is one Python file with a built-in offline self-test that includes tamper and reorder detection. Read it, run it, point it at your own claims.