From 0a98b5d0ca8b838817fe10ddeea194dfb462609b Mon Sep 17 00:00:00 2001 From: Greg Soucy Date: Wed, 20 May 2026 23:01:12 -0400 Subject: [PATCH] Fix light-theme page blockers and add missing protocol docs pages --- public/ambient-verification.html | 18 ++++++++---------- public/api.html | 8 +++----- public/canonical-receipts.html | 1 + public/claim.html | 11 +++++++++++ public/how-it-works.html | 20 +++++++------------- public/mcp.html | 2 +- public/runtime-core.html | 1 + public/schemas.html | 2 +- public/stack-proof-demo.html | 2 +- public/verify-badge-demo.html | 3 ++- public/verifyagent.html | 1 + 11 files changed, 37 insertions(+), 32 deletions(-) create mode 100644 public/canonical-receipts.html create mode 100644 public/runtime-core.html create mode 100644 public/verifyagent.html diff --git a/public/ambient-verification.html b/public/ambient-verification.html index d3a0600..c358835 100644 --- a/public/ambient-verification.html +++ b/public/ambient-verification.html @@ -39,6 +39,7 @@ CommandLayerCommandLayer
Home + Protocol Capabilities Verifier SDK @@ -56,12 +57,12 @@

Ambient Machine-Action Verification

-

Four verification surfaces

+

Live today

-

Webhook Auto-Verification

For backend automation, use webhook consumers to verify receipts on arrival.

Example/planned path: examples/webhook-auto-verify

+

SDK/runtime verification

Use SDK and runtime verifier flows in applications that verify receipts on delivery.

@@ -97,6 +98,10 @@

Developer use cases

+
+

Planned

+
+

Careful wording

- + diff --git a/public/api.html b/public/api.html index 0440ea6..2d8d7e8 100644 --- a/public/api.html +++ b/public/api.html @@ -1,7 +1,5 @@ -CommandLayer API Reference
API

API surfaces for verifiable agent actions.

CommandLayer APIs expose runtime signing, verification, and verifier surfaces.

Runtime endpoints

  • GET /health
  • POST /verify
  • POST /trust-verification/{verb}/v1.0.0

MCP endpoint

  • GET https://mcp.commandlayer.org/health
  • POST https://mcp.commandlayer.org/mcp

Website verifier surfaces

  • /verify.html
  • /api/verify (public route; treat production canonical status cautiously until separately validated)
  • /api/agents/verifyagent

Example curl

curl -X POST https://runtime.commandlayer.org/trust-verification/sign/v1.0.0 \ +CommandLayer API Index

API Index

Response states

  • VALID / VERIFIED
  • INVALID
  • TRANSPORT_ERROR

Example runtime sign

curl -X POST https://runtime.commandlayer.org/trust-verification/sign/v1.0.0 \
   -H "Content-Type: application/json" \
-  -d '{"agent":"runtime.commandlayer.eth","action":"sign","payload":{}}'
-
-curl -X POST https://runtime.commandlayer.org/verify \
+  -d '{"payload":{"subject":"demo"}}'

Example runtime verify

curl -X POST https://runtime.commandlayer.org/verify \
   -H "Content-Type: application/json" \
-  -d '{"receipt":{}}'

Response states

  • VALID / VERIFIED
  • INVALID
  • TRANSPORT_ERROR

Trust boundary

  • Runtime signs.
  • Verifier validates.
  • MCP bridges.
  • SDK wraps.
Try VerifierView Production Proof
+ -d '{"receipt":{}}'

Note: website /api/verify route behavior should be treated cautiously unless separately validated for canonical production semantics.

\ No newline at end of file diff --git a/public/canonical-receipts.html b/public/canonical-receipts.html new file mode 100644 index 0000000..7c5cf58 --- /dev/null +++ b/public/canonical-receipts.html @@ -0,0 +1 @@ +Canonical Receipts | CommandLayer
Canonical Receipts

Canonical receipts anchor trust verification.

Receipt model

A CommandLayer receipt is a structured action result with a canonical metadata.proof envelope for deterministic verification.

  • canonicalization: json.sorted_keys.v1
  • hash algorithm: SHA-256
  • signature algorithm: Ed25519
  • signature key id: vC4WbcNoq2znSCiQ
  • signer id: runtime.commandlayer.eth

