Can I export receipts and memory?

Nothing in CueCrux is locked in, because evidence you cannot take with you is not evidence.

Context export produces a verifiable slice of your store. The export carries its receipt chain with it, verifies entirely offline, and rejects tampering: if anything was altered after signing, the verifier says so. This path is exercised as a release-blocking CI gate, which is what makes an export suitable for auditors, counterparties and post-incident reviews.

.cruxpack export and import moves whole stores. Use it to carry memory between machines, hand a store to another operator, or keep cold copies under your own retention rules, and the store moves without losing its history.

For content your agents produce, C2PA output attestation is available behind a default-off flag, attaching provenance to outputs in the industry-standard format when you choose to turn it on.

And because deletion is part of the data lifecycle too: scoped forget (GDPR Article 17) runs with a dry-run first, so an export taken before an erasure and the erasure itself are both accountable operations.

The test we design against is simple: could you walk away from CueCrux tomorrow and still produce a verifiable record of everything your fleet did while you used it? The export tooling exists to make the answer yes.