Frozen vocabularies that sealed records cite by id.
A record says “my disclosure is written in this vocabulary”, or “my reason is drawn from this one” — and it can say nothing more. The meaning lives in the document, not in the record. So a reader has to be able to fetch the document and read it, forever. That is what this page is for.
…-v2), never an edit. Old records go on pointing at
the old file, and the old file never changes — because the alternative is that a
record quietly comes to mean something it did not mean when it was sealed, with
nothing on the record to show it.songseal-ai-disclosure-v1
— frozen 2026-08-16
How an artist states what part AI played, in their own words, in a fixed vocabulary a reader can resolve years later.
songseal-ai-disclosure-v1 · sha256 d38c59f637a25765732e3e9b316a1dc65316b0d1db6c7c6391055d2b9d7a2486
songseal-correction-reasons-v1
— frozen 2026-08-18
The closed set of reasons a correction may give. Corrections are added to a record, never applied to it — both the original and the correction stay visible.
songseal-correction-reasons-v1 · sha256 82d3c249f1d773e70d737103f87744fa309af61f8ca6032821833d54209af1d9
Those digests are the freeze. They are also published as
CHECKSUMS.json beside the documents, so
the promise is something a build can check rather than something we assert. To
check a document you were served here:
curl -O https://songseal.org/schemes/songseal-correction-reasons-v1.md sha256sum songseal-correction-reasons-v1.md
The scheme documents publish under CC BY 4.0, the same as the rest of the record format. Quote them, cite them, translate them, put them in a filing.
New schemes published from 2026-08-18 onward may carry the licence line inline from the start. The ones already frozen cannot, and must not.