External trust anchor
Supply an Ed25519 public key or JWKS. Missing, ambiguous, or mismatched key identifiers fail verification.
Independent verification
Verify the receipt without trusting Operandi
The verifier checks schema, signature, key identity, and receipt integrity against a trust anchor you supply. It does not trust a key embedded beside the receipt.
Release candidate command
npx vba verify receipt.json trusted-jwks.jsonPublic package installation is not available yet. Publication remains gated on written name clearance and a fresh-environment release proof.
Fail-closed checks
What the verifier accepts—and refuses
Known receipt schemas
Outcome receipts and candidate Verified Read receipts must pass their published schema and integrity rules.
Machine-readable result
Success returns stable JSON and exit code zero. Tampering, schema failure, or invalid trust returns a non-zero exit code.
What verification means
Integrity is not business truth
A valid signature proves who signed the content and that the signed bytes have not changed. It does not, by itself, prove that a provider completed an action or that a business claim is correct. Those outcomes require their own retained evidence.