Skip to content

AGENTS.md

Latest commit

 

History

History
53 lines (47 loc) · 3.91 KB

AGENTS.md

File metadata and controls

53 lines (47 loc) · 3.91 KB
Raw

Thinloop Routing Kernel

config/routing-kernel.json is the normative routing source. This block is generated by node scripts/sync-routing-kernel.mjs; edit the source, not this copy.

  1. Next：只问状态、阻塞或下一步 → scd-next：只读实时 Issue、PR、Initiative DAG 与验收证据，给出唯一下一行动。
  2. QuickDev：清晰的单交付仓库变更 → scd-quickdev：以一个中文 Issue 为边界实现和验证；直接证据与独立验收通过后才合并，高风险动作仍需明确批准。
  3. Discovery：产品结果仍不清楚，尤其是从 0 到 1 或多个相互依赖的产品决定 → scd-discovery。
  4. Project：已批准的稳定结果包含多个可独立验证交付 → scd-project：只建立并校验 Initiative、Delivery Issues 与依赖 DAG，不执行实现。
  5. Execute：已批准 Initiative 需要开始、继续、恢复或完成 → scd-execute：选择当前安全 READY 波次，每个 Issue 进入隔离 QuickDev 通道。
  6. Reengineering：跨语言、框架、架构、存储或运行时替换，或项目级大幅重构 → scd-reengineering：先固定来源、兼容性与切换门，再消费批准的 DAG。
  7. 条件设计：只有真实复杂度需要时才加入设计：重要 Web 体验 → scd-uiux；领域、系统或共享接口边界 → scd-architecture。
  8. 显式治理：只有用户明确要求时才调用治理与个人能力：scd-maintenance、scd-knowledge、scd-evolve、scd-interview；普通开发不得自动触发。

Thinloop Delivery Default

After an in-scope Thinloop development change passes its required engineering verification, do not ask whether to finish delivery. Complete the ordinary delivery sequence:

  1. create or update the governing GitHub Issue;
  2. commit only the task-owned changes and push the issue branch;
  3. create a pull request with acceptance evidence and wait for required checks;
  4. audit the complete Issue, including acceptance evidence, task disposition, exact diff, and delivery state; for page changes, require real browser interaction and visual evidence rather than API or build-only proof;
  5. delegate acceptance to a separate fresh-context verification subagent that returns PASS, FAIL, or BLOCKED with direct evidence, then merge only after PASS;
  6. synchronize local main and confirm it contains the accepted change;
  7. after every Thinloop delivery, check installed ZCode, Claude Code and Codex against merged main, including repository-only changes: refresh Thinloop payload or source links whenever the version or content has drifted, then verify version, complete skills and each platform's supported hooks. Do not install missing clients or upgrade host apps. Missing required evidence stays UNVERIFIED and must be reported, never treated as PASS;
  8. for other supported installed agents, refresh when the merged change modifies installed payload or runtime behavior. WorkBuddy alone remains exempt (verification.mode: skip). Preserve unrelated plugin settings, data and authentication; use native update commands/APIs and recheck their result;
  9. close the Issue only after the merged version, required installation state, and all three completion-audit ledgers still support PASS.

This standing instruction authorizes ordinary task-local GitHub writes, task-branch cleanup, and local Thinloop reinstall work. It does not authorize unrelated changes, weakening repository protections, production deployment, live destructive migration, authentication or authorization changes, payments, secrets, privacy or compliance changes, or another irreversible high-risk action. Stop for explicit approval when one of those boundaries applies or when credentials, required checks, or repository protections block safe completion.