---

title: “Agentic OS” doc_type: “Index” version: “1.0.1” date: “2026-09-23” lang: “en-US” owner: “agentic-os” frontmatter_contract: “required” load_policy: “on-demand”

agentic-os

The Agent Development Lifecycle (ADLC) harness: a clonable workspace for multi-worktree, multi-agent development that lands work on a canonical branch. Node.js 20.11+, Git, npm; zero runtime dependencies.

This page is the repository entry point and routes to owners. It defines no requirement, design, or decision of its own — each one lives with the owner named below.

Install and verify

git clone https://github.com/huijoohwee/agentic-os.git
cd agentic-os
npm install
npm run setup     # select packaged hooks; refuses to clobber an existing hook manager
npm run doctor    # report harness and remote drift, change nothing
npm run check     # affected behavior and packaging, plus readiness, doc and module budgets

Commit the repository’s .agentic-os.json profile before any repository-bound command. Forking under a different owner starts at the fork guide.

Daily loop

npm run release:common --help                                  # the full operator flow
npm run release:common -- start  --write=
npm run release:common -- publish --message="feat: ..."
npm run release:common -- complete --ref=               # wait for merge, then close and retire the lane when local evidence is sufficient
npm run release:common -- complete --ref= --bundle= --stopped

complete without a bundle now uses the exact local merged-review and required-check evidence to quarantine the retained lane when the profile-governed local cleanup path is sufficient. Use --bundle and --stopped when the exact authenticated cleanup plan is required instead.

npm run status, npm run reap, and agentic-os completion status --ref= are the read-only diagnostics. START-WORKFLOW, RELEASE-WORKFLOW, and the deploy workflow route the universal lifecycle grammar that the ADLC guidelines own; cleanup is globally required but repo-local in mechanics inside those stages. The user cookbook owns the smallest path for a direct edit.

Owners

Portable, host-registered skills ship beside the runtime: Canvas and ESP-IDF. Both are instruction assets read without a Node.js runtime.

Reference implementation — the profile selects a Git repository adapter and a GitHub provider adapter, and agentic-canvas-os, agentic-commerce-os, and agentic-graph are the composed consumers. The adapters are swappable and the consumer set is this project’s own choice; accepted revisions are pinned in composition-source-lock.json.

Consuming as a package

Pin an exact 40-hex source revision rather than a floating name, so the audited governance bytes are identifiable. Consumers reference the packaged evaluator instead of copying it:

npm --prefix node_modules/agentic-os run evals
node bin/agentic-os.mjs pin --consumer=/absolute/root    # report consumer pin drift

The package root exposes the four provider-neutral request operations — claim, continue, integrate, retire — under GOVERNANCE, which owns their records and limits.

Governing artifact

PRD-TAD-ADR-ADLC-PIPELINE-001, at the revision its PRD-TAD-ADR-MVP-GTM frontmatter declares, is the single governing artifact for scope, candidate, integration, release, and runtime evidence. Precedence runs from that artifact, to its named composition owner, to derived indexes, to navigation and command documents including this one. Raise a conflict at the owner, not here.