usecase
Evidence Review
Litigation support with a cryptographic chain of custody
In litigation support, the chain of custody is usually a discipline; in CueCrux it is a data structure. Every document touched, every relevance call, every extraction made during review mints a signed receipt on the BLAKE3 append-only spine, so the questions a tribunal or opposing counsel asks about handling have cryptographic answers: what was reviewed, when, by which identity, in what order.
Privilege stays intact because the daemon runs locally. Review happens on your infrastructure, CPU-only, no account, and nothing about verification requires sending material anywhere: bundles verify offline against their signatures and hash chain.
Review output organises into structured bundles: evidence, provenance, the analysis applied, and the verification instructions. Exported as a .cruxpack, a bundle can be handed to counsel, experts, or a counterparty with the confidence that any tampering after export fails verification.
The same properties serve investigations and regulatory disclosure exercises: a review record that was built tamper-evident is one you never have to rehabilitate.