Skip to content

Add canonical Protocol page (public/protocol.html)#227

Merged
GsCommand merged 1 commit into
mainfrom
codex/create-or-rebuild-protocol-page
May 20, 2026
Merged

Add canonical Protocol page (public/protocol.html)#227
GsCommand merged 1 commit into
mainfrom
codex/create-or-rebuild-protocol-page

Conversation

@GsCommand
Copy link
Copy Markdown
Contributor

Motivation

  • Provide a dedicated canonical Protocol page that explains CommandLayer’s architecture, trust boundaries, and receipt model as the authoritative reference for the stack.
  • Surface the production proof facts and canonical receipt model so integrators know the canonicalization, hash, and signature algorithms and the runtime signer identity.
  • Preserve the site visual direction and top navigation order so the new page fits the existing homepage design system and routing.

Description

  • Added a new file public/protocol.html implementing the full Protocol page with the required top nav (Home, Protocol, Capabilities, Verifier, SDK, Docs, Claim, GitHub) and homepage visual style.
  • Implemented required sections: Hero (eyebrow/headline/subheadline + CTAs), Architecture stack cards (CLAS, runtime-core, runtime, MCP, VerifyAgent, agent-sdk), Canonical receipt model code block using metadata.proof, Trust boundaries grid and warnings, Verification lifecycle flow, Production proof summary (STEP 1/2/3), Capability families, and final CTA panel.
  • Included canonical production-truth values and algorithms exactly as required: json.sorted_keys.v1, SHA-256, Ed25519, kid: vC4WbcNoq2znSCiQ, and signer_id: runtime.commandlayer.eth.
  • Did not change other pages, API routes, schemas, or delete files, and avoided deprecated/incorrect fields (top-level proof, proof.alg, proof.kid, lowercase ed25519, signature_b64, hash_sha256, or claiming MCP as signer/trust root).

Testing

  • Ran npm install successfully with no install errors.
  • Ran npm test and all automated tests passed (26 tests passed, 0 failed).
  • Confirmed there is no build script in package.json, so npm run build was not executed.

Codex Task

@vercel
Copy link
Copy Markdown

vercel Bot commented May 20, 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 20, 2026 10:53pm
commandlayer-org Ready Ready Preview, Comment May 20, 2026 10:53pm
commandlayer-org111 Ready Ready Preview, Comment May 20, 2026 10:53pm

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