Canonical Release
An instrument version is official only when it is issued by the Hybrid Board, carries a release label and UTC timestamp, and its canonical SHA-256 fingerprint and release metadata are docketed in the Public Record. Possession of identical bytes is not issuance.
Canonical definition
A canonical release is the official issuance of an instrument version: issued by the Hybrid Board, identified by a release label and a UTC timestamp, and recorded in the Public Record under a docket with its canonical SHA-256 fingerprint and release metadata.
Why this node exists
Possession of a file is not issuance. Official status depends on the docket, not on the bytes, and this rule is what makes third-party copies harmless and derivatives distinguishable.
Operational meaning
Verification is a one-minute path: obtain the canonical PDF from the release endpoint, compute SHA-256, compare with the docketed fingerprint and, where provided, verify the OpenTimestamps receipt. Authorized copies are byte-identical reproductions; publication copies may add release metadata if marked; any derivative must be marked non-authoritative and cite the fingerprint it references.
What this does not mean
A canonical release is not an endorsement by anyone and not a claim of legal force. Two hashes can coexist for one instrument: the archival artefact's digest referenced inside a copy, and the docketed fingerprint of the public release; only the latter is verifiable against the downloadable file.
Canonical facts
- Validity conditions
- issued by the Hybrid Board; release label and UTC timestamp; fingerprint and metadata docketed (Statute §3.2)
- Fingerprint method
- SHA-256, published per release
- Verification
- compute SHA-256 of the canonical PDF, compare with the docket, verify the OTS receipt (FAQ)
- Derivatives
- must be marked non-authoritative and cite the referenced fingerprint (Statute §3.4)
- Current releases
- AI Constitution v1.0 (PR-0001), Board Statute v1.0 (PR-0002), Sentinel Liaison Protocol v0.8 (PR-0003), supplements set v1.0 (PR-0004)
Structural relationships
Outgoing
- Canonical Release requires Docket
- Canonical Release uses Proof of Existence
Incoming
- Hybrid Board issues Canonical Release
- No Silent Edits requires Canonical Release
- Proof of Existence anchors Canonical Release