This week a thread on r/AI_Agents settled an argument the field has been having for a month. The question was blunt: does all the "harness engineering" talk mean the industry is walking back "the model does everything"? The top reply put it in four words. "Agent = Model + Harness." The model is the brain. The harness is everything around it — the tools, the prompts, the retries, the state, and the verifiers that check the work. Then the line that matters, from another builder: "more gains coming from the harness side than the LLM."
That is the council thesis with a new coat of paint. Reliability was never a property of the model. It is a property of what you wrap the model in.
The harness almost everyone builds wraps one model
Here is the part the thread got right and then walked past. If reliability lives in the harness, look at the harness people are actually building. It wraps a single model. Claude Code wraps Claude. Cursor wraps whatever you point it at. The verifier inside that harness — the thing deciding whether the output is any good — is usually the same model that produced the output, or a close cousin of it.
A different builder on the same subreddit named the failure the same week, without meaning to. His coding agent reads its own code back, decides it looks right, and calls it done. It never ran the thing. It never clicked the button it built. The reviewer and the author are the same mind. And a model's confidence does not track whether it is right — an auditor agent's confidence scored an AUROC of 0.634 against its own reasoning quality in one June paper (arXiv:2606.10296), barely above a coin flip. A harness with one model has a careful verification layer pointed straight at its own blind spot.
Independence is the whole game
A harness is good when the checker is independent of the thing being checked. That is it. And the cheapest way to buy independence is not a cleverer verification prompt — it is a different model. Two models trained on different data, with different failure modes, break in different places. When one is confidently wrong, the other is often just confused enough to object.
So the most reliable harness is not one brain wrapped in scaffolding. It is a harness that runs a few brains and makes them check each other. That has a name too. It is a council.
What makes a council a good harness, not just a bigger one
The difference isn't the model count. It's the structure.
Decorrelated members. A second model is only a second opinion if it fails differently. A checker that agrees with the author every time is not independence — it is an echo. The value is in the disagreement, which means the members have to be genuinely different, not the same base model run at three temperatures.
Anonymized peer review. Models defer to famous names the way people do. Strip the byline and a model argues with the claim instead of the reputation. Randomize who speaks first, because in a debate, position gets mistaken for merit.
A verifier aimed at the real failure. Generic "double-check this" is weak. A verifier calibrated to where a task actually breaks — legal AI that omits versus legal AI that invents — beats a generic one even when the two systems hallucinate at the same rate (arXiv:2606.18021).
A chairman that resolves disagreement instead of averaging it. The point of running three models is not to take a vote. It is to have something read the split and decide what to do with it. Averaging throws away the exact signal you paid for — the minority report.
"Not sure yet" as a real output. A harness that can only say PASS or FAIL will confidently say PASS on the questions it should escalate. A council can return "we don't agree, send it to a human," and that verdict is often the most useful one.
The honest part
More brains is not automatically better. A badly structured council loses to one well-prompted model — DeliberationBench found best-single-model selection beating every deliberation protocol 82.5% to 13.8% (arXiv:2601.08835). Throw three models in a room with no roles, no independence, and no chairman, and you get a more expensive way to be wrong. The win is not the head count. It is the structure. Which is exactly what the harness crowd is saying — the gains are in the scaffolding, not the model — carried one model further than most of them have taken it.
Some in the thread called "harness engineering" a rebrand of tooling we have had for three years. Fair. But the rebrand does real work, because it moves the reliability question off the model and onto the architecture. Once that move is common ground, the next question writes itself: if the harness is where reliability lives, why does yours only run one model?
The harness was the right idea. The builders naming it this week are describing a council without saying the word — a structured layer around the model where the checking happens. They stopped one model short. A council is the harness that stopped trusting a single brain and put the disagreement on the table instead of hiding it behind one confident answer.
Run the hard question through a few models and watch them argue it out. That part is the demo.
Try it free — no signup. shingik.ai