CommandLayer is licensed to keep the contract surface public and the execution surface investable. Commons and Commercial define the contract. Agent Cards define discovery. Runtime defines execution.
CommandLayer never charges for semantics, schemas, or validation. Monetization lives in runtime execution, guarantees, routing, and commercial service surfaces.
The contract layer remains inspectable, versioned, and portable. Discovery remains open because Agent Cards are protocol descriptors, not private lock-in. Execution value accrues where operational cost, risk, and guarantees actually exist.
This is not open-core theater. The protocol surface remains public so builders can validate, route, and interoperate without permission. Commercial value shows up where execution has cost, policy, and guarantee overhead.
| Component | License | What it means |
|---|---|---|
| CommonsCanonical contract layer | MIT | Public-goods request and receipt schemas. Anyone can implement, validate, mirror, or extend integrations against Commons without asking permission. |
| CommercialEconomic contract layer | Apache-2.0 | Economic verbs remain public and portable. Builders can use the same schemas across processors, marketplaces, and runtimes while keeping patent posture clean. |
| Agent CardsDiscovery layer | Apache-2.0 | Open descriptors for identity, discovery, and routing. Clients should be able to discover capabilities without scraping private docs. |
| RuntimeExecution layer | BUSL-1.1 | Reference runtime code can be inspected and used under its terms, while commercial deployment, guarantees, routing logic, and managed execution remain monetizable service surfaces. |
Standards only work when the semantic layer is public. If schemas are paywalled, builders cannot validate independently, judges cannot trust the protocol claim, and portability collapses.
CommandLayer keeps the meaning layer open so multiple runtimes can compete on execution without fragmenting the contract.