Specification
AI-Authored Change Attestation (in-toto predicate) v0.1
An in-toto Statement (https://in-toto.io/Statement/v1) whose predicate type is https://spec.bucker.io/ai-authored-change/v0.1. It states who and what authored a change, what was verified about it, and which human took responsibility, carrying a full Proof Ledger inline. Wrap it in a DSSE envelope with payloadType application/vnd.in-toto+json.
The document
https://spec.bucker.io/ai-authored-change/v0.1/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/ai-authored-change/v0.1/schema.json| Specification identifier | https://spec.bucker.io/ai-authored-change/v0.1 |
|---|---|
| JSON Schema dialect | https://json-schema.org/draft/2020-12/schema |
| Root type | object |
| Required at the root | _type, subject, predicateType, predicate |
| Named subschemas | 48 |
| Size | 107,690 bytes |
Where this identifier appears
The in-toto predicate type on every attestation the remediation loop emits. A verifier reads it to decide what the statement means.
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.