Skip to content

Rebuild runtime-core and canonical-receipts protocol reference pages#256

Merged
GsCommand merged 1 commit into
mainfrom
codex/build-protocol-level-reference-pages
May 21, 2026
Merged

Rebuild runtime-core and canonical-receipts protocol reference pages#256
GsCommand merged 1 commit into
mainfrom
codex/build-protocol-level-reference-pages

Conversation

@GsCommand
Copy link
Copy Markdown
Contributor

Motivation

  • The existing public/runtime-core.html and public/canonical-receipts.html were placeholder/thin pages linked from the site footer/docs and needed full protocol-level reference content.
  • Provide deterministic, canonical protocol guidance for receipt creation and verification without changing API routes, schemas, or deleting files.
  • Remove stale/legacy proof terminology and align visible copy to the canonical metadata.proof model and trust boundaries.
  • Preserve the site look-and-feel (light ENS/Stripe direction), canonical nav/Docs dropdown, and grouped footer.

Description

  • Rebuilt public/runtime-core.html with a full reference including hero copy, "what it does" and "what it is not" cards, proof pipeline flow, canonical metadata.proof field block, stack placement, verification result model, and developer link cards.
  • Rebuilt public/canonical-receipts.html with hero copy, receipt semantics cards, a complete receipt JSON example, required proof field list, verification lifecycle flow, valid vs tampered outcomes, schema-vs-proof warning, usage surfaces, trust boundaries, and CTA section.
  • Aligned both pages to the canonical top nav (including Docs dropdown) and 3-column grouped footer, added consistent CSS snippets and card/code-block layouts, and avoided introducing legacy proof field names.
  • Kept canonical protocol values and notation such as json.sorted_keys.v1, SHA-256, Ed25519, vC4WbcNoq2znSCiQ, runtime.commandlayer.eth, and https://runtime.commandlayer.org.

Testing

  • Ran npm install in the repo and the examples; install completed without errors.
  • Ran npm test in the repo and all tests passed (node --test tests/*.test.js reported successful assertions).
  • Attempted npm run build but the repository has no build script (noted and skipped).
  • Ran cd examples/webhook-auto-verify && npm install and cd examples/webhook-auto-verify && npm run check and the example checks passed (all example verification tests succeeded).

Codex Task

@vercel
Copy link
Copy Markdown

vercel Bot commented May 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
commandlayer-commandlayer-org Ready Ready Preview, Comment May 21, 2026 10:02pm
commandlayer-org Ready Ready Preview, Comment May 21, 2026 10:02pm
commandlayer-org111 Ready Ready Preview, Comment May 21, 2026 10:02pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant