A builder on r/AI_Agents wrote the cleanest argument for AI councils this week without ever using the word. Buried in a thread about agent loops was a single line: an agent can never review its own work, because it will overlook the same mistakes it just made. Review, he argued, has to be mechanical — tests — or it has to come from an independent agent.
That's the whole thesis, arrived at from the bottom up, by someone with nothing to sell.
The same blind spot is doing the grading
Most AI workflows still resolve to one model checking itself. You ask a model for an answer, then you ask the same model — or the same model with a sterner prompt — whether the answer is right. It says yes. It almost always says yes. The blind spot that produced the error is the same blind spot now reading the work, and a blind spot can't see itself by trying harder.
This matters more as the tasks get more autonomous. When a model drafts a contract clause, narrows a dosage range, or commits a trade, "are you sure?" is not a control. It's the model grading its own exam. A wrong answer that passed its own review ships looking exactly like a reviewed one — same confidence, same polish, none of the catch.
The fix isn't a smarter model
It is not a more confident answer either. It is a different model — one that doesn't share the first's training, priors, or failure modes, and is therefore structurally able to see what the first one can't.
One model has an opinion. A second, different model has a check. That gap — the distance between two minds that fail in different places — is the entire value. Add a reviewer that thinks exactly like the author and you've added a rubber stamp with extra steps.
The research has been circling this for a month. Even when you build a dedicated critic agent into a debate, its confidence turns out to be the least reliable signal in the room — the auditor's certainty tracks its actual reasoning quality far worse than the builder's does (AUROC 0.634 versus 0.804 in one June study). The lesson isn't "add a critic and trust it." It's that the reviewer has to be genuinely independent, and you have to read its reasoning, not its certainty.
Orchestration routes work. A council argues a question.
Here's where the vocabulary is quietly splitting, and it's worth getting right.
Aravind Srinivas recently described Perplexity Computer as a team of agents using up to 20 different AI models, orchestrating across models, tools, and files. That's real, and it's useful — but it is a logistics system. It takes a task, breaks it into pieces, and routes each piece to the model best suited to do it. Twenty models, one assembly line, one output.
That is not the same machine as a council. A council doesn't divide the question up; it puts the same question to multiple models and makes them argue it. The output isn't a finished task — it's a map of where they agreed, where they split, and why. One system is built to get work done. The other is built to catch the work that's wrong.
Both are "multi-model." Only one puts an independent reviewer on the answer.
Routing can quietly remove the reviewer
This is the trap inside the orchestration wave. When you route each subtask to its best-fit specialist and stitch the pieces back together, there's no point in the pipeline where a second mind looks at the whole thing and asks whether it holds. Salesforce shipped multi-agent orchestration to enterprises in June. The sharpest critique wasn't about any single agent — it was that routing-and-merging leaves a seam no one reviews. Efficiency went up. The independent check disappeared.
For a workflow — file this expense, draft this reply — that's fine. For a decision that's expensive to get wrong, it's the self-review fallacy wearing twenty hats instead of one.
The reviewer has to fail differently
The reason a council beats a louder single model is almost boring once you see it: the second reader has to be capable of a different mistake. Same architecture, same training data, same blind spot — and your "review" is the original answer in a fresh font. Different vendor, different training, different priors — and the disagreement, when it shows up, is the system telling you exactly where to look.
That's why the interesting moment in a council is never the consensus. It's the split. Two models confidently disagreeing is not a bug to be averaged away. It's the signal that the question was harder than one confident answer let on.
The builder on Reddit and the researchers are converging on the same sentence from opposite directions: you cannot grade your own exam, and neither can your AI. The answer isn't a model that's surer of itself. It's a second mind that doesn't share the first one's blind spot — and a structure that shows you the disagreement instead of hiding it.
That's what a council is. You can watch one argue a question live, no signup. Try it free — shingik.ai.