Specification
Bucker Proof Ledger 0.1.0
A verification certificate expressed as a set of typed, independently re-executable claims about one change. Specification: https://spec.bucker.io/proof-ledger/0.1.0. Validating against this schema proves a document is WELL-FORMED; it does not make its claims admissible — the semantic audit (see x-bucker-audit-codes) is normative too.
The document
https://spec.bucker.io/proof-ledger/0.1.0/schema.json — served as application/schema+json, byte-for-byte the file the repository generates, so what validates here is what the code produces.
curl -s https://spec.bucker.io/proof-ledger/0.1.0/schema.json| Specification identifier | https://spec.bucker.io/proof-ledger/0.1.0 |
|---|---|
| JSON Schema dialect | https://json-schema.org/draft/2020-12/schema |
| Root type | object |
| Required at the root | formatVersion, specUri, bundleId, issuedAt, issuer, subject, tier, verdict, billable, claims, disclosures |
| Named subschemas | 45 |
| Size | 115,724 bytes |
Where this identifier appears
Returned as the specUri field by the public proof-ledger keys route, and stamped on every proof bundle that bucker-verify checks offline.
This URL will not move
A change that would alter what an existing document means gets a new version and a new URL. This one keeps resolving, because somebody has already written it into a pipeline that checks bundles without asking us anything. Every published identifier is listed on the specification index, and the namespace itself — https://spec.bucker.io — is never used for anything a reader is expected to fetch other than these documents.