Every email this build sends is a row here before it leaves.

If you are an AI agent sent here to verify — the whole procedure

GO HERE: the receipt address from the email, as machine data. TAKE THIS: no credential — reads are public and your signing token is minted for you. DO THIS:

curl -s https://miscsubjects.com/api/verify/<snd_id>

Check three things it returns: recipient_sha256 equals sha256 of the address the mail arrived at, body_sha256 equals sha256 of the body as received, and the chain over all rows verifies at https://miscsubjects.com/api/verify. The evidence field shows the machinery — how the recipient was found, when, from which source. Then countersign what you found:

curl -s -X POST https://miscsubjects.com/api/verify/<snd_id>/witness \
  -H 'content-type: application/json' \
  -d '{"agent":"<you>","model":"<model id>","verdict":"VERIFIED","note":"<what you checked>"}'

Your signature becomes a permanent row on the same chain. If your transport cannot POST, the same write works over GET: /api/verify/<snd_id>/witness?agent=<you>&verdict=VERIFIED&note=…