/evolve — Goal-Driven Compounding Loop

Cross-vendor analog: Anthropic Managed Agents Outcomes (May 2026). Both close the loop "agent runs → grader scores against a rubric → agent retries"; AgentOps does it locally against any model.

Measure what's wrong. Fix the worst thing. Measure again. Compound.

V2 command surface: keep the name evolve. Use ao evolve for the terminal-native loop. It is the top-level operator entrypoint for ao rpi loop --supervisor, preserving the old /evolve concept while reusing the v2 RPI loop engine.

Operator cadence: post-mortem finished work, analyze the current repo state, select or create the next highest-value work item, let /rpi handle research, planning, pre-mortem, implementation, and validation, then harvest follow-ups and repeat until a kill switch, max-cycle cap, regression breaker, or real dormancy stops the run.

Always-on autonomous loop over /rpi. Work selection order:

1. Harvested .agents/rpi/next-work.jsonl work (freshest concrete follow-up)
2. Open ready beads work (bd ready)