Who built what, and what each record establishes

OpenVerifier is independently operated by Aurifex Inc. This page separates implementation ownership, upstream technical sources, package identity, deployment evidence, and interoperability boundaries.

Operation and attribution

OpenVerifierDesigned, implemented, and independently operated by Louis Clybourn Jr. / Aurifex Inc. · openverifier.org

SYNC IntentHuman authorization / presentation-evidence source supported by OpenVerifier · Aurifex Inc. · App Store listing

EMILIA ProtocolPublic technical source for Gate Qualification and CAID materials. OpenVerifier is not operated by EMILIA Protocol, Inc. · public repository

CAID Internet-DraftThe Canonical Action Identifier (CAID), authored by Iman Schrock, Work in Progress · IETF Datatracker

Technical sources

Gate Qualification v2EMILIA public profile source

CAID materialsPublic CAID registry and implementation sources. OpenVerifier's exact-action profile remains pinned to the reviewed local payment.release.1 definition rather than silently following future registry changes.

ISO 4217 alpha-3 pinSIX Financial Information AG, Secretariat of the Maintenance Agency for ISO 4217. The package carries a closed offline code-set snapshot for payment.release.1; no runtime fetch or caller extension is permitted.

OpenVerifier compatibility logicVerifier-side interoperability implementation maintained by Aurifex Inc.; compatibility output is not a native EMILIA Gate record.

Exact-action continuity

OpenVerifier uses exact-action continuity as explanatory language for the relationship established when the material action protected by a human-reviewed SYNC record is the same typed action represented by the corresponding signed Gate compatibility projection under explicit relying-party pins.

The phrase is not an EMILIA protocol-state name and does not add an authorization decision. A continuity match does not prove execution, provider settlement, physical effect, human comprehension, or a canonical Gate deployment.

Package and deployment identity

Package revisionv13.9.0-rc3 — completed UI/state/reporting and release-state finalization over the independently checked rc2 exact-action logic. Current review and deployment state are intentionally external to these immutable bytes.

Source revisionopenverifier-v13.9.0-rc3

Deployment manifestDEPLOYMENT_MANIFEST.json identifies the exact intended served files and public-surface hash. Mutable deployment status is intentionally outside the immutable manifest.

Prior rc2 ZIPc59a7ec00b5e3a63d8c036624dd8521236ab18511481fbc3286ca932054e034c

Prior checked rc2 public surfacea02df8dd91f56e328748fb16ead5fb3576f88071b26268f63d1af7c467b626c6

Prior deployment attestationJSON record · checksum · SHA-256 53d6ba62ace7076bdb11542db79d9849773064aab93ff6072396ce9764c7b8ca. The record is unsigned; its hash identifies exact bytes rather than signer provenance.

Historical baselinesp3 ZIP fc676e975bb679c2f5971a8209c5dd07bb828dfd95fee8ba0a33bb6847823e3d; separately reviewed v13.8 ZIP e6d2324baf13d09d7c2cee74d905f74230bfddaf3fdcae343661bbeee1d6697d.

Deployment-state model

The review package and deployment manifest are immutable byte identities. Whether those bytes are currently deployed is a later operational fact. OpenVerifier records that fact separately through a versioned deployment-attestation JSON so the reviewed package never has to be rewritten merely because deployment state changed.

A deployment-attestation hash identifies the exact JSON bytes. Unless that record is separately signed, it is not a signer-provenance attestation and does not expand the checks it describes.

Compatibility boundary

Aurifex Inc. operates OpenVerifier independently. Support for public EMILIA Gate Qualification, CAID, or related artifact shapes means only that OpenVerifier implements a verifier-side compatibility profile against cited public sources.

Compatibility does not mean EMILIA approval, certification, partnership, endorsement, or a canonical EMILIA Gate deployment. OpenVerifier does not speak on behalf of EMILIA Protocol, Inc. or Iman Schrock.

Licenses and modification notices

EMILIA repositoryApache License 2.0. OpenVerifier cites public EMILIA materials and identifies its verifier-side modifications separately.

CAID registry metadataPublic repository metadata identifies CC0-1.0 for the registry materials.

CAID Internet-DraftWork in Progress under applicable IETF Trust Legal Provisions. Citation does not imply IETF endorsement.

rc3 modification boundaryCompletes UI/state/reporting and release-state cleanup by removing mutable package-review metadata from exact-action result output and the dynamic result label while retaining the previously scoped continuity, onboarding and state-association fixes. Verification decisions/checks are unchanged; four supporting verification modules remain byte-identical to rc2.

Read plain-text notices