QUEUEPROOF
How QueueProof reached the answer

Search every source.
Show every receipt.

QueueProof does not ask you to trust an unexplained answer. It records the route, the HydraDB calls, the retained evidence, the conflicts, and the exact basis for the next action.

Run the proof Inspect measured results
01

Verify the sources

A source counts only after HydraDB returns attributable records and QueueProof stores the proof receipt.

02

Choose the route

Direct facts use Quick. Cross-source, timeline, conflict, and changed-information questions use Investigate.

03

Search and follow the evidence

Investigate preserves a Quick grounded baseline, then uses identifiers from those results for one bounded follow-up search.

04

Compare the proof

QueueProof matches people and projects, orders dated records, preserves conflicts, and ignores instruction-shaped source text.

05

Cite or abstain

Every supported claim opens to a receipt. Missing proof produces a partial result or an explicit abstention.

06

Recommend the next safe action

The action is linked to evidence, ranked by a versioned policy, and any external write remains approval-gated.

QueueProof can say

  • Verified, with supporting receipts.
  • Contradicted, with the disagreement preserved.
  • Partially verified, with the missing facts named.

QueueProof refuses to say

  • A source is healthy without a real record check.
  • A claim is supported when its citation cannot resolve.
  • An external action happened without a provider response receipt.
One reproducible receipt

Mode · route reason · filters · calls · latency · evidence · relative cost

Fixture, live connector, and large-PDF measurements stay separate so a deterministic router score cannot be mistaken for live retrieval accuracy.