We compare more than persuasive model output. We study results a team can verify and accept: git diff, tests, scope compliance, manual fixes, and total cost.
Real cases · controlled experiments · independent verification
Why this matters
The agent reported success. Code changed. Tests passed. Requirements were met without scope drift. A human or independent check accepted the result—these events are not interchangeable.
VOLY studies where task meaning is lost, where the executor falls short, and where the verification process fails to detect it.
Signals from the field
“Don’t prompt Claude. Build a system that prompts itself.” Attention is moving from a single chat to agent systems.
VOLYWe test conditions where specialization and independent verification produce a measurable gain—not whether multi-agent is popular.
Claude Code users discuss usage limits and manual workarounds: multiple accounts, proxy CLIs, and alternative harnesses.
VOLYThis supports the Job: finish a task without quota failure, with transparent fallback and total result cost.
Native Managed Agents already introduce session budgets; basic orchestration is rapidly becoming a platform capability.
VOLYVOLY differentiates on cross-agent task budgets across tools and fallback boundaries—not roles alone.
Large multi-agent systems increase the need for observable environments, bounded roles, and verifiable episodes.
VOLYCollect trustworthy episodes and role metrics first; defer self-play until the evidence is reliable.
Metrics are snapshots of public activity when checked. They provide market context, not VOLY research results.
Choose your depth
If you have two minutes, start with the survey. To inspect the claims, open the methodology or the test bank.