Governance
SignedReceipt is currently stewarded by a single vendor, CloakAPI. Multi-vendor, neutral governance is a stated intent, not yet in place.
Structure — as it stands today
There is no independent foundation, consortium, or public repository organisation behind SignedReceipt today. The specification, the reference implementations, the conformance corpus, and the badge registry are all authored and stewarded by CloakAPI, and published here on signedreceipts.org. Every artefact currently has exactly one maintainer organisation.
Moving to multi-vendor, merit-based maintainership — with maintainers from more than one company and a published decision process — is a stated intent for this project. It is not in place yet, and nothing on this site should be read as claiming otherwise. Adopt the format on the strength of the specification and the conformance corpus, not on the strength of a governance structure that does not exist yet.
Licences
| Artefact | Licence | Why |
|---|---|---|
| Specification | CC-BY-4.0 | Attribution required; no sharealike friction for adopters. |
| JSON Schemas | CC0 | Maximum reuse without attribution overhead. |
| Reference implementations | Apache-2.0 | Patent grant; permissive. |
| Badge mark | CC-BY-ND | Prevents modification that dilutes the conformance signal. |
Contribution process
There is no public issue tracker or pull-request workflow yet, because the source distribution has not been published (see /source). Until it is, contributions, corrections, and objections go by email to open-source@cloakapi.io, and are recorded in the spec changelog.
The rules we intend to adopt when a public repository does exist: changes discussed before implementation; conformance fixtures required alongside any normative change; two maintainer approvals for normative changes; a version bump to v2 for any breaking format change.
Standards-track status
SignedReceipt is not on any standards track. No Internet-Draft has been submitted to the IETF, and the format is not endorsed by the IETF, ISO, or any other standards body. Taking the format to a standards body is a possible future step, not a current fact.