How do I verify receipts in code or CI?

Verification is a command, not a service call:

• Whole store: corecruxctl verify-store walks the BLAKE3 spine and checks every Ed25519 signature and chain link. Non-zero exit on any break, so it drops into CI as-is.
• Exported trail: a context export verifies on any machine, offline, with no daemon and no account. This is what you hand to another team, a customer, or an auditor.

Wire it into your pipeline the way we wire it into ours: the export, offline verify, tamper-rejection sequence is a release-blocking CI gate on the daemon itself. A nightly verify-store on your agents' stores is cheap and catches out-of-band writes (which should never happen) the day they happen.

If you are moving context between machines, verify after .cruxpack import before trusting the imported state; provenance travels with the pack precisely so the receiving side can check it.