51 lines (35 loc) · 1.61 KB

Onboarding — CommandLayer Agent Cards

Start here

v1.1.0 is the current line. The repository enforces one canonical publication model:

schema bindings resolve through https://commandlayer.org/schemas/...
the legacy duplicate schema field is removed
commons cards use https://runtime.commandlayer.org/execute
commercial cards use x402://<agent>/<verb>/v1.1.0

Canonical current-line surfaces:

agents/v1.1.0/
schemas/v1.1.0/
meta/manifest.json
.well-known/
checksums.txt

Archival-only surfaces:

agents/v1.0.0/
schemas/v1.0.0/
dist-pin/agent-cards/v1.0.0/

Product boundaries

Agent Cards describe identity metadata, capability metadata, endpoint discovery, supported verbs/actions, and signer/receipt metadata references.
CommandLayer receipts provide signed execution proof.
VerifyAgent is an external verifier for receipt validity checks.
CommandLayer Commercial provides hosted runtime, paid API, x402, indexing, dashboards, and support.

For public receipt verification, see https://github.com/commandlayer/verifyagent.

Editing rules

Keep $schema, $id, version, schemas, and entry aligned.
Use only canonical hosted schema URLs under commandlayer.org.
Never reintroduce the legacy duplicate schema field.
Commons entries must stay on the runtime endpoint.
Commercial entries must stay on the x402 route pattern.

Supported workflow

npm run generate:dist-pin
node scripts/generate-checksums.mjs
npm run validate
npm run validate:release

Historical scripts under scripts/archive/ are preserved only for migration reference.