---

标题：“智能操作系统” doc_type：“索引” 版本：“1.0.2” 日期：“2026-09-23” 朗：“恩-美” 所有者：“Agentic-OS” frontmatter_contract：“必修” load_policy：“点播”

特工-奥斯

代理开发生命周期（ADLC）机束：一个可克隆的多工作树、多代理工作区 将工作落到规范分支的开发。Node.js 20.11+，Git，npm;零运行时依赖。

本页是仓库的入口点，并引导到所有者。它没有定义任何需求、设计或 每个人都与下面列出的所有者同住。

安装并验证

在任何仓库绑定命令之前，提交仓库的.agentic-os.json配置文件。 换了别人分叉从前叉指南开始。

每日循环

complete 报告源集成和关闭，同时保留通道。清理是单独的， 显式操作：通过--bundle传递精确认证的清理包并确认停止 拥有--stopped的作者。仅靠配置文件设置永远不会触发线路隔离。

[npm run status、npm run reap和[agentic-os completion status --ref= 是只读的 诊断。开始-工作流，释放-工作流，

---

title: “Agentic OS” doc_type: “Index” version: “1.0.2” 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

The reviewed .agentic-os.json profile must be committed before setup, doctor, or lane work. Consumer repositories also commit the exact AOS package pin and lock. AOS’s own checkout already includes its profile. Forking under a different owner starts at the fork guide.

Default source loop

npm run lane --  --write= [--plan=]
# edit only in the printed worktree
npm run land -- --message="feat: ..."
# finish the protected PR checks/review and merge
npm run release:common -- complete --ref=

complete waits for and records exact source integration, then reports the lane’s remaining ADLC actions. An open or blocked result keeps the lane open; follow its named next action. Source integration does not imply delivery or cleanup. For a batch, use npm run release:common -- complete-adlc --worktrees= on demand. Solo maintainers use a PR and green CI with required approvals set to zero, bypass off, and no self-approval. Load deployment, rollback, recovery, cleanup, diagnostics, or extra validation only when the lane scope or its reported next action requires them. Each effect retains its owner’s authority and receipt.

First-time profile and hook setup is in START-WORKFLOW. RELEASE-WORKFLOW owns source closeout; ADLC guidelines own lifecycle rules. Diagnostics and specialized workflows stay on demand. Use the deploy workflow only for a delivery-bound lane.

Owners