Every normative MUST in each pinned UCP spec version is accounted as a kill-rate-validated check, a documented exemption, or an open gap — no silent omissions. Every check additionally carries an evidence class — live-wire (kill-tested against an independently-authored server), official ucp-schema oracle, crypto self-test, or self-referenced (only our own fixture vouches for it) — so this matrix says not just that a requirement is checked, but how strongly. Each requirement links to the exact line of the pinned official spec, and is browsable as the check register, graded per the rubric.
The tabs above are the merchant lane (a store's UCP responses). This is the agent lane: the reverse harness that grades a shopping agent's own behavior — OAuth mix-up / PKCE, RFC 9421 request signing, refusing mismatched totals, phishing defense — against the agent-side MUSTs, with the same kill-rate rigor. About the agent lane → · watch it live →
| Req | Status | Requirement (verbatim-verified against the pinned spec) | Spec | Covered by |
|---|
coverage CI gate fails the build if this page's data goes stale or accounted coverage ever decreases (ratchet).
Evidence classes are derived mechanically from how each check actually runs — never hand-labeled — backed by a recorded run against both independent reference targets, and the published split is drift-gated in CI; the self-referenced class is the fixture-circularity we also flag upstream (conformance#79).
Roadmap →