Can I share proof of what my agents did?

Yes, and the person you share it with does not need CueCrux, an account, or a network connection to check it.

The unit of sharing is a context export. Export the relevant slice of your store, hand it over, and the recipient verifies the receipt chain offline. If anything in the export was altered after signing, verification rejects it. That export, verify, tamper-rejection path is exercised as a release-blocking CI gate, so it is not a marketing diagram; it is a tested property of every release.

What the recipient can establish is precise. Each CROWN receipt resolves to who acted, at what trust tier, under which grants, and the hash chain establishes order and completeness: nothing inserted, nothing removed. Refusals appear as signed RefusalReceipts with reason codes, so the record covers denied actions as well as executed ones.

For moving whole stores rather than proving a slice, .cruxpack export and import carries memory between machines and sessions. For content your agents produce, C2PA output attestation is available behind a default-off flag.

The practical use cases are the unglamorous ones: an auditor who wants evidence rather than screenshots, a customer dispute about what an agent changed, a post-incident review where the timeline must be beyond argument. In each case you hand over signed records, not a narrative.