Seven documents
Numbered, versioned, dated and public domain. Review means the format is implemented and the lab is looking for problems with it. Draft means it will change, and building on it without saying so is your own risk.
| Spec | Title | Status | Version | Summary |
|---|---|---|---|---|
| RVW-1 | Credential claim | Review | 0.3 | The document a professional signs: what it holds, how it is canonicalised, how it is identified, how it is signed. |
| RVW-2 | Domain binding | Review | 0.2 | A DNS record on the business domain, and a signature naming that domain. Neither side can claim the pair alone. |
| RVW-3 | Delegation and operational keys | Draft | 0.2 | One identity, many addresses. How a cold identity key authorises a fresh address for a single job. |
| RVW-4 | Attestation | Draft | 0.1 | A signed statement that somebody checked something, carrying exactly the weight of whoever signed it. |
| RVW-5 | Authority file | Review | 0.2 | The smallest useful thing an issuing authority can publish: one file, on its own domain, no API. |
| RVW-6 | Revocation and freshness | Draft | 0.1 | Why every claim expires, how a claim is withdrawn, and how a consumer shows decay instead of a badge. |
| RVW-7 | Anchor contract | Review | 1.0 | The optional onchain contract: fifty lines, no owner, no upgrade path. Deployed and verified on Ethereum mainnet. |
How these change
A specification in review changes only in ways that do not break a document already signed, and every change is recorded in the changelog with a date. A specification in draft changes however it needs to.
Nothing here is ratified by anybody. There is no committee, no membership and no vote, because there is nothing yet that deserves that ceremony. If the formats are adopted beyond the first implementers, governance becomes a real question and it will be answered in the open.
Every document is CC0 1.0: copy it, fork it, ship it under another name, no permission needed and no attribution owed. Reference code is MIT. The name and the mark are not covered by either.
Problems with a specification go through the contact page. A problem that changes a document is published in the changelog whether or not it was comfortable.