The standard is open. Certification is the audited product: a signed conformance report, a public registry entry, and a mark that carries its own scope — so anyone can check it rather than trust it.
A candidate manifest, the evidence bundle, and read access to the model + data.
The conformance suite recomputes the deficit, gates, mutations, reviewer independence and evidence.
A sample of gates and mutation tests is re-run; the evidence bundle is confirmed.
Pass → certificate. Fail → a written list of the gaps.
Version, level, deficit, guards proven and the report hash, in public.
product v{version} · audited {date} · L3 · m={m} · report hash — no evergreen badge.
Every certified version is listed with its scope. The first entry is a self-certified reference — we ran our own suite — and is labelled as such; the first independent certification is a design-partner run.
| Product | Version | Level | Deficit | Gates | Auditor | Status |
|---|---|---|---|---|---|---|
| pacland | 0.9 | L3 | m = 4 of 12 | 5/5 structural | VVS (self) | self-certified reference |
The machine-readable registry is in the standard repo. The first independent entry appears after a design-partner run.
Revocations are public in the same registry, with the reason and the date.
Bring the model you're not sure about. We return the signed conformance report — and, if it holds, the mark.