Specifications
The identifiers resolve
Every schema below declares an $id under https://spec.bucker.io, and that identifier is what a proof bundle, an attestation or an essence document carries. These are the documents behind those strings, served byte-for-byte from the repository that generates them.
Published documents
| Document | Identifier | Where it appears |
|---|---|---|
| AI-Authored Change Attestation (in-toto predicate) An in-toto Statement (https://in-toto.io/Statement/v1) whose predicate type is https://spec.bucker.io/ai-authored-change/v0.1. | https://spec.bucker.io/ai-authored-change/v0.1/schema.json | The in-toto predicate type on every attestation the remediation loop emits. A verifier reads it to decide what the statement means. |
| Error Essence A token-budgeted, trust-labeled projection of one production error, intended for an LLM context window. | https://spec.bucker.io/error-essence/1.0.0/schema.json | The normative schema for the essence format, generated from the reference implementation in shared/src/essence.ts so prose and code cannot drift. |
| Error Essence (causal) A token-budgeted, trust-labeled, CAUSAL projection of one production error, intended for an LLM context window. | https://spec.bucker.io/error-essence/2.0.0/schema.json | The normative schema for the essence format, generated from the reference implementation in shared/src/essence.ts so prose and code cannot drift. |
| Bucker Proof Ledger A verification certificate expressed as a set of typed, independently re-executable claims about one change. | https://spec.bucker.io/proof-ledger/0.1.0/schema.json | Returned as the specUri field by the public proof-ledger keys route, and stamped on every proof bundle that bucker-verify checks offline. |
Identifiers with no document yet
Named rather than hidden. These strings ride on responses the product already returns, so a reader will meet them; the honest answer is that the format is stable and versioned in code and that no schema document has been generated for it.
Versioned paths never move
A published identifier is a promise to whoever wrote it into their pipeline. A change that would alter the meaning of an existing document gets a new version and a new URL; the old one keeps resolving. That is why this index is generated from the files rather than curated — a document that exists is a document that is served, and one that was served cannot quietly stop being.