Disputes & Refunds (MVP)

This guide explains how to raise a dispute when a deliverable or proof looks wrong, how CueCrux reviews the case, and what outcomes are available. It applies to evidence‑backed deliverables and trust reports produced through verified or audit modes.

What Qualifies

  • Missing sources: promised citations absent, or evidence does not cover the stated claims.
  • Failed receipts: CROWN receipt cannot be replayed, signatures don’t verify, or artefact hashes don’t match.
  • Out‑of‑scope: deliverable clearly ignores the agreed scope (e.g., wrong jurisdiction or timeframe).
  • Policy breaches: licence violations, personal data exposure, or prohibited sources.

Issues of tone, formatting, or preferences are treated as revision requests rather than disputes.

How Reviews Work

  1. Open a ticket (SupportCrux or in‑app) and attach the receipt ID and a short description.
  2. Automatic checks run first: receipt verification, QUORUM (MiSES) coverage check, licence status, Findings state.
  3. Operator review (WatchCrux/OpsCrux) examines contradictions, domain diversity, and freshness.
  4. A decision is issued with a written rationale and links to verification artefacts.

We aim to complete most reviews within 5–7 business days; urgent safety or policy cases may be prioritised.

Outcomes

  • Revision (preferred): the originator corrects sources or scope and re‑submits with a new receipt.
  • Partial refund: where a portion of work is valid but not all claims are supported.
  • Full refund: when receipts fail, sources are missing, or policy violations are confirmed.
  • Dismissed: if the deliverable verifies and matches scope; guidance is provided.

All outcomes include a dispute receipt that records checks performed and the final decision.

Tips to Avoid Disputes

  • Use verified or audit mode for high‑stakes work.
  • Include at least two independent domains when available.
  • Prefer primary sources; flag counterfactuals clearly.
  • Keep scope precise (jurisdiction, dates, definitions) in your request.

If you need help verifying a receipt locally, see the “Receipt Anatomy” guide.

Table of Contents