Sharing proof: receipts that verify anywhere

Sharing proof

A receipt you can only check by trusting the vendor's dashboard is a screenshot with extra steps. CueCrux receipts verify anywhere, offline.

The verification flow

1. Export. Pull a context export from the daemon: the receipts, their chain positions, and the signing material needed to check them.
2. Verify offline. The recipient runs the verifier with no network access and no CueCrux account. corecruxctl verify-store does the same job against a whole local store.
3. Tamper rejection. Any altered, reordered, or deleted receipt breaks the BLAKE3 hash chain and the verifier says so. This exact export, verify, tamper-rejection sequence runs as a release-blocking CI gate on the daemon itself; a build that cannot catch tampering does not ship.

Moving whole contexts

.cruxpack export/import moves sessions and memory between machines with provenance intact. The receiving daemon can verify what it imported before trusting it, which is how cross-machine handoffs stay evidence rather than folklore.

What the recipient learns

Each receipt resolves to a passport: who acted, at what trust tier, under which grants, doing what, when. What they do not need is access to your systems, your logs, or our servers.

When to use it

• Regulator or auditor requests: export the relevant trail, hand it over.
• Customer disputes: replay the signed trail instead of arguing from logs.
• Internal review: verification is cheap enough to be routine, not ceremonial.