From e4200bd7c22be477579ac5dbd35c11b838c0ef87 Mon Sep 17 00:00:00 2001 From: sehkone Date: Mon, 10 Aug 2026 11:10:46 +0900 Subject: [PATCH] Update shared instruction blocks to 0.2.0 Synced from aicers/agent-instructions at 0.2.0, which the drift check is now pinned to. Do not edit the marked blocks in this repository; change them upstream, tag a release, and re-run the sync. 0.2.0 adds the agentcoop block, which explains the pipeline that turns this repository's issues into pull requests. A new block needs its marker pair placed by hand -- nothing upstream can decide where in this file a block belongs -- so the pair sits after the workflow block, and the apply filled it in the same commit. Splitting the two would have left the drift check red in between, rejecting a marker the pin file does not yet list. --- .agents/instructions.toml | 4 ++-- AGENTS.md | 28 ++++++++++++++++++++++++++++ 2 files changed, 30 insertions(+), 2 deletions(-) diff --git a/.agents/instructions.toml b/.agents/instructions.toml index c5836dbb..1eb7b02c 100644 --- a/.agents/instructions.toml +++ b/.agents/instructions.toml @@ -2,5 +2,5 @@ # it is on, and the shared blocks it has. Its drift check reads this file, # and its apply job rewrites it. Which blocks a repository should carry is # decided upstream in repos.json, not here. -ref = "0.1.4" -blocks = ["workflow", "rust", "changelog"] +ref = "0.2.0" +blocks = ["workflow", "agentcoop", "rust", "changelog"] diff --git a/AGENTS.md b/AGENTS.md index e60f5d6e..cdce694f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -73,6 +73,34 @@ before generating code. descriptions or issue comments. + +## AgentCoop + +AgentCoop is the pipeline this organization runs over its GitHub issues, +so its vocabulary turns up in issue bodies and pull request comments +here — and an agent working in this repository may itself be running +inside it. + +- Two agents do the work. The **author** (Agent A) produces, the + **reviewer** (Agent B) reviews independently, and the two converge + through structured feedback; a deadlock escalates to a human rather + than resolving silently. They are usually different models. +- **Implementation** turns one issue into a pull request with green CI. + The author implements it in a dedicated worktree, self-checks, opens + the pull request, and drives CI to green; the reviewer then reviews + the pushed branch and the two iterate in the pull request's comment + thread, tagged `[Author Round N]` and `[Reviewer Round N]`, until it + is approved. +- **Design** shapes work into issues: an RFC file becomes an umbrella + issue over a sub-issue tree, or a single issue is refined — and split + only when one pull request cannot cover it. +- **Verification** holds a completed issue against the diffs that closed + it and files follow-up sub-issues for whatever it did not deliver. +- The issue is the contract, and the only input a run is given. A human + writes that seed and merges the result; AgentCoop invents no + requirement and asks no clarifying question along the way. + + ## Coding standards (Rust)