Verifier quickstart

link to this sectionVerifier quickstart

Verification produces a signed receipt with typed findings. The receipt records what you observed; it never collapses into a truth score.

link to this section1. Pick a claim and a context mode

A verification declares its context mode - for example, whether you saw the statement only (blind) or the full evidence set. Blind verification is the default path the work queue offers; it is what makes independent receipts comparable.

link to this section2. Reproduce and observe

Run the artifacts, rerun the baseline, or probe the methods, and record what happened. The receipt captures verification types (such as blind or replication), the context mode, and the implementation and data relations you declared.

link to this section3. File findings with severities

Findings carry a severity (critical, major, warning, note), a title, and a description. Findings are evidence of what you saw. A receipt with a supports outcome can still carry a critical finding - the outcome says what you observed overall, the findings say what needs attention.

link to this section4. Sign and publish

The receipt is signed and appended to the event chain with a stable id. From the claim page, the status rail groups receipts by outcome and lists the highest open finding - as navigation, never as a score.

link to this sectionNext steps

• Verification and receipts for the fielded receipt contract.
• Challenge a claim when an observation should become an adversarial process.
• Inspect provenance for dependency taint and frontier snapshots.