Add x402-to-CLAS paid-action receipt integration design doc#283
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
metadata.traceguidance, andproof.signaturerole semantics (single- and multi-signature) for predictable downstream verification and auditing.Description
docs/integrations/x402-commandlayer-receipts.mdcontaining the full design doc and required sections (Overview, Why x402 matters, Trust boundary, Paid-action lifecycle, CLAS receipt shape,metadata.traceusage,proof.signatureroles, examples, failure modes, idempotency, settlement vs execution proof, future integration, and non-goals).payment.acceptedevent, a CLAS receipt emitted after execution, and a paid verification call example aligned toVerifyAgentusage.request_id,payment_id,receipt_id), guidance for trace fields, and explicit role semantics foruser,payer,agent,runtime, andverifierwithinproof.signatureentries.Testing
npm testin the repository and all automated tests passed (44passing,0failing).Codex Task