▸ repositories
Repositories
CommandLayer is one system with separate repos for separate layers. Read this page top-down: VerifyAgent.eth is the public verifier for CommandLayer receipts, Commons/Commercial define contracts, Runtime executes actions, SDK supports developers, Agent Cards handle discovery, and Commercial infrastructure handles scale.
Protocol stack
Read the repositories in stack order: contract first, discovery second, execution third, then SDK and publishing surfaces that mirror and explain that core.
The canonical open contract layer. Defines the public request and receipt schemas, the minimum verifiable receipt, and the baseline semantics builders should target first.
MITCanonical contractIPFS-pinned
The commerce-oriented contract extension. Adds payment, checkout, fulfillment, shipping, and verification schemas while preserving the Commons-first model and portable receipt discipline.
Apache-2.0Economic contractsPortable schemas
The discovery and identity layer. Agent Cards say who an agent is, which verbs and versions it supports, and where clients should route requests without redefining the contract itself.
Apache-2.0Identity + routingIPFS-pinned
Public verifier for CommandLayer receipts. Anyone can paste a receipt and verify whether it is valid or tampered with.
MITPublic verifierCommons trust layer
Client-side tooling for integrating the stack. Helps applications discover agents, call pinned contract surfaces, and verify receipts without blurring contract data with runtime metadata.
see repoTypeScript + PythonClient tooling
Shared execution and verification primitives. Holds schema validation, canonical serialization, signing, and receipt-proof helpers used by runtime implementations.
Execution primitivesShared library
The commerce-oriented execution surface. Runs Commercial flows against the public contracts and may attach proof, trace, and orchestration metadata around the canonical receipts it returns.
Commercial executionx402-aligned
The public explanation and publishing surface. Hosts the website, docs hub, quickstart, demos, and mirrored schema publishing paths that make the rest of the stack legible to builders.
Docs + demoPublishing surface
Architecture rule
Do not read these repos as separate products. They are one stack with a strict boundary.
Canonical receipt first
VerifyAgent.eth answers “Is this receipt valid?” Runtime answers “What action ran?” SDK answers “How do developers create and verify receipts?” Agent Cards answer “What is this agent and what can it do?” Commercial answers “How do teams run and verify at scale?”