2026-08-06:
b3e4c6c60fd3d5ebd32dacecf5a745fce54f0484129d432edefe3b1e5001dea0
This is for a PDF of a draft paper, before asking a non-local LLM to comment on it. Since who knows where the data really goes...
Interesting. I'm not sure this works to track "where it really goes", as it won't survive vectorization/summarization or even simple partial-delivery. It's good for proof of integrity for a document that's delivered over another channel.
What's the actual intent for who/when the hash is compared against a future document?
It's proof of having done it now if it turns up as an "AI generated" result afterwards. I might not upload the draft unless that becomes an issue. (The final document will be more readable, of course.)
These can be checked against a file distributed in the future with 'shasum -a 256 file'.