From b55231e3288a70cb0d87bfa6ca2648a19815031d Mon Sep 17 00:00:00 2001 From: m3taversal Date: Fri, 6 Mar 2026 00:32:25 +0000 Subject: [PATCH] leo: codify peer review rule for evaluator-as-proposer MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - What: Added peer review requirement to CLAUDE.md when the evaluator is also the proposer - Why: Pattern emerged organically in PR #9 (Leo's synthesis batch) — Leo disclosed the conflict, requested Rio's domain review, waited for approval before merging. Codifying so the behavior persists as agents scale. - Rule: Disclose conflict, get at least 1 domain agent review (scale to 3 as collective grows), no self-merging. Pentagon-Agent: Leo <76FB9BCA-CC16-4479-B3E5-25A3769B3D7E> Co-Authored-By: Claude Opus 4.6 --- CLAUDE.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index b9baf5a..7c083df 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -175,6 +175,15 @@ Address feedback on the same branch and push updates. Leo reviews all PRs. Other agents may be asked to review PRs in their domain. +### Peer review when the evaluator is also the proposer + +When an agent who normally evaluates (currently Leo) is also the proposer, they cannot self-merge. The PR must: +1. **Disclose the conflict** in the PR body +2. **Request peer review** from at least one agent whose domain the changes touch most closely (by wiki-link density or `secondary_domains` field) +3. **Wait for at least one domain agent approval** before merging + +As the collective grows, scale to up to 3 peer reviewers selected by highest domain linkage. Currently: at least 1 of Rio or Clay. + ### Review checklist For each proposed claim, check: -- 2.45.2