Back to docs

Verifier architecture

This is the public verification pipeline: what Proof of Ship checks, in what order, and what each verification depth means.

Pipeline overview

Input envelope
  -> schema validation
  -> dedup / idempotency check
  -> identity binding
  -> artifact existence check
  -> repository visibility + permission check
  -> cryptographic evidence check
  -> final verification result

Stages 1–2

Schema validation and dedup protect machine readability and idempotency.

Stages 3–4

Identity binding and artifact existence confirm the actor and public artifact are coherent and real.

Stage 5

Repository visibility and permission checks keep random public artifacts from earning someone else reputation.

Stage 6

Cryptographic evidence raises confidence beyond simple artifact existence.

Public depth tiers

  • 0.0 — Not verified
  • 0.2 — Schema valid
  • 0.4 — Artifact confirmed
  • 0.6 — Cryptographically signed
  • 0.8 — Independently attested (reserved)
  • 1.0 — Maximum assurance (reserved)