/agents

This site has a machine face.

Endpoints

Generated from the seeds' own artifacts, never hand-copied. If it isn't in a seed's repository, it isn't here.

/agents/catalogue.json: Catalogued products: identity, category, description, version, clause count and links to available source instructions and artifacts.
/agents/seeds/<id>/seed.json: The manifest. Capabilities mapped to contract clauses, declared externals with reasons, extension points, limits, operating cost, deploy requirements.
/agents/seeds/<id>/CONTRACT.md: What the product does, clause by clause, with stable IDs; coverage and unmet requirements are recorded separately.
/agents/seeds/<id>/BASELINE.md: Declared baseline requirements. Read the edition’s actual scope, changes and verification evidence.
/agents/seeds/<id>/AGENTS.md: Instructions for the owner’s agent: authoritative source, requirements, intentional differences and actual checks. Legacy products may retain separate consumer guidance.
/llms.txt: A short plain-text index of all of the above.

Edition commands

Read the selected edition's README and operating description for its actual install, development, verification and deployment commands. The examples below apply to Lily, Orbit, Lamp and Ferry source checkouts.

# describe declared operations without provisioning node scripts/operations.mjs describe # inspect selected source and its lock node scripts/edition-authoring/cli.mjs inspect node scripts/edition-authoring/cli.mjs check node scripts/edition-authoring/cli.mjs changes

# in an edition checkout, using its frozen lock pnpm install --frozen-lockfile pnpm dev # follow that edition's README for verification and deployment # source integrity does not establish product acceptance

For source updates, extract publisher/component /new/baseline opens a verified retained baseline and compare publisher/component /clean/candidate reports incoming changes. Run these through the same authoring CLI. Release creates a Git repository and a separate receipt file; distribute both and use receipt /path/to/release.json in a later clone. Your agent chooses how to preserve your requirements.

Written for your agent

Use the edition’s guidance and requirements to change any source, including UI, core logic, schema and infrastructure. Hooks are conveniences. A deeply diverged edition can still receive useful upstream fixes adapted by its agent.

Verified, not vibes

Run the edition’s actual checks and inspect coverage gaps. A passing suite or clean merge alone does not prove that owner intent and existing-data transitions survive.

Nothing calls home

Independent operation is a product requirement. Consult the selected release’s baseline and evidence for verified behavior; catalogue metadata alone does not establish it.