explorer
What does the audit trail look like?
Receipts are the log: signed, hash-chained, tamper-evident
corecruxctl verify-store --mode full --strict ok: true · 4 receipts · chain intact
Signatures bind to both the receipt id and the payload hash, so a receipt cannot be edited in place or transplanted elsewhere; ordering is carried by chained segment seals on the spine. You can run this exact experiment on your own machine: scripts/demo-receipt-tamper.sh in the Crux repo.
Most platforms bolt an audit log onto the side of the system and hope the two never disagree. CueCrux removes the gap: the receipts that record agent activity are the audit trail. There is no second, weaker copy to reconcile or to doubt.
Every state mutation the daemon performs is signed as a CROWN receipt using Ed25519, and receipts are hash-chained on a BLAKE3 append-only spine. The chain structure is what makes the trail trustworthy. Alter a record and its hash no longer matches; remove one and the chain visibly breaks; insert one and the sequence fails verification. You do not audit this log by trusting whoever operates it. You audit it by checking the maths.
Attribution is built into every entry. Because all writes are bound to passports, any receipt resolves back to who acted, at what trust tier, under which grants. Refused actions appear too: RCX denials produce signed RefusalReceipts with reason codes, so the trail records not only what agents did but what they were prevented from doing.
Verification is offline and independent. corecruxctl verify-store checks a store's chain end to end on any machine, and the export-verify-tamper-rejection path is a release-blocking CI gate on the daemon, tested on every release. An external auditor can take an exported pack and validate it without touching your infrastructure.
This is also the substance behind CueCrux's EU AI Act positioning: the hash-chained record-keeping, oversight and transparency machinery that the Act's Articles 9, 10, 12, 13, 14, 15 and 50 contemplate is the same machinery everything runs on daily, not a parallel compliance system switched on for inspections. Even deletion respects the trail: scoped forget removes data under GDPR Article 17 while leaving a receipted record that the removal happened.