~/djzs/verify $ recompute --receipt --v2
A receipt is a claim. This tool recomputes it. Settlement from the chain; the binding key from the intent alone; the attestation from EAS. It checks that all three agree with each other. Nothing here trusts DJZS. Unknown resolves to WAIT, contradiction to FAIL.
receipt · json · body + payment_response as the gate returned them
Q3 daily anchors · the study's record book, Merkle-rooted to Irys
10 recordsprotocol 1.13
root 0xae02db92d1ea365107f1b365775b35922dd3529941684cbcea6be3f8ba874682 irys 3w8hzn8mDr…nAKk9P anchored 2026-09-14T23:56:42.577Z1 recordprotocol 1.3.1
root 0xb393fdfe3d61b835d9bad781c30891356a7b828562de6158e4afe7481608e75b irys CvkLcDSJbx…ToSWxN anchored 2026-09-04T16:33:35.186Z2 recordsprotocol 1.1
root 0x8a5117fa6f999355cc0e02560d0dbde5a96fb6bed2a21381b837b58f99ad335d irys Cf87hGKm9u…KrWfY4 anchored 2026-09-03T02:44:52.514Z3 anchored days · 13 records
Each day's sealed record_hash values are Merkle-rooted and the root written to Irys. Git history alone is rewritable and is not tamper-evidence; these items are. Recompute with npx tsx tests/q3/q3-anchor.ts --verify <date>; it fetches the item and compares the anchored root against one recomputed from the committed records.