Three levels. One executable kit.
Conformance in OASP is something you prove, not something you assert. Pick the level that matches what you’re building, then run the kit against it — the same suite every other implementation runs.
What each level requires
Capability by level
Prove it by passing.
The conformance kit is an executable test suite (@oasp/conformance) you run against your implementation. It
exercises the MUSTs for the level you claim and reports pass/fail per check — a
distributable CLI and a signed, portable result format are planned, not shipped yet.
Once that ships, a passing run is what will earn a listing on Implementations — conformance demonstrated, not declared.
Get listed →This is today’s shape — @oasp/conformance is a private, in-repo vitest suite (v0.0.0). No CLI, no remote target, no signing yet.