Publish scoped execution + settlement docs and execution receipt demo#384
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c77d3dc31a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <body> | ||
| <nav><div class="container nav-inner"><a href="/" class="brand"><img src="/commandlayer-logo.png" alt="CommandLayer" /><span>CommandLayer</span></a><ul class="nav-links"><li><a href="/">Home</a></li><li><a href="/protocol.html">Protocol</a></li><li><a href="/capabilities.html">Capabilities</a></li><li><a href="/receipts.html" class="active">Receipts</a></li><li><a href="/proof.html">Live Proof</a></li><li><a href="/sdk-records.html">SDK</a></li><li class="nav-drop"><a href="/docs.html" aria-haspopup="true">Docs ▾</a><div class="nav-drop-menu"><a href="/docs.html">Docs Home</a><a href="/docs/wrap-your-agent.html">Wrap Your Agent</a><a href="/docs/scoped-execution-settlement.html">Scoped Execution + Settlement</a><a href="/execution-receipt-demo.html">Execution Receipt Demo</a><a href="/runtime.html">Runtime</a><a href="/mcp.html">MCP Bridge</a><a href="/schemas.html">Schemas</a><a href="/api.html">API Reference</a><a href="/integrations.html">Integrations</a><a href="/verify.html">Verifier</a></div></li><li><a href="/claim.html">Claim</a></li><li><a href="https://github.com/commandlayer" target="_blank" rel="noopener">GitHub</a></li></ul></div></nav> | ||
| <main> | ||
| <section class="hero"><div class="container"><h1>Execution receipt demo</h1><p class="lead"><strong>Private settlement, public accountability.</strong> These examples show how <code>clas.execution.receipt.v1</code> scopes signatures so execution and settlement are independently attested.</p><p style="margin-top:18px"><a class="btn btn-primary" href="/verify.html">Verify in VerifyAgent paste flow</a> <a class="btn btn-secondary" href="/docs/scoped-execution-settlement.html">Read docs</a></p></div></section> |
There was a problem hiding this comment.
Stop sending unsigned scoped examples to the verifier
When a reader follows this CTA and pastes any of the demo receipts shown below, /verify.html posts the JSON to /api/verify, whose verifier currently requires the existing runtime shape with metadata.proof plus signer/hash/signature fields; these new examples instead use an unsigned top-level proofs array. As a result, the two examples labeled valid are reported as INVALID, which makes the new demo look broken unless verifier support or real signed sample receipts are added first.
Useful? React with 👍 / 👎.
Motivation
clas.execution.receipt.v1model that separates execution and settlement attestations under onereceipt_idto preserve trust boundaries and private settlement data while enabling public accountability.sha256:payee commitments and opaquepayment_refvalues.Description
public/docs/scoped-execution-settlement.htmlexplaining the scoped receipt model, why execution and settlement proofs are separate, opaquepayment_refrequirements,payee_commitmentassha256:commitments, selective disclosure, VerifyAgent UI, and a schema publication note.public/execution-receipt-demo.htmlwith three examples: execution-only, execution + private settlement, and an invalid example where the agent attempts to cover settlement, plus CTAs to the verifier paste flow and docs.public/docs.html,public/receipts.html, andpublic/sdk-records.htmlso the docs and demo are discoverable without changing the overall nav layout.Codex Task