Skip to content

Update shared instruction blocks to 0.2.1 #813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sehkone wants to merge 1 commit into from
+30 −2
Closed

Update shared instruction blocks to 0.2.1 #813

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .agents/instructions.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"]
28 changes: 28 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,34 @@ before generating code.
descriptions or issue comments.
<!-- END shared:workflow -->

<!-- BEGIN shared:agentcoop -->
## 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.
<!-- END shared:agentcoop -->

<!-- BEGIN shared:rust -->
## Coding standards (Rust)

Expand Down
Loading