Originally published on hexisteme notes.
I run a small fleet of AI agents that check each other's work — one agent drafts a conclusion, another (usually from a different model vendor) is asked to poke holes in it.
For a while I had two house rules governing that setup, and I followed both of them literally, and they turned out to say opposite things.
Rule one, in my notes on verification schemas: a single dissenting reviewer's opinion cannot be used to settle whether a conclusion is right.
You need more than one independent voice before you act on an objection.
Rule two, in my notes on picking verification tools, and echoed in my own global defaults: in ordinary (non-load-bearing) situations, one cross-vendor review pass is enough.
Don't multiply reviewers past that.
Read together, those two rules can't both survive contact with a real decision.
If a single reviewer flags a problem, do I need a second reviewer before I'm allowed to change anything (rule one), or was the first pass already sufficient (rule two)?
Every time I actually had a single dissenting opinion in hand, I had to pick which rule to obey, and I had no principled way to choose.
Either verification bloats to two-plus passes every single time, quietly violating the "one pass is enough" default, or I quietly ignore the first rule and act on one voice anyway.
Both outcomes are silent failures of the same kind: a rule sitting in the document that isn't actually being followed.
The bug wasn't in either number My first instinct was to argue about the numbers — is one enough, or do you need two?
That's the wrong axis.
When I actually traced where the two rules came from, they were answering different questions that I had been treating as one question. "Can I collect a dissenting opinion from a single source?" and "can I act on that dissenting opinion?" are not the same operation, and there's no reason they should require the same quorum.
Collecting an objection is cheap and low-stakes.
One reviewer, one pass, is completely sufficient — because the output isn't a decision yet, it's a hypothesis. "This might be wrong for reason X" is worth having on the table even if the reviewer who raised it is wrong.
You lose almost nothing by admitting a candidate objection into evidence.
Turning that objection into an actual verdict — reversing a conclusion, rewriting a rule, shipping a fix — is a different act entirely, and it's the one that needs a real quorum.
My rulebook now states it as two rows instead of one blurred rule: collection needs one leg and produces a hypothesis, not a verdict; a verdict needs either a ground-truth check (the original source text, the actual code, an actual measurement) or convergence from two genuinely independent lineages, and only then is it something you're allowed to act on.
The part that actually resolved the contradiction was realizing the second thing a verdict needs doesn't have to be a second reviewer at all.
It can be a fact check against the primary source.
My rule for picking verification tools already separated "ways to close uncertainty" into three distinct axes — checking against ground truth, running the claim through a computational engine, or getting an independent model family's opinion — and treats a panel-style review as a step that generates and disperses candidate objections, not as one of those three closing axes itself.
Once I saw the second axis as "ground truth OR a second lineage" rather than "a second lineage, full stop," a single dissenting leg plus a ground-truth check is two axes.
It settles the peacetime default and the settle-requires-more-than-one-voice rule at the same time, because they were never actually about the same step.
Why a confirmed single voice beat two that agreed There's a reason a ground-truth-confirmed single objection can outrank two reviewers nodding in agreement, and it isn't intuitive at first: two reviewers agreeing on the same wrong idea is exactly what you'd expect if they were trained on