The base magic is that, when a "checksum" is included, there is a link to the referenced content.
For Git repositories, this might need to include a full path to the repo.
But it is (or at least should be) a way of asserting a datetime and content.
There are two basic functions needed for magic.
One is delayed-release. The checksum is released now, the content is released in 1 year.
The other is expiration. The checksum is released now, the ability to "forge" a checksum is released in 1 year. Now, one can have arbitrary content with the same checksum.
🔥 as 小龙语 is not available, we will use JSON.
⚔️ well, actually ... this all seems needlessly complicated. because of trying to get one system to do two very different things.
step 1 is add support for Github checksums to earlyversion.
step 2 is some type of blob storage with metadata.
once i stop needing to tie them together, the need for magic dissipates.