Modes & Decision Guide
CueCrux offers three trust modes. Pick the one that fits your task: speed when you just need an idea, depth when you need proof you can defend.
What Each Mode Guarantees
- Light
- Purpose: quick reading and exploration.
- Guarantees: basic provenance and citation hints; may not enforce independent domains.
- Typical latency: sub‑second to ~1.5 s.
- Typical cost: lowest (see Economy for details).
- Verified (recommended default)
- Purpose: everyday reliability for work products.
- Guarantees: provenance checks; QUORUM (MiSES) selects a minimal evidence set (MiSES) per claim; aims for ≥2 independent domains when available; freshness rules; contradiction surfacing.
- Typical latency: p95 ≤ ~2 s (k=10).
- Typical cost: 1 CRUX per answer (see Economy).
- Audit
- Purpose: high‑stakes proof (legal, regulatory, publication).
- Guarantees: deterministic replay; counterfactual lane; signed CROWN receipt required; no answer if integrity gates fail.
- Typical latency: ~2–4 s.
- Typical cost: 5 CRUX per run (see Economy).
When To Use Which (Quick Tree)
flowchart TD
A[What do you need?] --> B{Is this high‑stakes?
Legal, regulatory,
external publication}
B -- Yes --> AUDIT[Use AUDIT]
B -- No --> C{Do others rely on this?
Client, team,
published deliverable}
C -- Yes --> VER[Use VERIFIED]
C -- No --> D{Just exploring or drafting?}
D -- Yes --> LGT[Use LIGHT]
D -- No --> VER2[Use VERIFIED]
flowchart TD
A[What do you need?] --> B{Is this high‑stakes?
Legal, regulatory,
external publication}
B -- Yes --> AUDIT[Use AUDIT]
B -- No --> C{Do others rely on this?
Client, team,
published deliverable}
C -- Yes --> VER[Use VERIFIED]
C -- No --> D{Just exploring or drafting?}
D -- Yes --> LGT[Use LIGHT]
D -- No --> VER2[Use VERIFIED]
Tips
- You can always start Light → upgrade to Verified/Audit for the final draft.
- When topics are contentious or time‑sensitive, prefer Verified or Audit.
Examples
- Brainstorming ideas for a headline → Light.
- Slide deck for an internal meeting → Verified.
- Public whitepaper or regulator submission → Audit.
Common Pitfalls
- Expecting audit‑grade proof from Light mode upgrade to Verified/Audit.
- Using stale sources for time‑sensitive topics check freshness and Findings.
- Relying on a single domain when others exist Verified/Audit prefer diversity.
See Also
- Receipt Anatomy: verify proof in 30 seconds
- Trust Scoring: explainable signals behind the scenes
- Economy: CRUX and C³ budgets

