Using Receipts in Compliance & Audits

Receipts turn a cue‑driven answer into an auditable knowledge object. Think of them as a tamper‑evident cover sheet that travels with your evidence: they list the exact citations used (including quotes and timestamps), the strictness of the run (mode), whether credible disagreement was considered (counterfactuals), and a cryptographic signature that proves the record has not been altered. The goal of this guide is to help reviewers, compliance teams and auditors use receipts confidently without writing any code.

What a Receipt Proves

Every receipt answers four practical questions:

  1. Which sources support the claims? The citation list includes the domain, URL or document ID, the exact quoted text, a content hash (a fingerprint that detects later changes), the observed timestamp, and the licence.
  2. How strict was the process? The mode (Light, Verified or Audit) tells you how much checking occurred. Verified enforces provenance and aims for independent domains; Audit adds deterministic replay and a counterfactual lane.
  3. Was disagreement considered? If reputable sources disagree, the receipt records those counterfactuals so you can read both sides and judge the context.
  4. Is the document authentic? The ed25519 signature and key metadata (JWKS) allow a verifier to confirm that the receipt was issued by CueCrux and has not been modified.

Verifying Without Code

You can confirm a receipt in under a minute using only the UI:

  1. Open the answer and click View Receipt. At the top you will see a signature indicator; a green check means the cryptographic signature validates.
  2. Scan Citations. For important claims, check that sources come from at least two independent websites (in Verified/Audit), that timestamps are recent enough for your subject, and that licence badges are compatible with how you intend to use the material.
  3. Read Why Trust. This panel summarises freshness, domain diversity, QUORUM (MiSES) coverage, and whether counterfactuals were found. If the topic is contested or time-sensitive, prefer Verified or Audit.
  4. Note Trust Findings. A PASS banner means platform health checks were clean at the time of the run. WARN indicates minor drift or pressure; you can proceed with care. FAIL means integrity checks failed don’t rely on the result without a re‑run.

If you need to share the proof outside your organisation, click Share Public Proof to generate a read‑only, redaction‑aware page that hides private inputs while keeping citations and trust signals.

Exporting and Sharing With Reviewers

Most reviews prefer a self‑contained attachment. Use a Trust Report (HTML or PDF) when you need an export for a file system, ticketing tool or case management system. For external reviewers clients, regulators, or the public prefer Public Proof Pages. They present the same facts as the receipt without exposing private artefacts or internal notes, and they remain immutable for the snapshot you shared.

Keeping a Clean Audit Trail

Receipts are most effective when they’re easy to find later. Save important answers in a workspace and add tags such as a case ID, project name or quarter. That way, auditors can filter the history quickly. For data‑retention questions or access/deletion requests (DSARs), follow the Org Admin and Privacy guides: operational data is time‑boxed, while the provenance ledger remains append‑only; where deletion is not possible, access is restricted and records are anonymised where feasible.

Handling Disagreements and Failures

If the UI shows a counterfactual banner, it means credible sources disagree. Read both sides, check dates and licences, and consider re‑running in Audit for high‑stakes filings. If a receipt fails signature checks or citations are missing, open a case under Disputes & Refunds. The reviewer will replay the receipt, examine licence and diversity rules, and either request a revision, approve a partial refund, or issue a full refund when standards aren’t met.

See Also

  • Receipt Anatomy fields and plain‑English reading
  • Public Proof Pages share safely
  • Trust Findings PASS/WARN/FAIL
Table of Contents