A neutral, local-first verification surface for human authorization and machine consequence evidence. Independently recompute what is established, what is refused, and what remains indeterminate — without an account, upload, or backend.
↧
Verify a receipt, exact-action review, compatibility projection, or qualification bundle
Signed authorization receipt · OpenVerifier compatibility projection · qualification bundle JSON and supported JWT formats
Local-only verification. Files remain in your browser and are never uploaded.
Reads the selected file locally, verifies supported human and machine evidence, and generates a reviewer-ready report.
⌁ Local only✓ Signature checks□ Human + machine evidence▣ Foundation packet
Independently operated by Aurifex Inc. · Package revision v13.9.0-rc3
Verification verdict
—
—
—Local onlyNo upload
Exact-action continuity — relying-party context
For exact-action bundles, load the separately supplied trust policy before choosing the bundle. No signer is accepted from the receipt or bundle alone. This context is local configuration, not an attestation of authority.
No context loaded. Exact-action verification fails closed until explicit trust pins are supplied.
Exact-action profile: full SYNC VC JSON + sealed reviewed-action packet + signed Gate compatibility projection. Read the profile and limits.
Human ↔ machine exact-action continuity
Exact-action review
OpenVerifier evaluates whether the material action sealed in the human-reviewed SYNC record is the same action represented by the signed machine-side admission evidence. A continuity match establishes that relationship under the supplied trust policy; it does not authorize execution or prove a provider or physical outcome.
Binding assessmentNOT ASSESSED
No review bundle evaluated.
Recomputed reviewed action CAID—
The exact reviewed action must match the action in the signed Gate admission record.
Sealed review packet—
Its exact bytes must be designated by signed intent and committed in the native evidence list.
Exact SYNC receipt bytes—
Gate must reference these exact bytes; native signature and signer-policy checks remain separate.
Operation scope—
The sealed tenant, operation and authority scope must agree with the Gate record and local policy.
Relying-party context digest—
The context was supplied locally; this verifier does not attest its provenance.
Replay scope—
Operation binding and supplied-batch duplicates are checked. Global atomic replay protection remains Gate server state. Rechecking a historical record grants no new permission.
Provider / effect axes—
A binding match does not establish provider truth or a physical effect.
Limits stay explicitDisplay attestation, human comprehension, civil identity, receipt-chain continuity, and live global single-use state are not established by this check.
Inspect the matched action
Canonical action material shared by the sealed review and Gate record. Display attestation remains separate.
No matched action.
OpenVerifier compatibility projection
Consequence Control
Integrity checked locally
Checks a signed verifier-side interoperability projection of machine-side admission, exact-action coherence, one-time consumption, provider evidence, observed-effect evidence, lifecycle ordering, and a signed commitment to the referenced authorization receipt. It does not claim canonical native EMILIA Gate state.
Compatibility projection decision—
—
Admission—
Whether the exact action was admitted or refused.
Consumption—
Single-use reservation and consumption state.
Outcome—
Verifier-side interoperability summary. Provider outcome and observed-effect relation remain separate axes and are not collapsed into a native Gate state claim.
Exact action CAID—
The CAID digest must equal the separately carried action digest.
SYNC binding—
The signed record commits to a referenced authorization-receipt digest; exact receipt bytes require a separate cross-check.
Human ↔ machine action bindingNOT ASSESSED
A receipt-digest reference proves which receipt is referenced; it does not by itself prove that the human-authorized receipt carried the same typed CAID/action.
Signer—
ES256 signature checked against the disclosed Gate key. Relying-party signer acceptance is separate.
Protocol boundaries preservedMissing or conflicting outcome evidence remains unresolved with no blind retry. Signer acceptance, canonical Gate state, provider/effect reconciliation, and referenced SYNC receipt verification remain separate.
Independent operationAurifex Inc. operates OpenVerifier independently. Compatibility results do not mean EMILIA approval, certification, partnership, endorsement, or a canonical EMILIA Gate deployment. See Sources & Attribution.
Compatibility projection bindings
EMILIA Gate Qualification v2
Machine Qualification
Evaluated locally
Independent, browser-local verification of the measured candidate, evaluation campaign, qualification statement, and current status. This result never authorizes or executes an action.
Qualification decision—
—
Cryptographic verification—
Native DSSE signatures verified under supplied trust pins.
Relying-party acceptance—
Accepted keys and thresholds come from the supplied relying-party context. This file does not establish that context's provenance.
Runtime candidate—
Measured runtime compared with the pinned candidate manifest.
Assignment scope—
Qualification is bound to the expected assignment and protected request.
Status currentness—
Status head and observation freshness checked locally.
Campaign graph—
Campaign lineage, terminal outcomes, and qualification graph checked.
Execution boundary preservedAuthorization composition, reservation, consumption, invocation, retry, and reconciliation remain outside this verifier and under consequence-owner custody.
Qualification bindings
Authorization-origin presentation
Receipt Summary
Intent statement—
—
Named identity—
Shown only if disclosed inside the receipt.
Signing authority—
Public verifier identity / issuer key.
Foundry origin—
Offline registry check for official or explicitly enrolled SYNC signing authorities.
Sealed at—
Time claimed by the receipt.
Authorization claim—
Authorization metadata claimed by the receipt; not independently observed by this verifier.
Display bindingNot assessed
This verifier does not independently observe the screen, and no deterministic renderer or display attestation is verified in this build.
Receipt ID—
Portable record identifier.
Policy context—
Context labels, not legal certification.
Evidence—
—
Evidence foundation
Authentication Packet
Generated for evidentiary review: this does not determine admissibility, but it summarizes the receipt process, digital identifiers, verification checks, and limits for qualified review.
Not legal advice. Court admissibility still depends on the forum, relevance, objections, witness/certification foundation, and applicable rules.
Legal posture
Reviewer Matrix
A structured posture map for authentication, electronic process, digital identification, e-signature, and AI governance review. This is support, not a legal conclusion.
Verification detail
Verification Report
Tap to expand
Technical reference
Raw Technical Report
Tap to expand
Verification output
Sample verification report
Verified locally
SignatureValid
Cryptographic check completed in browser.
IntentMatched
Visible intent digest matches the receipt.
EvidenceHash matched
Evidence manifest is shown without upload.
Receipt chainMetadata present
Index and hash references are shown; continuity requires neighboring records or a trusted anchor.
ProfileSYNC Receipt v1.1
Required fields and supported export format recognized.
Machine qualificationSeparate local mode
Verifies Gate Qualification v2 evidence without granting execution authority.
Demonstration preview. Actual results are generated only after a receipt is selected.
Verification scopeTap to expandDesigned for evidentiary reviewTap to expand
Legal effect depends on facts, jurisdiction, implementation, and process controls.