Specification
Verification profiles
Public rules for locally verifying supported authorization receipts, exact-action continuity bundles, compatibility projections, and qualification bundles.
Supported receipt profile
Supported formatsVC JSON, VC-JWT, Compact JWT, Local W3C Package, Raw Technical JSON.
Core fieldsIntent, evidence manifest, authorization, timestamp, proof, receipt ID, issuer, and chain metadata.
Verification checksParse, profile validation, digest comparison, signature verification, chain inspection, and signer-policy attribution where available.
Privacy modelBrowser-local. No account, upload, or verification backend.
Exact-action continuity
For the narrow OPENVERIFIER-EXACT-ACTION-BINDING-v1 profile, OpenVerifier checks whether the material action protected by a human-reviewed SYNC full VC JSON receipt is the same typed action represented by the signed Gate compatibility projection.
Trust contextA separate relying-party context must be loaded first. Signer pins are not accepted from the bundle itself.
Human-side proofNative SYNC seal, explicit signer acceptance, designated sealed review packet, exact packet bytes and signed review intent.
Action identityRecomputed CAID and digest over the pinned
payment.release.1 material schema, including the closed packaged ISO 4217 alpha-3 pin.Machine-side joinThe signed Gate compatibility projection must reference the exact original SYNC receipt bytes and agree on action, tenant, operation and authority scope.
Positive result
MATCH / VERIFIED means the supplied human-side and machine-side evidence denote the same exact action under the supplied policy.Not establishedExecution authorization by OpenVerifier, provider invocation, settlement, physical effect, human comprehension, civil identity, or global replay state.
Exact-action input modes
Single bundle
OPENVERIFIER-EXACT-ACTION-BINDING-v1 with one signed Gate projection and one canonical reviewed-action packet. The exact SYNC receipt bytes are carried inside the signed projection attachment.Batch
OPENVERIFIER-EXACT-ACTION-BATCH-v1 evaluates multiple bindings and refuses colliding positive entries for the same protected native seal or operation within the supplied batch.Full VC requiredReceipt-only VC-JWT, compact JWT, raw technical JSON and Local W3C viewers do not silently inherit the exact-action assessment.
Machine-side profiles
OpenVerifier compatibility projectionChecks a signed verifier-side projection under a verifier-pinned signer; verifies typed action bytes, exact attached receipt bytes, separate provider/effect evidence, duplicate lineage, lifecycle ordering and retry safety without claiming canonical native Gate state.
Standalone projection boundaryA standalone projection intentionally does not establish the extra human ↔ machine exact-action continuity join; supply the complete exact-action bundle for that assessment.
Gate Qualification v2Checks the complete supplied qualification bundle against independently supplied trust pins and request context. Qualification does not authorize execution.
Recognition is not trust by itself
A file can match a known profile without being accepted as authentic. OpenVerifier separates profile recognition, content integrity, signature verification, signer-policy acceptance, exact-action joining, admission evidence and outcome evidence so each conclusion remains independently visible.