A conformance badge for implementations that pass the OpenChainGraph v0.4 §15 gate suite. The criterion is the gate suite itself, nothing else. Every entry on the registry links its actual passing gate output, not a checkbox.
An implementation may display OpenChainGraph Verified Build if and only if it passes the OCG v0.4 §15 gate suite at its stated spec_version. No separate criteria exist: the gate suite is the standard (§15 preamble), and §15 itself states the meta-rule that every normative MUST in the spec binds to a named gate, and a rule with no wired gate is not part of the standard.
The full rule-to-gate matrix lives in SPEC.md §15 in the public standard repository. It spans envelope and node schema validation, single version-of-record consistency, surface and catalog parity, canonicalization lints against the §4 forbidden constructions, kernel determinism and coverage checks, sign-and-verify round trips for the §16 / §17 / §18 / §20 attestation layers, and post-deploy sweeps that re-verify every live artifact's execution_hash and confirm a real MCP handshake.
Every gate in the matrix is an executable script, checked into the standard repository alongside the schema. A conformance run is: clone the implementation's repository, install nothing beyond what the repository itself declares, and execute each gate script named in the SPEC.md §15 table against the artifacts under test. The AINumbers reference implementation runs the full set with one command, node scripts/preflight.mjs, which executes every §15 gate plus this repository's own build-hygiene checks in CI order and exits non-zero on the first failure.
Every gate exits 0. There is no partial credit and no reviewer judgment call: a gate either accepts the artifact set or it does not, and spec-gate-coverage.mjs separately fails the build if any normative rule in SPEC.md names no gate at all. A green run is the entire proof.
Static list, no submission form. A new entry is a pull request against this page, reviewed by a human, that adds a row linking the implementation's own passing gate artifacts: the actual CI output or gate-run log, not a self-attestation.
| Implementation | spec_version | Passing gate artifacts |
|---|---|---|
| AINumbers.co (reference implementation) | 0.4.0 |
Scripts Verify runs on main ↗ |
To add an implementation, open a pull request against this page's source file with one row naming the implementation, its spec_version, and a link to a public, reproducible gate run.
on dark
on light
The badge is a single self-contained SVG, badge-ocg-verified.svg. It reads prefers-color-scheme and switches its own colors, so the same file embeds correctly on a dark or a light page with no build step.
Any implementation whose passing gate artifacts are linked on this page's registry. Displaying the badge without a registry entry is a misuse of the mark.
Exactly this: the linked implementation passed the OCG v0.4 §15 gate suite at the stated spec_version, as of the date on its linked gate run. Nothing broader: not general product quality, not security posture, not endorsement of any other claim the implementation makes.
OpenChainGraph Verified Build is an unregistered, self-declared-with-evidence mark. It is not a certification mark under the Lanham Act, no application for one has been filed, and none is planned: a certification-mark owner cannot use the mark on its own goods, and the reference implementation both runs the gates and ships a conformant build, so a certification-mark structure would not fit here. The linked gate run is what carries the weight, not the badge graphic.