CommandLayer Logo
CommandLayer Semantic verb & schema layer for agents
Roadmap

Where the semantic layer is going

From 10 core Commons verbs today to a complete semantic framework for the agent economy. CommandLayer ships a small, stable language first, then grows Commercial flows, Agent Cards, and Runtime endpoints in lockstep with x402 and ERC-8004 adoption.

Protocol v1.0.0
Commons v1.0.0 · Commercial v1.0.0 · Agent Cards v1.0.0
Runtime layer · coming online
Schemas are permanently free — economics live in the execution layer, not in the verb language.

How to read this roadmap

The focus is simple: ship a trusted semantic layer first, then expand it as x402 rails and ERC-8004 registries come online. The cards below show what’s already shipped, what’s being wired now, and what’s staged next.

Done In flight Planned

Lead with semantics

Commons v1.0.0 locks down a small, stable verb set and strict schemas — the language contract that agents can rely on regardless of which runtime or rail executes them.

Complete the stack, don’t compete

x402 moves money. ERC-8004 helps you find agents. CommandLayer defines what they do. The roadmap assumes those standards win and makes the missing semantic layer inevitable.

Schemas free, economics in execution

The verb language and JSON Schemas are public goods. Long-term economics sit in Runtime endpoints, routing, and guarantees — not in locking up schema access.

Phase 1 — Foundations of the semantic layer

Lock down the core language: a small Commons set, strict schemas, pinned artifacts, and framing that makes CommandLayer the default semantic layer on top of x402 and ERC-8004.

Foundations — Commons v1.0.0

Done

10 universal Commons verbs with request/receipt schemas, shared primitives, and strict validation.

  • Verbs: analyze, classify, summarize, parse, format, clean, convert, describe, explain, fetch.
  • JSON Schema 2020-12, strict mode, no ad-hoc drift.
  • MIT-licensed and treated as semantic public goods.

Immutable protocol artifacts

Done

Make the language durable: deterministic IDs, pinned CIDs, and repeatable builds so clients can trust what they resolve.

  • Canonical $id layout for all schemas.
  • Manifest + SHA-256 checksums for clients and registries.
  • CI validation before anything is tagged as v1.0.0.

Semantic layer framing

In flight

Make it explicit to standards bodies and ecosystem partners what CommandLayer does and does not do.

  • Positioning: “x402 moves money, ERC-8004 finds agents, CommandLayer defines what they do.”
  • Docs and site copy aligned to “semantic verb & schema layer for agents”.
  • Clear separation between Commons (MIT), Commercial (Apache-2.0), and Runtime (BUSL).

Phase 2 — Agent Cards, Commercial verbs & expanding Commons

Once the initial Commons surface is stable, Phase 2 extends the protocol into identity, economic flows, and a richer semantic language for agents.

Agent Cards v1.0.0

Done

Bind ENS names to verbs, schema versions, and entrypoints so agents become discoverable and composable across runtimes and infra.

  • Canonical JSON documents served from /agent-cards/v1.0.0/.
  • Fields for identity, capabilities, limits, and one or more x402 entry URIs.
  • Compatible with ERC-8004-style discovery flows and third-party registries.

Commercial verbs v1.0.0

Done

Define the first Commercial verbs focused on money movement and fulfillment, separate from Commons semantics.

  • Initial set: authorize, checkout, purchase, ship, verify.
  • Apache-2.0 schemas with clear economic intent; MIT Commons stays the neutral baseline.
  • Schema patterns aligned with x402 payment envelopes and receipts.

Expanding the Commons surface

Planned

Grow beyond the initial 10 verbs into richer workflows, data operations, and reasoning primitives while preserving backwards compatibility.

  • Workflow: notify, reply, schedule.
  • Data ops: filter, visualize, optimize.
  • Cognition & state: reason, update, store — all versioned and schema-first.

Phase 3 — Runtime & ecosystem integrations

With Commons, Commercial, and Agent Cards in place, Phase 3 brings the Runtime layer online and integrates with wallets, processors, and registries — all reusing the same free schemas.

Runtime v1.0.0

In flight

Execution endpoints for Commons and Commercial verbs. Where paid flows, routing decisions, and guarantees live — all on top of the same semantic contracts.

  • BUSL-licensed Runtime repo for providers who want stronger guarantees around uptime, ordering, and receipts.
  • x402-compatible HTTP endpoints that accept CommandLayer *.request payloads and return structured receipts.
  • No new schema surface — Runtime reuses the free verb language defined in Commons and Commercial.

Registries & discovery

Planned

Make it trivial for ERC-8004 registries and third-party indexes to treat CommandLayer as the default semantic contract.

  • Reference “semantic-first” registry patterns over Agent Cards and schema versions.
  • Example queries: “all summarize agents on mainnet with v1.0.0 schemas”.
  • Guidance for wallets, hubs, and platforms to surface verbs as first-class objects.

Ecosystem playbook

Planned

Document how infra providers, API vendors, and builders plug into the semantic layer without fragmenting it.

  • Integration guides for x402 providers and execution hubs.
  • Patterns for logging, tracing, and receipts that align with Commons/Commercial schemas.
  • Clear story for how economic value accrues to Runtime & endpoints while schemas remain free.

Where builders fit in

You don’t need to wait for “all phases” to land. One verb, one Agent Card, or one example agent is enough to plug into the semantic layer today.

  • Pick a Commons verb (e.g. summarize) and wire your agent to its *.request / *.receipt schemas.
  • Validate payloads against the pinned, free schemas using your JSON Schema validator of choice.
  • Describe your agent with an Agent Card so ERC-8004-style registries and clients can discover and route to it.
  • As x402 rails and Runtime endpoints come online, you keep the same contracts — only the execution layer changes.

Start with one verb. As the ecosystem grows around x402 and ERC-8004, your agents are already speaking the shared language that the agent economy will use.