Verification happens in the browser.
Governance
Neutral verification layer
Open Verifier is an independently stewarded verification layer for inspecting human and machine evidence locally without sending private files to a server.
Governance model
Files are not uploaded, stored, or transmitted.
Supports standards-aligned receipt formats.
Verification behavior can be reviewed, mirrored, or implemented independently.
Every pass, warning, or failure should be explainable to the reviewer.
Protocol compatibility is kept separate from sponsorship, endorsement, or control.
Legal posture is support, not a guarantee of admissibility or compliance.
Stewardship
The initial implementation is stewarded by Aurifex Inc., which maintains the first verifier profile, foundry registry support, and authentication packet workflow.
The long-term direction is open specifications, transparent verification behavior, and adapter support that can expand across human-authorization, qualification, and consequence-control systems.
Brand and compatibility boundary
Open Verifier names a protocol or product only when an exact wire profile, signed identifier, or source artifact must be identified accurately. Public presentation remains Open Verifier-led and vendor-neutral.
Supporting a profile does not imply that its publisher sponsors, endorses, controls, or has approved Open Verifier. Likewise, verifier-side projections are not represented as canonical source-system records unless that mapping is separately established.