Status lives in the API
Publisher verification writes currently return 404. When a reviewed proof flow reopens, consumers must check the rights endpoint instead of trusting a copied image.
README badge
Link to the proof model.
This asset is reserved for a future verified namespace. Publisher onboarding is currently fail-closed and production has no rights rows, so do not use the badge as a current claim. When verification reopens, the authoritative namespace-control record will remain GET /v0/publishers/{publisher_passport}. The image alone is not proof, and it does not imply a signed rights receipt.
/badge/verified.svgCopy & paste
Two snippets, one verification model
These snippets link to the protocol's verification boundaries, not to a per-server evidence page. Public receipt retrieval and authoritative key discovery are M1a work.
Markdown
[](https://rcxprotocol.org/verify)HTML
<a href="https://rcxprotocol.org/verify">
<img src="https://rcxprotocol.org/badge/verified.svg" alt="Verified on RCX-Registry" height="20">
</a>Why it’s worth it
A badge that actually means something
It links to the model
Clicking through explains canonical bytes, signatures, link semantics, conformance vectors, and the current gap before complete public live verification.
It is not proof by itself
The SVG is a public static asset and can be copied by anyone. Treat it as a navigation aid; rely on API metadata for actual status only after verification is reopened.
Verification is temporarily unavailable.
Do not publish this badge as a verified claim today. Review the closure and evidence boundary while the replacement publisher-proof flow is designed and accepted.