• Don’t Trust, Verify • Not a single byte changes. • If it cannot be reproduced, it is not evidence.
I’m publishing a contract-only spec for a non-custodial integrity receipt workflow (exit code + SHA-256 + normalized JSON). Feedback I want: is the NOT_COVERED fence strict enough to prevent over-claims?