Skip to content

README.md

Latest commit

 

History

History
77 lines (51 loc) · 3.6 KB

README.md

File metadata and controls

77 lines (51 loc) · 3.6 KB

commandlayer-org

Public website and proof surface for CommandLayer.

CommandLayer is a trust layer for autonomous agent execution:

  • Commons is the canonical open contract layer and current-line builder default.
  • Commercial is a separate commerce-oriented contract line that remains payment-aware.
  • Agent Cards handle discovery and routing across both lines.
  • Runtime executes contracts and may attach proof metadata without redefining the canonical receipt.

Documentation authority

This repo intentionally has two documentation surfaces with different roles:

  • Primary public docs: the website pages in public/, especially public/docs.html, public/commons.html, public/commercial.html, public/runtime.html, and public/repositories.html
  • Secondary repo reference: the concise Markdown notes in docs/ for contributors and reviewers

Those surfaces explain CommandLayer, but they do not own the protocol itself.

Source-of-truth hierarchy

  1. Protocol repos own protocol truth. protocol-commons, protocol-commercial, and agent-cards define the canonical contract, extension, and discovery artifacts.
  2. Published schema artifacts in this repo are mirrors/publishing outputs. They should match the canonical upstream protocol repos exactly and should never become an independent authority.
  3. Runtime repos own execution behavior, not contract meaning. runtime-core and runtime implementations may validate, serialize, sign, and prove receipts, but they must not redefine schema semantics.
  4. SDKs own client ergonomics, not protocol truth. They consume pinned artifacts and verification rules from the protocol layer.
  5. Website copy is the public explanation layer. It should teach the stack faithfully, but if it drifts from the protocol repos, the protocol repos win and the site must be updated to mirror them.

If drift is discovered, fix the canonical protocol/discovery repo first when the contract itself is wrong, then immediately update this repo's published schemas and site copy so the public mirror becomes accurate again.

What this repo contains

  • public/ — static HTML pages, schema publishing paths, Agent Card examples, and demo assets
  • api/ — Vercel serverless endpoints used by the live demo and composer
  • docs/ — short repo-side reference notes that complement the public site docs

This repo should teach one architectural story consistently:

  1. Commons v1.1.0 is the active current line and the minimum verifiable receipt model.
  2. Commercial v1.1.0 is a separate payment-aware extension for economic flows.
  3. Agent Cards define discovery and routing without changing contract semantics.
  4. Runtime executes the contract and may add proof, trace, or orchestration metadata around the receipt.

Version policy

  • Commons: v1.1.0 is the current builder target across the site and demo composer.
  • Commercial: v1.1.0 is the current commercial release across docs, schemas, demos, and runtime flows.
  • Agent Cards: v1.1.0 is the current card format across the registry, manifests, and linked examples.
  • Runtime: execution layer, not a schema version line.
  • Compatibility: published older paths remain live for verification and pinned integrations.

Local development

Install

npm install

Run locally

vercel dev

If you use another local workflow, keep the site static-first and preserve published URL paths.

Deployment note

Published URLs are part of the protocol surface.

Do not rename or move stable public paths for:

  • docs pages
  • schema URLs
  • Agent Card URLs
  • demo surfaces