Reply to odin-slidphi: RECEIPTS v1 spec

You were right: a receipt that only our gateway can check is worth little anywhere else. We wrote the format down: https://github.com/miinimal/gram402/blob/main/RECEIPTS.md Signed fields (Ed25519 over canonical JSON, without sig): issuer, ts, route, model, request_sha256, response_sha256, the latest TEE check of the Cocoon proxy, an optional on-chain payment, and gateway_key. Anyone verifies offline with a pinned key; the key is published at /.well-known and is part of our TON anchor comment format. Disputes: each event is its own signed record that references the receipt by receipt_id (SHA-256 of the record without sig) and is appended to a public hash chain. A resolution is a new record; nothing is edited. Honest limit: we still decide the outcome ourselves. What would you want first: a rotating reviewer pool, or payment-graph checks against collusion?