Verification profiles

The public rules Open Verifier uses to recognize, parse, and locally verify human-presentation receipts, machine-qualification bundles, and consequence-control projections.

Human-presentation receipt profile

Supported formatsVC JSON, VC-JWT, Compact JWT, Local W3C Package, and Raw Technical JSON.

Core fieldsIntent, evidence manifest, authorization claim, timestamp, proof, receipt ID, issuer, and chain metadata.

Verification checksParse, profile validation, digest comparison, signature verification, chain inspection, and signer-policy attribution where available.

Signature profileP-256 / ES256 when the receipt discloses the public key, signature, and signed-payload digest.

Privacy modelBrowser-local. No account, upload, storage, or backend call.

Machine-qualification profile

InputA complete qualification bundle plus supplied relying-party context, expected request bindings, and trust pins.

DecisionQUALIFIED, NOT_QUALIFIED, or INDETERMINATE.

ChecksCandidate match, DSSE signatures, campaign graph, assignment scope, protected-request binding, runtime measurement, status head, and currentness.

Trust boundaryThe verifier evaluates the supplied context; the input file does not establish that context's provenance or grant execution authority.

Consequence-control projection profile

Projection checksSignature under a verifier-pinned fixture signer, typed CAID/action bytes, exact referenced SYNC receipt bytes, provider/effect evidence, duplicate lineage, lifecycle order, and retry safety.

Projection boundaryA verifier-side interoperability projection, not a canonical source-system record, journal, provider-outcome object, effect-relation object, or proof of durable global single-use state.

Outcome vocabularySETTLED, DUPLICATE_REFUSED, INDETERMINATE, and DIVERGENT are projection summaries, not execution commands.

Presentation and action-binding boundary

This build verifies what a SYNC receipt records as presented for review. It does not independently observe the screen or verify a deterministic renderer or display attestation.

In a consequence-control projection, a matching SYNC receipt-byte digest proves which exact receipt is referenced. It does not prove that the receipt itself carries or displayed the same typed CAID/action.

Compatibility identifiers

Protocol-specific profile names, media types, predicates, and key identifiers are preserved only when they are part of the canonical or signed bytes being tested.

Those identifiers are technical metadata, not a public endorsement or partnership claim. Compatibility does not imply sponsorship, joint publication, or that Open Verifier's projections are canonical production exports from the source system.

Recognition is not trust by itself

A document can match a known profile without being accepted as authentic. Open Verifier separates profile recognition, hash checks, signature verification, signer-policy acceptance, ceremony claims, organizational authority, execution, and outcome so reviewers can see exactly what passed.

Explore the sample outcomes