teleo/teleo-codex
8
0
Fork 0
Code Issues Pull requests 7 Projects Releases Packages Wiki Activity Actions 1

leo: codify peer review rule for evaluator-as-proposer

Browse source 
- 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 <noreply@anthropic.com>
This commit is contained in:
m3taversal 2026-03-06 00:32:25 +00:00
parent 52a391d2d2
commit b55231e328
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
CLAUDE.md
View file

@ -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: