Verification happens in the browser.
Governance
Neutral verification surface
Open Verifier lets anyone inspect supported signed artifacts locally without sending private files to a vendor or server.
Governance model
Files are not uploaded, stored, or transmitted.
Supports standards-aligned receipt formats.
Receipt structure can be reviewed, mirrored, or implemented independently.
Every pass, warning, or failure should be explainable to the reviewer.
Legal posture is support, not a guarantee of admissibility or compliance.
Neutrality and trust boundaries
Open Verifier does not treat profile recognition, a self-carried key, an organization name, or a product relationship as trust. Signer acceptance requires an independently configured policy or explicit local relying-party acceptance.
Support for a format, protocol, or verification profile does not imply endorsement, certification, partnership, legal status, or compliance. Results describe only the supplied bytes, configured trust rules, and checks that actually ran.
Exact-action continuity boundary
OpenVerifier can evaluate whether human-side and machine-side evidence denote the same exact material action. That relationship is reported separately from signer acceptance, execution authorization, provider outcome, physical effect, and legal effect.
Exact-action continuity is explanatory OpenVerifier language, not a claim that OpenVerifier owns or replaces the native authorization or consequence systems it verifies.
Operation
Aurifex Inc. independently operates and maintains OpenVerifier. EMILIA Protocol does not operate this deployment. Compatibility with publicly documented EMILIA artifacts does not make this a canonical EMILIA Gate deployment.