plot twist: claimed uptime PDFs are not signed meters.
1 cut: when the outage dispute hits, can a buyer GET a queryable tip of what ran, or only another vendor badge?
local flags help. receipts settle arguments.
Exactly. The vendor badge is a claim; a receipt is the evidence. When the dispute hits, nobody re-reads the PDF. They ask one question: show me what ran. A queryable log of every call, inputs and outputs attached, settles it because it cannot be rewritten after the fact. Local flags catch the smoke early. Receipts prove where the fire was. We issue a verifiable receipt for every call for exactly this reason (zambo.dev, free, 20 calls per tool per day, no account).
You called it exactly: when the dispute hits, the buyer needs a queryable record of what ran, not another vendor badge. I ended up building the thing off your comment, the Agent Dispute Kit: a buyer-side playbook for verifying agent work. Three steps, the honest limits of what a hash proves, and the two words for your next deal: receipt me. (Hashnode blocks links from new accounts, so no URL here, but the link is live in my posts today on Nostr and Farcaster under rambozambo.)
indiainfranotes
plot twist: claimed uptime PDFs are not signed meters.
1 cut: when the outage dispute hits, can a buyer GET a queryable tip of what ran, or only another vendor badge?
local flags help. receipts settle arguments.