Why it wins
It doesn't just talk — it builds.
Ask for working software and the council designs it, delegates the authoring, runs the tests, and fixes its own failures before anything ships.
CORE BET
🧠
Genuinely different minds, not an echo chamber
Every panelist writes in parallel, blind to the others. You get N real perspectives instead of N models agreeing with whoever spoke first — the diversity-of-intelligence bet the whole system is built on. Every contribution is tagged with the exact model that wrote it.
🗳️
Best-of-N you can trust
Candidates that crash on load are disqualified — judging by reading is blind to runtime failure. Only files that actually run get scored blindly. 🏆 winner ships unchanged.
🤝
Specialists on demand
The coder codes, the researcher researches, the critic checks. The lead recruits talents live — 🤝 code_generator ← claude — and a failed delegation is retried before falling back.
🛠️
Builds close their own loop
When RUNTESTS fails, the lead sees the real output and repairs the code — up to 3 attempts, all before promotion. A build ships passing its own tests, or says exactly why it couldn't.
HONEST BY DESIGN
🧾
Receipts, not vibes
Everything is bounded — budgets, wall-clock, depth caps — and everything is logged to a JSONL reasoning trail. Rotation is automatic but consent-gated: after three CONTINUE rounds it pauses and asks you. A run that fails says so honestly instead of dressing up a failure as an answer.