Verification semantics

Tampering invalidates proof because both hash and signature checks fail.

Schema-valid alone is not verified.

diff --git a/public/claim.html b/public/claim.html index 8d302e9..b2ec985 100644 --- a/public/claim.html +++ b/public/claim.html @@ -157,6 +157,17 @@

Pricing / tier preview

+ +
+

Namespace activation pricing

+
+

Starter Namespace

Free / application review

+

Builder Namespace

$99/mo

+

Protocol Partner

$499/mo

+

Enterprise / Registry

Custom

+
+

Pricing is for namespace and capability activation services, not ownership sale of ENS names unless explicitly stated. Introductory pricing; final terms depend on namespace, usage, and integration scope.

+

Protocol notes

CLAS receipts are network-agnostic.

ENS and ERC-8004 can assist discovery and identity, but they are not required for receipt verification.

diff --git a/public/how-it-works.html b/public/how-it-works.html index c69e896..0766bd1 100644 --- a/public/how-it-works.html +++ b/public/how-it-works.html @@ -42,6 +42,7 @@ CommandLayerCommandLayer
Home + Protocol Capabilities Verifier SDK @@ -90,10 +91,10 @@

Layer-by-layer explanation

Capability discovery

Trust Verification capabilities are discoverable through a capability catalog and discovery records. ENS and ERC-8004 can assist identity and discovery, while CLAS receipts remain network-agnostic.

@@ -123,14 +124,7 @@

Related links

- + diff --git a/public/mcp.html b/public/mcp.html index 7a359ee..b2599a3 100644 --- a/public/mcp.html +++ b/public/mcp.html @@ -1,4 +1,4 @@ -CommandLayer MCP Bridge
MCP Bridge

MCP bridges agent clients to CommandLayer runtime actions.

MCP exposes CommandLayer tools to MCP clients, but MCP is a bridge, not the signer.

View Production ProofExplore Capabilities

What MCP does

  • Exposes tools.
  • Forwards payloads to runtime.
  • Blocks private key fields.
  • Returns runtime receipts.
  • Supports automatic verification workflows.

What MCP does not do

  • Does not hold private keys.
  • Does not sign receipts.
  • Is not the trust root.
  • Does not make schema-valid equal verified.

Transport

GET  https://mcp.commandlayer.org/health
+CommandLayer MCP Bridge
MCP Bridge
MCP bridges agent clients to CommandLayer runtime actions.
MCP exposes CommandLayer tools to MCP clients, but MCP is a bridge, not the signer.
View Production ProofExplore Capabilities
What MCP does
  • Exposes tools.
  • Forwards payloads to runtime.
  • Blocks private key fields.
  • Returns runtime receipts.
  • Supports automatic verification workflows.
What MCP does not do
  • Does not hold private keys.
  • Does not sign receipts.
  • Is not the trust root.
  • Does not make schema-valid equal verified.
Trust boundary
The proof model is identical whether an action is called through MCP or direct HTTP. MCP changes transport, not trust. Runtime still signs. Verifier still validates. MCP does not hold keys.
Transport
GET  https://mcp.commandlayer.org/health
 POST https://mcp.commandlayer.org/mcp
 
 Note: /mcp is POST-only MCP transport. GET /mcp is not expected to work.
Tools
clas.trust-verification.verify
diff --git a/public/runtime-core.html b/public/runtime-core.html
new file mode 100644
index 0000000..b2aedc0
--- /dev/null
+++ b/public/runtime-core.html
@@ -0,0 +1 @@
+runtime-core | CommandLayer
runtime-core
runtime-core is the crypto truth layer.
canonicalize → hash → sign → verify
runtime-core powers deterministic proof creation and verification for runtime, verifier, and SDK integrations.
It is not a runtime, not MCP, and not a marketplace.
https://github.com/commandlayer

diff --git a/public/schemas.html b/public/schemas.html
index 85d45fb..1f1b7c0 100644
--- a/public/schemas.html
+++ b/public/schemas.html
@@ -1 +1 @@
-CommandLayer Schemas
Schemas
Schemas define structure. Proof verifies truth.
Schemas define the shape of requests and receipts. They support verification, but schema-valid alone is not verified.
Explore CapabilitiesWrap Your Agent
Schema types
  • Request schemas
  • Receipt schemas
  • Shared proof envelope
  • Capability schemas
  • Agent cards / discovery metadata
Canonical proof envelope
  • metadata.proof.canonicalization
  • metadata.proof.hash.alg
  • metadata.proof.hash.value
  • metadata.proof.signature.alg
  • metadata.proof.signature.value
  • metadata.proof.signature.kid
  • metadata.proof.signer_id
Important warning
Schema-valid alone is not verified. Verification requires hash and signature checks.
Capability schema model
  • Trust Verification v1 first.
  • Future capability families later.

+CommandLayer Schema Hub
Schema Hub
CLAS Trust Verification schemas define request and receipt structure, including a shared canonical proof envelope.
Canonical proof fields
  • metadata.proof.canonicalization
  • metadata.proof.hash.alg
  • metadata.proof.hash.value
  • metadata.proof.signature.alg
  • metadata.proof.signature.value
  • metadata.proof.signature.kid
  • metadata.proof.signer_id
Expected schema paths
  • /schemas/v1.1.0/_shared/receipt.base.schema.json
  • /schemas/v1.1.0/commercial/verify/receipts/verify.receipt.schema.json
  • /public/schemas/v1.1.0/_shared/receipt.base.schema.json
IPFS CIDs
  • CID_SCHEMAS_V1 = bafybeieoynknzalaojwpzjzjy77kpnfe4kla5io7jbfnmyu7w7vyvuljpq
  • CID_CARDS_COMMONS = bafybeiha4diqc32lsvjsg3hl6zvtwn4qcfryze7zxf4d36av7tvur6lwfe
Warning: Schema-valid alone is not verified. Verification requires hash and signature checks.

\ No newline at end of file
diff --git a/public/stack-proof-demo.html b/public/stack-proof-demo.html
index 8dccc6b..d1c8a1e 100644
--- a/public/stack-proof-demo.html
+++ b/public/stack-proof-demo.html
@@ -134,7 +134,7 @@ 
Signed. Verified. Tamper-invalidated.

   

 
   
Run the proof locally
cd mcp-server
-export COMMANDLAYER_RUNTIME_URL=https://runtime-production-214f.up.railway.app
+export COMMANDLAYER_RUNTIME_URL=https://runtime.commandlayer.org
 unset COMMANDLAYER_VERIFY_URL
 unset COMMANDLAYER_VERIFY_PATH
 npm run e2e:local
diff --git a/public/verify-badge-demo.html b/public/verify-badge-demo.html
index 2561c31..deb6bbc 100644
--- a/public/verify-badge-demo.html
+++ b/public/verify-badge-demo.html
@@ -18,6 +18,7 @@
       CommandLayerCommandLayer
       

         Home
+        Protocol
         Capabilities
         Verifier
         SDK
@@ -56,7 +57,7 @@ 
Embed snippet

         

       

     
-  

+

What the badge checks

  • fetches or receives a receipt
  • submits receipt to verifier
  • displays VALID / INVALID / TRANSPORT_ERROR
  • does not itself sign receipts
  • does not make schema-valid equal verified
  • relies on hash and signature verification

Demo receipts: valid sample, tampered sample.

diff --git a/public/verifyagent.html b/public/verifyagent.html new file mode 100644 index 0000000..de6a366 --- /dev/null +++ b/public/verifyagent.html @@ -0,0 +1 @@ +VerifyAgent | CommandLayer
Verifier Surface

VerifyAgent verifies receipts by proof, not claim.

What VerifyAgent checks

  • metadata.proof canonical envelope fields.
  • Canonical hash using json.sorted_keys.v1 and SHA-256.
  • Ed25519 signature validity.
  • Signer identity and key id (runtime.commandlayer.eth, vC4WbcNoq2znSCiQ).
  • Supported Trust Verification verb.

Verifier surfaces

Manual verifier: /verify.html
Production proof: /stack-proof-demo.html

Trust boundary

VerifyAgent verifies. Runtime signs. MCP bridges transport. SDK wraps actions.