Rebuild homepage as protocol foundation with canonical proof messaging#226
Merged
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
Description
public/index.htmlhero to: badgeProduction proof live, headlineCommandLayer turns agent actions into signed, independently verifiable receipts., subheadline about the protocol stack, and CTAs linking to/stack-proof-demo.html,/capabilities.html, and the SDK GitHub.verb,class, nestedresult.payload, andmetadata.proofwithcanonicalization: json.sorted_keys.v1,hash.alg: SHA-256→hash.value,signature.alg: Ed25519withkidandvalue, andsigner_id: runtime.commandlayer.eth.Canonicalized,Hash matched,Signer identity matched,Signature valid) and changed runtime animation status toSTEP 1 SIGNED,STEP 2 VERIFIED,STEP 3 TAMPERED INVALIDwithout implying schema-valid == verified.Action executes→Runtime signs receipt→Verifier checks proof→Tampering failswith the requested descriptions, clarified SDK section that the SDK wraps actions while production runtime handles signing and updated the code snippet to use@commandlayer/agent-sdk@1.2.0andprivateKeyPemmarked as environment-only.json.sorted_keys.v1,SHA-256,Ed25519,metadata.proof.hash.value) and renamed API section toVerification surfaceswith cautious wording about runtime/verifyvalidation; added a Capabilities preview section and updated footer product links to include Protocol, Capabilities, Verifier, Runtime, MCP, SDK, Claim, Docs, GitHub.public/index.htmlwas modified and no API routes, schemas, global CSS, or other files were changed.Testing
npm installsuccessfully.npm testand all automated tests passed (26tests passed,0failures).npm run buildand it failed because nobuildscript is defined inpackage.json(this is reported, not a change failure).Codex Task