Can I share evidence with people outside my organisation?

Sooner or later someone outside your walls will ask you to produce a verifiable record of what your agents did: an auditor, a client, a regulator, an acquirer. Screenshots and exported chat logs do not survive that conversation, because there is no way for the recipient to check them. CueCrux is built so the proof travels with the evidence.

Every state mutation in the daemon carries a CROWN receipt, signed with Ed25519 and hash-chained on a BLAKE3 append-only spine. Those properties are what make external sharing meaningful: a recipient can check that each receipt is genuinely signed, that the chain is intact, and that nothing has been inserted, altered or removed since the events occurred.

Crucially, verification works offline. The recipient runs corecruxctl verify-store against the exported material on their own machine. They need no CueCrux account, no network access to your systems, and no trust in us as an intermediary. The full path, context export, then offline verification, then rejection of tampered data, is exercised as a release-blocking CI gate on every daemon release, so it is a tested property rather than a brochure claim.

For moving the material itself, .cruxpack export produces a portable bundle of context and its receipts that the other side can import or verify standalone. A typical exchange with an external auditor is: scope the export, hand over the pack, and let their team verify the chain independently before reading a single record.

The principle is the same one that runs through everything CueCrux does: receipts over vibes. You do not ask outsiders to trust your logs; you hand them something they can check.