Skip to content

Meta-agent search over plugin workflows: design + working proof of concept - #20

Draft
JoshuaOliphant wants to merge 4 commits into
mainfrom
claude/meta-agent-workflow-design-rg6v6y
Draft

Meta-agent search over plugin workflows: design + working proof of concept#20
JoshuaOliphant wants to merge 4 commits into
mainfrom
claude/meta-agent-workflow-design-rg6v6y

Conversation

@JoshuaOliphant

@JoshuaOliphant JoshuaOliphant commented Jul 8, 2026

Copy link
Copy Markdown
Owner

Summary

Design and working proof of concept for ADAS/AFlow-style meta-agent search over this marketplace's own workflow artifacts (docs/meta-agent-search-design.md, §8 has first results).

Design

  • Cites both papers: ADAS (Hu et al., arXiv 2408.08435) for the archive + meta-agent + self-refine outer shape; AFlow (Zhang et al., arXiv 2410.10762, ICLR 2025) for sample-efficiency mechanisms — operator library, experience backpropagation, soft mixed selection, convergence stop.
  • Three search tiers by evaluation cost: trigger descriptions (seconds/cents), skill procedures (minutes), full autonomous-sdlc workflow variants in disposable worktrees (hours) — with "run Architect/Builder on cheaper models at equal success rate" as the headline tier-3 objective.
  • Goodhart defenses: committed dev/holdout split, guardrail metrics, immutable runner/judge, winners promoted only via human-reviewed PR.

Proof of concept (phases 1–2, implemented)

  • evals/run_trigger_eval.py — the fitness function: batched haiku judge via the claude CLI, deterministic hash-based dev/holdout split, balanced accuracy + separate FP rate, autoloop-convention METRIC output. Also useful standalone as a regression check for hand-edited descriptions. CI-safe tests (stub judge, no network); pyproject testpaths now includes evals/.
  • meta/ — the search harness: program.md loop protocol (operators, soft-mixed parent selection, two self-refine passes, experience records, convergence stop) and immutable auto/run.sh candidate runner. verification-stack-eval.json is deliberately unmapped — it targeted the skill removed by the v2 loop redesign.
  • Baseline (candidate-000): 4 of 8 descriptions already saturated at dev 1.0; headroom on beads-workflow (.833), compound-retrieve (.850), bdd-generate (.917), mochi-creator (.929, the only over-triggerer).
  • First searched candidate (candidate-001): add-trigger-phrases on beads-workflow — adding the bd lifecycle surfaces the incumbent omitted (stats/health, sync/dolt sharing, ready-work) took dev .833 → 1.0 and holdout .875 → 1.0, FP 0. The holdout jump says it's a real win, not dev overfit. Cost: 56 → 99 description words.

No plugin versions bumped — everything lives at repo level (evals/, meta/, docs); plugins/ is untouched (promoting candidate-001 into the plugin would be a separate reviewed change). scripts/check_all.py passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_015Dexou9QTmNb2Vf8XhedgQ

claude added 4 commits July 8, 2026 05:40
Applies ADAS-style meta-agent search to the marketplace's own artifacts:
skill descriptions (tier 1, scored against evals/*.json), skill procedures
(tier 2), and full autonomous-sdlc workflow variants (tier 3). Reuses
autoloop's runner/METRIC/ledger conventions with a population archive
instead of single-file hill-climbing, and phases the work so the cheap
trigger-description search debugs the machinery before any hours-long
SDLC benchmark runs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015Dexou9QTmNb2Vf8XhedgQ
The linked paper is AFlow (Zhang et al., ICLR 2025), a sibling of ADAS
that searches code-represented workflows with MCTS. Corrects the
citation to cover both papers and adopts AFlow's sample-efficiency
mechanisms: a per-tier operator library constraining mutations,
experience backpropagation in each candidate's meta.json, soft
uniform+score-weighted selection, convergence-based early stop, ~5x
evaluation runs, and dollar-weighted cost in the tier-3 fitness — with
'run Architect/Builder on cheaper models at equal success rate' promoted
to the headline tier-3 objective, mirroring AFlow's cost result.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015Dexou9QTmNb2Vf8XhedgQ
evals/run_trigger_eval.py scores a skill description against its
evals/*-eval.json fixture via a batched haiku judge (claude CLI),
with a deterministic hash-based dev/holdout split, balanced accuracy
as the primary metric, false-positive rate reported separately, and
autoloop-convention METRIC output. Supports --description-file so
candidate genomes score without touching plugins/.

meta/ holds the search harness: program.md (loop protocol with
operators, soft-mixed parent selection, two self-refine passes,
experience records, convergence stop) and the immutable auto/run.sh
candidate runner. verification-stack-eval.json is deliberately
unmapped — it targeted the skill removed in the v2 loop redesign.

Tests use a stub judge only (no network); pyproject testpaths now
includes evals/ so they run in CI.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015Dexou9QTmNb2Vf8XhedgQ
… -> 1.0

Baseline (candidate-000) scores all 8 mapped descriptions: 4 already
saturated at dev 1.0, headroom on beads-workflow (.833),
compound-retrieve (.850), bdd-generate (.917), mochi-creator (.929).

Candidate-001 applies add-trigger-phrases to beads-workflow, adding the
bd lifecycle surfaces the incumbent omitted (stats/project health,
sync/dolt remote sharing, ready/unblocked work). Result: dev .833 -> 1.0
AND holdout .875 -> 1.0 with zero false positives, at the cost of a
56 -> 99 word description. Archived with lineage, operator, and
experience record; design doc gains a section 8 with PoC results.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015Dexou9QTmNb2Vf8XhedgQ
@JoshuaOliphant JoshuaOliphant changed the title Design doc: meta-agent search (ADAS) over plugin workflows Meta-agent search over plugin workflows: design + working proof of concept Jul 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants