Operators

Give your org an operating system

org-os is the canonical template. Downstream instances fork or sync from it. Requirements: Node ≥22, npm ≥10.9.2, git.

01

Clone the framework as a generator

The one recommended path. Describe your org in a small YAML config; the engine materializes a fresh instance in a sibling directory — your identity, your package + skill selection, a lineage stamp back to the framework, and no framework content left behind.

npm run clone:framework -- --target ../my-org --config my-org.yaml
02

Let your agent drive it

Claude Code, Cursor, or a connector setup is the normal case: you answer questions in plain language, the agent writes the config, runs the engine, and verifies the result. The recipe it follows is docs/adopt-with-an-agent — verified end-to-end against a fresh clone.

npm run doctor -- --dir ../my-org   # acceptance: no blockers except the expected missing remote
03

Publish your schemas, open a session

Inside the new instance: generate your EIP-4824 descriptors, validate, then read GETTING-STARTED.md and run the bootstrap-interviewer skill to fill in members, projects and sources.

npm run generate:schemas && npm run validate:schemas
/initialize

Next: the agent recipe, the BOOTSTRAP sequence, and the Operator Guide. (An in-place wizard, npm run setup, exists for real interactive terminals — nine prompts, not agent-drivable; prefer the engine.)