# Certification Process
Certification is fully automatic. There is no review board, submission queue,
private approval, or maintainer blessing. Run the suite, keep the structured
results, and publish them if you want others to rely on the claim.
## Process
1. Construct a backend that implements `VyreBackend`.
2. Run the conformance suite for the desired level.
3. Inspect the result.
4. If any required test fails, the backend is not conforming at that level.
5. If every required test passes, the backend is conforming at that level.
6. The certificate is the structured report produced by the run.
Quality is the gate. A backend that passes L4 is conforming at L4. A backend
that fails any required L4 test is not conforming at L4, even if the failure
looks small, rare, or vendor-specific.
## Certificate
The certificate records what was tested: backend identity, suite version,
operation IDs and versions, engine IDs and versions, conformance level, seeds,
coverage metrics, regression set, law results, invariant results, composition
results, performance baselines, and failures.
Because the certificate is structured, it can be published, compared, archived,
and verified in the future. A downstream project can require "L4 for suite
version X" without asking who approved the backend.
## Failure
Any required failure blocks certification for that level. A parity mismatch, law
violation, invariant violation, nondeterministic replay, missing output,
duplicate output, unacceptable dispatch error, skipped regression, or broken
performance baseline means the backend does not conform at the claimed level.
The correct response to a failure is to fix the backend or correct and version
an invalid spec entry. The process does not permit waivers for known failures.