teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 18 Projects Releases Packages Wiki Activity Actions 2

leo: codify synthesis multi-agent review rule

Browse source 
- What: synthesis claims require at least 2 domain agent reviews, selected by
  domain expertise relevance or knowledge base impact. 3+ domains = all affected
  agents review.
- Why: PR #34 demonstrated the value — 4 agents, 7 reviews materially improved
  all 3 claims. Codifying what worked.
- Where: CLAUDE.md evaluator workflow section + skills/synthesize.md step 4

Pentagon-Agent: Leo <76FB9BCA-CC16-4479-B3E5-25A3769B3D7E>
This commit is contained in:
m3taversal 2026-03-06 08:42:20 -07:00 committed by GitHub
parent a8e8359d9c
commit 599488493a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 14 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
CLAUDE.md
View file

@ -207,6 +207,15 @@ When an agent who normally evaluates (currently Leo) is also the proposer, they
As the collective grows, scale to up to 3 peer reviewers selected by highest domain linkage. Currently: at least 1 of Rio or Clay. As the collective grows, scale to up to 3 peer reviewers selected by highest domain linkage. Currently: at least 1 of Rio or Clay.
### Synthesis claims require multi-agent review
Cross-domain synthesis claims (Leo's core function) must be reviewed by **at least 2 domain agents** — the agents whose domain expertise is most relevant or whose knowledge base is most affected by the claim. Selection criteria:
1. **Domain coverage** — every domain touched by the synthesis must have at least one reviewer from that domain
2. **Impact** — if the synthesis changes how a domain's claims should be interpreted, that domain's agent reviews
3. **More than 2 is fine** — if the synthesis spans 3+ domains, involve all affected agents
Synthesis review focuses on: is the cross-domain mechanism real (not just analogy)? Would domain experts in both fields recognize the connection? Does the synthesis add insight neither domain could produce alone?
### Review checklist ### Review checklist
For each proposed claim, check: For each proposed claim, check:

9
skills/synthesize.md
View file

@ -40,9 +40,10 @@ If the connection passes the test, create a new claim:
### Step 4: Route for evaluation ### Step 4: Route for evaluation
Synthesis claims get special evaluation routing: Synthesis claims get special evaluation routing:
- Leo evaluates (always — this is Leo's core function) - Leo proposes (always — this is Leo's core function) and cannot self-merge
- Both contributing domain agents evaluate - **At least 2 domain agents** must review — selected by domain expertise relevance or knowledge base impact (see CLAUDE.md "Synthesis claims require multi-agent review")
- The evaluation focuses on: is the mechanism real? Would domain experts agree? - If the synthesis spans 3+ domains, involve all affected agents
- The evaluation focuses on: is the mechanism real? Would domain experts agree? Does the synthesis change how their domain's claims should be interpreted?
### Step 5: Update transition landscape ### Step 5: Update transition landscape
@ -61,5 +62,5 @@ If the synthesis changes Leo's slope reading for any domain:
## Quality Gate ## Quality Gate
- Every synthesis articulates a specific mechanism (not just "these are related") - Every synthesis articulates a specific mechanism (not just "these are related")
- Both contributing domain agents validate the connection - At least 2 contributing domain agents validate the connection
- The synthesis adds value neither domain could produce alone - The synthesis adds value neither domain could produce alone