Free cookie consent management tool by TermsFeed Generator

The Shared Ancestor Problem

Five agent instances score between 0.83 and 1.00 on a convergent proof task, averaging 0.967, a pool that looks, by simple headcount, like it is performing near its ceiling. Run it through outlier-resistant selection instead and the diversity-adjusted quality signal drops to 0.400, roughly forty cents on the dollar. Five high scores were not five independent confirmations. They were one answer, restated five times by instances drawn from the same training distribution. The algorithm built to reject a corrupted minority did exactly what it was built to do: it found the disagreement and discarded it, on a task where the disagreement was the only genuine signal left in the pool, first measured in Independence Illusion.

That number is from a post on this blog published in July 2026. A different post on this blog, published in September 2026, proved something else [1] [2] : a reasoner whose self-trust is modeled as provability cannot derive a general reflection schema about its own soundness without collapsing into unconditional assertion. That holds for any system satisfying three specific derivability conditions, regardless of how reliable that system actually is.

Neither post cites the other. Both were computing the same requirement, and neither one derived the requirement itself, only one instance of it.

One Requirement, Computed Twice

Strip the vocabulary each series built for its own purpose and the underlying claim is identical: a verification signal only counts as a check if it draws on something the thing it checks could not also have corrupted. Independence Illusion proved this for committees: Condorcet’s jury theorem, Byzantine fault tolerance, and the Universal Scalability Law all price redundancy the same way. A committee of language-model instances drawn from overlapping training data fails the independence assumption by default, agreeing confidently for the same reason rather than disagreeing for different ones. Loeb’s theorem, applied to a single provability-based reasoner, proves the same requirement fails for a different reason entirely. The reasoner’s only available derivation apparatus is the one thing that could be wrong, so there is no computation inside the same system that avoids depending on it.

Both are instances of one question: when a system checks itself, or is checked by something built alongside it, what has to be true of the checker for the check to mean anything? The first draft of this post answered that question with one unified criterion and got it wrong in a specific, instructive way: it treated Loeb’s theorem as though it were a third instance of the committee mechanism, correlated failure at the limit where correlation reaches one. It is not. The two mechanisms are different in kind, not degree, and the difference is load-bearing enough that stating it precisely is most of this post’s actual content.

Definition 7 -- Common-Cause Check Validity: what a verification signal actually needs

Definition 7 (Common-Cause Check Validity). For a property , let be the specific process whose malfunction constitutes ’s failure mode. Let be the event that the object-level output is wrong, and the event that a verification signal ’s verdict about that output is wrong. is a valid check on to the degree that two conditions hold:

Physical translation. Independence without power certifies a coin flip: unconditionally independent of everything, and unconditionally useless. Power without independence certifies an echo. A checksum computed from the same original data as the payload it verifies satisfies both: it shares an ancestor with the payload, the source data, but not with the specific failure mode being checked for, corruption introduced in a transmission channel the checksum’s own computation never passes through. That is the whole distinction. Sharing an origin is not the same as sharing a failure mode, and only the second one breaks a check.

    
    %%{init: {'theme': 'neutral'}}%%
flowchart LR
    classDef term fill:none,stroke:#333,stroke-width:2px;
    classDef bad fill:none,stroke:#c0392b,stroke-width:2px;
    classDef good fill:none,stroke:#2980b9,stroke-width:2px;
    subgraph "Shares Φ"
        I1["Inputs"]:::term --> P1["Φ"]:::term
        P1 --> O1["Object-level output
E_O"]:::term P1 --> V1["Verifier V
E_V"]:::bad end subgraph "Avoids Φ" I2["Inputs"]:::term --> P2["Φ"]:::term P2 --> O2["Object-level output
E_O"]:::term I2 --> G["Ground-truth channel G"]:::term G --> V2["Verifier V
E_V"]:::good end
Figure 0: the same inputs feed both checkers in both graphs, so reading the same data is never what breaks a check. What differs is whether V's own path back to the inputs passes through Φ. On the left it does, failing Definition 7's independence condition, and E_V inherits whatever E_O inherits from Φ. On the right, V reaches the inputs through a separate channel G that never touches Φ, satisfying independence: E_V's dependence on Φ is severed even though V and O still share an ultimate origin.

This is a synthesis of two established tools, not a new theorem. The first is Pearl’s causal graphs, specifically the question of whether a shared ancestor creates a dependency between two variables [3] . The second is the standard signal-detection pairing of false-negative and false-positive rates from hypothesis testing. Definition 7 is this post’s own construction, assembled from those two tools to state precisely what both series’ own results were computing separately, not transcribed from a citation for either half.

One scoping note the first draft of this criterion got wrong and is worth stating explicitly, because the error is instructive. A verifier checking a single object-level output is not a special case of an -voter committee at . Independence Illusion’s own committee theorem restricts explicitly to odd , since an even pool admits an exact tie majority rule cannot resolve. The relational structure differs besides: symmetric peers estimating the same ground truth in parallel, versus an asymmetric pipeline where is built specifically to inspect an artifact already produced. The honest relationship is structural similarity, not formal reduction: both price a correlation between error events, and neither theorem is a special case of the other.

Definition 7 states independence and power as two separate conditions. They are not two independently satisfiable requirements, and the exact relationship between them is provable rather than merely plausible.

Proposition 6 (Power Margin Equals Correlation at Matched Base Rates). [Layer 1: Bound] Let be the object-level error rate and the checker’s own flag rate, with the correlation between and ’s fail verdict, not between and itself: , whether ’s verdict is wrong, is a false positive or a false negative depending on which side of it lands, and is not the single Bernoulli variable this identity is stated over. The power margin is exactly When the checker’s flag rate matches the object-level error rate, , this reduces to exactly.

Mathematical proof: the identity, verified against two numeric cases

The setup. Let and , Bernoulli variables with , , matching Definition 7’s own and exactly, both stated over ’s verdict, not over . Their correlation, by the standard definition for two binary variables, is , which pins down the joint probability:

The two rates. . Symmetrically, .

The identity. Subtracting the two: The bracketed term reduces algebraically to exactly, giving the identity stated above. This holds with equality for any joint distribution of two Bernoulli variables, by construction of , not as an approximation.

Checked against two numeric cases. At , : the joint probability works out to , giving , , and , matching exactly as the matched-rate case predicts. At , , : the general formula gives , matching a direct computation from the joint probability to four decimal places.

Physical translation. A checker whose own flag rate happens to match the base error rate it is checking, and whose correlation with the true error is exactly zero, has exactly zero power margin: it is the coin flip Definition 7’s own Physical Translation already named, now derived rather than asserted. Zero correlation with and positive discriminative power cannot coexist in that setting. The two trade off directly, at a rate this proposition makes exact rather than qualitative.

This sharpens what Definition 7’s independence condition actually forbids, and what it does not. It does not forbid correlation with itself, since Proposition 6 shows power requires exactly that. It forbids the specific correlation that runs through .

A checker built on the ground-truth channel in Figure 0 earns its correlation with honestly, by actually tracking the truth. A checker sharing earns the identical numerical correlation for free, by inheriting the same mistake. Proposition 6’s identity cannot tell the two apart on its own: it prices how much correlation power needs, not where that correlation is allowed to come from. Supplying the second half is Definition 7’s whole job. That is why “independent” in Definition 7 means independent of specifically, and was never a demand for independence from outright.

What Diversity Actually Buys, and What It Cannot

A checksum genuinely achieves independence, because the specific defect it screens for happens after the checksum was computed. Most real verification is not that clean, and the reason is not sloppy engineering, but a genuine trade-off, worth stating in the form this blog states every trade-off in: an achievable region, not a paragraph of hedging.

Definition 8 -- The Diversity-Correlation Achievable Region: what independence costs and what it cannot buy

Definition 8 (Diversity-Correlation Achievable Region). Order the layers of substrate that can be diversified between an object-level process and a checker verifying it, from cheapest to most expensive to change: prompt, then model weights, then training corpus, then the ground-truth channel itself. Let be the engineering cost of diversifying through the -th layer in that order, and the resulting correlation between and ’s fail verdict, in Proposition 6’s own sense of , specifically its -mediated component. The achievable region is the set of pairs reachable by diversifying through layer . It has a floor rather than a zero: as diversification exhausts every available layer, where is set by the difficulty landscape of the task itself, a property of the input space no substrate diversification touches.

The qualifier “its -mediated component” in that definition is not a technicality, and skipping it would put Definition 8 at odds with Proposition 6 rather than beside it. Proposition 6 already showed that correlation between and ’s fail verdict is not, on its own, something to drive to zero: it is what power is made of. Driving Definition 8’s toward its floor cannot mean driving that correlation down, on pain of driving power down with it, all the way to the coin flip at .

What diversification actually shrinks is narrower. Total correlation between and ’s fail verdict splits into two sources, matching Figure 0’s two paths. One is a -mediated part, earned for free by inheriting the same mistake makes. The other is a -mediated part, earned honestly by actually tracking the truth. Diversifying through a layer targets only the first. A well-built checker does not diversify its way toward zero total correlation; it diversifies the -component toward while holding, or growing, the -component that Proposition 6 says its power margin actually depends on. The floor this section is about is a floor on the bad half of the correlation, not a ceiling smuggled in against the good half.

Eckhardt and Lee proved something stronger than an empirical observation about sloppy engineering. Even genuinely independently developed checkers generically produce correlated failures whenever task difficulty varies across the input space, because harder inputs make every checker more likely to fail together, regardless of how differently they were built [4] .

This is not a purely theoretical worry. Knight and Leveson ran the experiment directly: twenty-seven independently written, independently tested implementations of the same specification, built by different programming teams with no contact between them. They still failed on a shared subset of inputs far more often than an independence assumption predicts, the empirical floor beneath Eckhardt and Lee’s theoretical one [5] . Littlewood and Miller later showed that deliberately forcing methodological diversity between checkers can push correlation below what independent development alone achieves, but never to zero [6] .

The floor drops. It does not disappear.

None of this is a hypothetical extrapolation to language models. Kim, Garg, Peng, and Garg measured the same failure directly [9] : LLM errors correlate across models far more than an independence assumption predicts. That correlation is severe enough that the naive ensembling and majority-vote aggregation Independence Illusion’s own committee math prices can fail outright, on exactly the pools that look healthiest by headcount.

Measuring that correlation is not the same as auditing it formally, and this post is not first to try the second thing either. A concurrent statistical framework audits behavioral entanglement among black-box LLM judges directly, introducing information-theoretic metrics that predict judge over-endorsement bias [10] . It derives a de-entangled verifier-reweighting scheme along lines close to what Definition 7’s own power condition demands. It stays entirely within the graded, empirical register C1 covers. It never crosses into the unconditional, self-reference register C2 requires.

This post’s own contribution is not the observation that verifiers correlate with what they check. Both works above already establish that. It is stating precisely when that correlation is C1’s kind and when it is C2’s, a distinction neither needed to draw, because neither one crosses into the Löbian half of the question at all.

Applied to a checker built from a language model, the hierarchy of shared, diversifiable ancestors runs in the fixed order Definition 8 already named:

Beyond even the last of these sits one ancestor no amount of substrate diversity touches: the difficulty landscape of the task itself. A checker built on a completely different model still shares that difficulty landscape with the thing it is checking.

That floor is why Definition 7’s independence condition has to be graded, correlation somewhere between 0 and 1, not a binary valid-or-invalid predicate. Independence Illusion’s own correlation-quality function is the working estimator for at the committee scale [7] . It was built for this purpose, and explicitly flagged there as that post’s own interpolation rather than a citation. The multi-agent series’ committee math and the single-agent series’ verifier math are pricing the same , at two different scales. They are not two different quantities that happen to share a symbol.

What This Buys: When to Stop Diversifying

Definition 8 names a floor. It does not say where a deployment should rationally stop short of it, and that question has an actual answer, provable by the same exchange argument Post 4 used for its own stopping rule, not by intuition about “enough diversity.”

Proposition 7 (Diversification Stopping Rule). [Layer 1: Bound] Let be the correlation reduction bought by diversifying through layer , and let be the deployment’s own exchange rate: how much engineering cost it is willing to pay per unit of correlation reduced. Assume returns are diminishing along Definition 8’s own cheapest-to-most-expensive order, non-decreasing in , which holds whenever cost rises at least as fast as marginal benefit falls. Under that assumption, the policy minimizing cost paid plus residual correlation is to diversify through layer exactly when , and stop at the first layer where this fails.

Mathematical proof: the exchange argument, and why the floor is never actually reached

The objective. A deployment choosing how many layers to diversify through is minimizing : total cost paid, plus the residual correlation left, weighted by what avoiding it is actually worth. is cumulative cost through layer .

Why the marginal rule is optimal. Taking layer changes the objective by : it costs and saves in residual correlation. Take the step exactly when this is negative, , and stop otherwise. Any policy that stops before this holds can be improved by taking the next step; any policy that continues past it can be improved by stopping there. Only the threshold rule is not improvable in either direction.

The diminishing-returns assumption is what makes that local argument a global one. It guarantees that once a layer fails the test, every later layer fails it too, so checking layers in the fixed order and stopping at the first failure is the same policy as checking every possible subset and keeping the best. Without it, a bad layer sitting in front of a good one could make skipping ahead beat the threshold rule outright. A layer costing 100 for a return of 0.1 blocks a later layer costing 1 for a return of 2, and stopping at the first failure throws away the second layer’s real value. Definition 8’s own cheapest-to-most-expensive ordering is what the assumption asks the engineering reality to match, not a free simplification.

The exchange argument itself is borrowed from Post 4’s Proposition 5, deliberately reused here, not the same theorem transplanted. Post 4’s Proposition 5 solves a stochastic problem, a reservation value pinned by an integral over a continuous draw distribution. This is a deterministic problem over a small, fixed, ordered set of layers instead. Claiming the diversification rule is a special case of Post 4’s Proposition 5 would repeat exactly the overclaim this post already rejected once for the N=2 committee case. What transfers is the proof technique, an exchange argument showing a threshold is non-improvable in either direction, not the probability model underneath it.

Why the floor is never reached. For any finite , the rule stops at the first layer whose marginal correlation reduction is no longer worth its cost, at some , strictly above the floor. Only as , a deployment willing to pay any cost for any reduction, does the stopping point push to the last available layer, and even there only approaches , because no further layer exists to buy the rest.

Physical translation. This is the same shape as Post 4’s own reservation value, arrived at independently rather than borrowed by force: an ideal a system would reach if the relevant cost were zero, approached but never touched at any positive cost, with the actual stopping point set by what the next unit of improvement is worth to the deployment, not by how close to the ideal it would like to be. Post 4 priced how much search is worth. This prices how much independence is worth. In both cases the honest answer is less than a system would like, for a reason a formula makes precise rather than a shrug.

Proposition 7 is about four discrete layers, in the fixed cheapest-to-most-expensive order Definition 8 named: prompt, model weights, training corpus, the ground-truth channel. The chart below does not illustrate that rule with an invented curve. It runs it, on one fixed set of per-layer cost and correlation-reduction numbers. Drag the exchange rate and watch which layers the rule actually takes, marked directly against , the condition Proposition 7 proves is the whole policy.

100

Figure 1: one fixed cost and correlation-reduction number per layer, Proposition 7's own stopping condition run directly against them. Each bar pair compares that layer's cost to its benefit priced at λ; the rule takes a layer while the cost bar is shorter, and the chart marks the first layer where that stops holding. Drag the slider and watch the stopping point move.

One honesty note this shares with Post 4’s own: is a real number a deployment has to supply, and this post does not derive one. What a unit of residual correlation actually costs, in downstream incidents, wasted retries, or a silently wrong deployment, is exactly the kind of deployment-specific judgment Post 4 already flagged when it declined to collapse token cost, latency, and context loss into one number. The theorem’s shape holds regardless of the number chosen. Only the number itself resists derivation.

Five Properties, Checked Against the Same Requirement

Proposition 8 (Two Structurally Different Reasons a Check Fails). [Layer 2: Fit] Definition 7’s requirement resolves differently across the five properties this series proved, and the difference is not uniform. Four of the five admit an available, if costly, internal pathway around their own worst-case regime. One does not, for any regime.

Working the five cases against Definition 7

Simulation. is the noticing process. A verification signal computed purely from noticed variety, the same channel that produced the original forecast, shares with it: the question “have I noticed enough” is answered using the same resource the forecast itself was built from. An externally-anchored variety estimate, one that does not derive from the same noticed-variety channel, avoids . It still has to actually cover the task’s disturbance variety to satisfy the power condition; independence relocates Ashby’s Law’s own requirement, it does not discharge it.

Abstraction. is the compression step that produced the working summary from the raw data . This is the cleanest case, because the theorem and the graph coincide exactly. By the chain rule, , and because is a deterministic function of , the sequence is a Markov chain for any target whatsoever, so the data processing inequality guarantees no computation on alone can recover the residual . A verifier confined to shares exactly that residual’s absence with the object-level process; one that returns to does not.

This is a hard zero within the -only regime, not a graded correlation the way the other cases are. But the regime itself is a choice: nothing prevents a system from retaining and returning to , at a cost. That escapability is what keeps this case distinct from Awareness, the one case below with no escape at any cost.

Rationality. is not the weighting function alone. A verifier applying an honestly different weight to the same censored evidence stream still shares the actual failure, because the censorship happened in how evidence was sampled, not only in how it was weighed. , the weighting function and the sampling policy together. A valid check needs independence in both: an honest weight applied to dishonestly sampled evidence is still corrupted, and an honest sample dishonestly weighed is too.

Awareness. is the entire derivation apparatus of a provability-based reasoner. This is the case that does not admit an internal escape at any cost, and the reason is worth stating precisely rather than by analogy. Loeb’s theorem, applied to resource-bounded reasoners, proves that no internal derivation, however structured, avoids answering to the same provability predicate the object-level claim itself was derived through. There is no “return to ” move available here the way there is for Abstraction, because there is no analogue of raw data sitting outside the derivation system that a check could return to while remaining an internal derivation.

The obstruction binds regardless of the system’s actual reliability. A hypothetically perfectly sound reasoner, one whose every proof happens to be true, still cannot derive the general reflection schema, because deriving it for every statement would force the reasoner to derive every statement outright, true or false, which is the collapse into unconditional assertion. This is a fact about what is derivable, not about what fails together. There is no error to correlate, because the obstruction does not depend on there being one.

Optimization. Post 4’s Proposition 5 proves the reservation-value threshold rule is exactly optimal given honest inputs. There is no -level failure to check for in Optimization’s own mechanism at all. What still requires external governance is addressed separately below, because it is not an instance of either pattern above.

The pattern that emerges is not “one criterion, five uniform instances.” It is two structurally different reasons a check can fail, and knowing which one applies changes what the fix actually has to be.

C1, the common-cause clause, covers Simulation, Abstraction, and Rationality, plus the multi-agent committee results Independence Illusion already proved. A check fails when its error correlates with the object-level error through a shared . This is graded, escapable at a cost per Definition 8’s achievable region, and it is the reliability-engineering and social-choice mechanism this whole first half of the post has been building: Condorcet, Krum, and the Universal Scalability Law on one side, Ashby’s Law, the data-processing inequality, and the asymmetric-updating divergence result on the other.

C2, the self-reference clause, covers Awareness alone. Loeb’s theorem binds even at zero error rate. There is no failure to correlate, because there is no failure, only a structural fact about what a system can derive about itself. This is binary and unconditional, not graded, and it is the one place either series has a proof rather than a measured or argued-for correlation.

Both clauses cash out as “the check has to live outside the closure of the thing it checks.” They are not the same reason for it, and collapsing them into one mechanism, the way the first draft of this criterion did, would misstate what Loeb’s theorem actually proves.

C1, common-causeC2, self-reference
NatureGraded, correlation Binary, unconditional
Escapable?Yes, at a cost (Definition 8)No, for any regime
GovernsSimulation, Abstraction, Rationality, the multi-agent committee caseAwareness alone
WarrantMeasured or argued-for correlationProof, Loeb’s theorem
Binds at zero error rate?No, independence can reach itYes, unconditionally
Table 1: the two clauses side by side. They share a conclusion, external verification is required, but nothing else on this row, which is the reason collapsing them into one mechanism was the first draft's central defect.
    
    %%{init: {'theme': 'neutral'}}%%
graph LR
    classDef c1graded fill:none,stroke:#2980b9,stroke-width:2px;
    classDef c1hard fill:none,stroke:#2980b9,stroke-width:2px,stroke-dasharray: 4 4;
    classDef c2 fill:none,stroke:#c0392b,stroke-width:2px;
    classDef ic fill:none,stroke:#333,stroke-width:2px;
    C1["C1: common-cause
graded, escapable at a cost"]:::c1graded C2["C2: self-reference
binary, no escape, any regime"]:::c2 IC["Inherited Consequence
corollary of C1/C2, not a clause"]:::ic C1 --- Sim["Simulation"]:::c1graded C1 --- Rat["Rationality"]:::c1graded C1 --- MA["Multi-agent committee
Independence Illusion"]:::c1graded C1 -.-> Abs["Abstraction
hard-zero sub-case, still escapable"]:::c1hard C2 --- Awa["Awareness"]:::c2 IC --- Opt["Optimization"]:::ic
Figure 2: five properties plus the multi-agent case, sorted by which structural pattern actually governs their failure. Solid blue is graded C1. Dashed blue marks Abstraction's hard-zero sub-case, which looks C2-shaped locally but stays escapable, the distinction the next section proves rather than asserts. Red is C2's unconditional bind. Optimization sits outside both, governed by composition rather than a failure of its own.

This lines up with Post 4’s own MAPE-K correspondence at exactly one seam and diverges at another, and both are worth stating rather than left for a reader to notice unprompted. Knowledge’s cross-cutting position there, standing outside the four active stages rather than inside them, is why Awareness stands alone here too: C2 governs a property that answers for the whole loop, not one stage of it, the same structural reason in both posts.

Where the two correspondences part ways is Optimization. Execute sits inside the active pipeline in Post 4’s mapping, on the same footing as Monitor, Analyze, and Plan, which correspond respectively to the three properties C1 does govern here, Simulation, Abstraction, and Rationality. Optimization does not follow its own pipeline neighbors into C1, for the composition reason argued below. Two independently built structural pictures agree exactly on where Awareness sits and disagree on whether Optimization is ordinary, and the disagreement is not a loose end between the posts, it is this section’s own finding, arrived at from a different direction.

One dashed line in that figure is doing more work than it looks like it’s doing.

Is the split actually exhaustive

Checked directly rather than left as an open item, because Abstraction’s own hard zero is a plausible place for a third category to be hiding, the way Awareness turned out to hide C2 in the first place. Confined to computing from alone, the data processing inequality gives exactly zero recoverable information about the discarded residual, a hard fact, not a correlation that interpolates between 0 and 1 the way Simulation’s variety bound and Rationality’s divergence bound do. Within the -only regime, Abstraction looks momentarily Loeb-shaped: absolute, not graded.

It is not a third category, and the reason is the same reason C2 does not reduce to C1 in the other direction. Whether the DPI ’s hard zero applies at all is a choice, not a fact about the system: nothing stops a verifier from retaining and returning to , the re-abstraction remedy this series already prescribes elsewhere, always architecturally available, just costly. Loeb’s theorem has no analogous escape. There is no “just don’t restrict yourself” move available inside the same formal system, because every internal derivation, however structured, answers to the same provability predicate, regardless of how the system is built or reconfigured. The DPI’s absoluteness is conditional on an architectural choice a system could make differently. Loeb’s is not conditional on anything a system could choose.

That is the actual line between C1 and C2: C1 cases have an available, if costly, internal escape route from their own worst-case regime; C2 does not, for any regime. C1 is not internally uniform. It splits further into a hard-zero sub-case escapable by regime change, Abstraction, and continuously-graded sub-cases, Simulation, Rationality, and the multi-agent committee result. Both sub-cases remain on the escapable side of the line that actually separates C1 from C2. The split is exhaustive, not merely unrefuted.

The Case a Verification Criterion Cannot Just File Away

Optimization does not fit either clause, and the honest move is not to file it outside the framework and move on. Individual decisions in a controlled multi-agent study showed strong rational cost-benefit logic with minimal escalation of commitment. The same decision, made through symmetrical peer deliberation among several model instances, escalated to near-universal, about 99.2 percent of runs [8] . Post 4’s own threshold rule did not become unsound between the individual case and the group case. Nothing in the object-level mechanism changed.

Definition 9 -- Inherited Consequence: why a sound mechanism can still need a governor

Definition 9 (Inherited Consequence). [Layer 2: Fit] If a property’s own verification is sound, neither C1 nor C2 applies to its own , but its inputs are drawn from a property where C1 or C2 does apply, the composed system still needs external verification. Not because the downstream property has a hidden failure of its own, but because C1 and C2 failures propagate through data dependencies regardless of how sound each individual computation is.

Physical translation. A stopping rule fed a corrupted probability estimate will stop at the wrong place with perfect internal consistency, because internal consistency was never what was in question. The rule is not the thing that failed. The rule is the thing that faithfully executed on state it had no way to audit, because auditing its own inputs is not an operation its own theorem covers, and was never claimed to be.

Optimization is not a third instance of C1 : forcing it into that clause would misstate what Post 4’s Proposition 5 actually proves, that the rule itself has no shared ancestor with any error, because it has no error of its own to correlate. Nor is it C2 , since nothing about the threshold computation is a self-reference obstruction. And Inherited Consequence is not a peer to C1 and C2 either. Giving it a letter of its own would imply a third reason a property’s own check can fail, when this is precisely the case where it does not: it is a corollary of the two clauses under composition, not a third clause beside them.

That word, corollary, is doing real work and is worth making precise rather than left as a figure of speech. A sound downstream mechanism sounds like it should offer some protection, the way redundancy ordinarily does. It offers no guaranteed protection, and the reason is provable.

Proposition 9 (No Structural Guarantee of Dilution). [Layer 1: Bound] If a downstream mechanism is a deterministic function of its input with no branch, cross-check, or aggregation step that compares that input against anything else, composing through it carries no structural guarantee that an upstream C1 or C2 failure is diluted. Whatever the propagated error rate turns out to be is set by the geometry of the corruption relative to that mechanism’s own mapping, a fact about that specific mapping and that specific corruption, not a property soundness confers. A downstream mechanism cannot be trusted, on soundness alone, to have reduced the error rate an upstream failure introduced, and cannot be assumed to have left that rate exactly as it was either.

Mathematical proof: why soundness downstream neither corrects nor is bound to preserve what it cannot see

The mechanism. Let be the downstream computation, sound in the sense Post 4’s Proposition 5 is sound: it correctly implements its own specification given whatever input it receives. Soundness is a claim about ’s relationship to its own input, not about the input’s relationship to the truth.

Why composition carries no guarantee either way. Suppose the upstream signal is wrong with probability , and has no second input, cross-check, or aggregation over multiple estimates that could reveal this. Then cannot condition its behavior on whether the input is wrong, because a wrong input and a right one differ only in value, not in any signal can observe.

Whether the propagated error rate ends up above, at, or below is therefore not something soundness decides. It turns on whether happens to map the specific wrong values the corruption produces to the same output the true values would have produced, a question about the geometry of ’s own level sets against the corruption’s own distribution, not about ’s soundness. A many-to-one , a threshold comparison among the plainest examples, can absorb corruption that stays on the same side of its boundary the truth was already on. What soundness forecloses is narrower than any claim about the resulting rate: only that detects the corruption and corrects for it, since detection requires exactly the second signal, cross-check, or aggregation step the premise excludes.

What this leaves open for any particular downstream mechanism, Optimization’s own threshold rule included, is a case-specific question, not a Layer 1 fact: not whether is trustworthy, but whether the corruption it actually receives has a geometry ’s mapping happens to absorb. Proposition 9 answers “no guarantee either way” in general. Whether a given stage dilutes, preserves, or worsens a given upstream failure has to be checked against that failure’s own shape, taken up below for Optimization specifically.

Physical translation. A vote-counting machine that counts every ballot correctly does not care whether the ballots were stuffed. Perfect correctness at the counting stage is not evidence about the count’s relationship to who actually voted, because the counting stage was never built to check that relationship at all. Composition can move where an error becomes visible, and can happen to blunt it or sharpen it depending on how the stage’s own arithmetic lands relative to the stuffing. It earns no credit either way, because nothing in soundness was ever aimed at getting that relationship right in the first place.

The tempting reading runs the other way, and it is worth saying plainly why it fails here. A system with several sound stages generally feels more reliable than any one stage alone, and for genuinely independent errors that intuition is correct: redundancy really does average out uncorrelated mistakes.

A pipeline is not a committee. Its stages are not redundant estimates of the same fact being combined. Each stage consumes only what the one before it produced, and a pipeline, unlike a committee, has no redundancy to average. Proposition 9 is the reason the usual intuition does not apply here.

    
    %%{init: {'theme': 'neutral'}}%%
flowchart LR
    classDef term fill:none,stroke:#333,stroke-width:2px;
    classDef bad fill:none,stroke:#c0392b,stroke-width:2px;
    classDef good fill:none,stroke:#2980b9,stroke-width:2px;
    subgraph "Committee: has redundancy to average"
        A1["Estimate 1"]:::term --> Agg["Aggregator
e.g. majority vote"]:::good A2["Estimate 2"]:::term --> Agg A3["Estimate 3"]:::term --> Agg Agg --> Out1["Output
wrong only if most inputs agree wrongly"]:::good end subgraph "Pipeline: no redundancy to average" X["Upstream signal
wrong with probability ε"]:::bad --> F["f: sound, single input,
no cross-check"]:::term F --> Out2["Output
error rate not guaranteed
lower than ε either way"]:::bad end
Figure 3: an aggregator has several independent-ish estimates to check against each other, so a minority error can be outvoted, the case Independence Illusion already covers. A single-input pipeline stage has nothing to check its one input against, so nothing in its own soundness promises the output is any less wrong than the input was. Whether it happens to be turns on how the stage's mapping lands relative to the specific corruption, not on anything soundness confers.

Calling this a corollary rather than a third clause is a claim about its structure, not about its stakes. C1 and C2 answer why a property’s own check can fail. Proposition 9 answers a different question: what happens when a sound mechanism sits downstream of one that already failed. For anyone assembling a multi-stage or multi-agent pipeline out of individually-verified pieces, that second question is the one actually load-bearing in production. Soundness at every stage, checked independently, is not evidence the pipeline as a whole is safe to run. This is worth flagging as its own practical warning before the next section narrows to Optimization’s specific case, because the general point survives even where that specific case does not.

Optimization’s own threshold is a case of Proposition 9, not a corollary of it [Layer 2: Fit]. Whether composition through Post 4’s threshold rule dilutes, preserves, or worsens what feeds it depends on the geometry Proposition 9 leaves open, and that geometry is not generic here. The signal reaching the threshold is not corrupted by noise scattered symmetrically around the true value. It inherits Simulation’s own systematic direction, Proposition 1’s token-cost forecast biased low by a factor of roughly five, and Rationality’s own systematic direction, Proposition 3’s asymmetric updating inflating confidence in whatever hypothesis was already favored. Both push the same way: believed cost down, believed odds of success up, toward the side of the threshold that says keep going.

A threshold does not attenuate a bias aimed at the specific side of it is least equipped to catch. A corrupted value that lands on the wrong side of produces the wrong decision with the same certainty a true value on the right side would have produced the right one. A bias large and consistently signed relative to the margin between the true value and lands on the wrong side far more often than a bias with no preferred direction would. This is not the general result. It is what the general result’s open question answers to, once the specific shape of the corruption feeding this specific stage is put in.

Applying Inherited Consequence to the multi-agent escalation result is a hypothesis, not a measured fact [Layer 3: Estimate]. Each agent instance’s verdict is read by the others in a symmetrical peer structure. That deliberative coupling would be a shared ancestor of every member’s vote, if the coupling is in fact what drives the escalation, and it would explain the group’s effective independent count collapsing toward one, the same pattern Independence Illusion formalizes for committees generally.

That qualifier is load-bearing, not throat-clearing. Post 4’s own account of this same study states outright that no formal result pins down which mechanism actually drives the escalation, an information cascade among correlated peers being one candidate among others. This post does not have stronger grounds than that post did. What is solid is narrower than “a live C1 instance”: the multi-agent finding is consistent with C1, and would be explained by it if the mechanism turns out to be correlated voting, a real, checkable hypothesis about the same data, not yet a measured mechanism.

The Constraint Sequence Framework, this blog’s own general systems-engineering maxim, said as much already: a constraint that surfaces at one level cannot be resolved by re-optimizing at that level, because the dependency graph puts the binding constraint upstream of where it became visible. What changes here is the grounding, not the claim, precise verification theory in place of a general maxim. Optimization’s portability gap is that constraint. The local mechanism is operating on borrowed guarantees from a property that was never secured, not a broken mechanism in its own right.

Falsification Criteria

F1 (the common-cause criterion). A verification signal is exhibited that shares its computation graph’s with the object-level process it checks, thereby failing Definition 7’s independence condition, yet still satisfies the power condition as stated in Definition 7 and reliably detects errors at a rate the correlation floor established above says it should not be able to reach.

This would falsify Definition 7 directly, not just weaken it. If a checker sharing a common cause with the thing it checks can still reliably discriminate errors above what the correlation floor predicts, the independence condition is not doing the work claimed for it.

F2 (the self-reference criterion). A consistent, sufficiently powerful provability-based reasoner is exhibited that derives the general reflection schema for arbitrary statements without thereby becoming able to derive arbitrary falsehoods, while remaining consistent.

Post 3, this series’ own Awareness post, already states this exact criterion for Proposition 4 as its own F1. It appears here as F2 only because this post’s numbering runs C1 first: the two labels name one criterion, not two. A counterexample here breaks C2, not C1, and it would not touch the graded cases at all.

F3 (the directional non-dilution claim). A single-input, non-aggregating, cross-check-free downstream mechanism is exhibited, fed a systematic, directional corruption engineered to land on the side of its decision boundary the mechanism is least equipped to catch, exactly the shape Simulation’s and Rationality’s own biases give Optimization’s threshold, whose output error rate is nonetheless measurably lower than the rate at which the corruption itself crosses that boundary.

This would falsify the Layer 2 claim about Optimization specifically, not Proposition 9 itself. Proposition 9 claims only that composition carries no guaranteed dilution, which a mechanism that happens to dilute a directional bias would not contradict, since no guarantee was made either way. What F3 tests is narrower and is the claim the Optimization case actually needs: whether a bare threshold, with nothing to compare its input against, can be relied on to attenuate a bias aimed at the specific side of its own boundary. A counterexample built from symmetric noise would not touch this, since any threshold dilutes symmetric noise that rarely reaches the boundary at all. That is not the case in question, and is not what F3 asks for.

This is the newest and least-tested claim in this post. Unlike F1 and F2, it has not been checked against an independent case beyond the one it was built from. Note the scope Proposition 9 itself states: a downstream mechanism that does aggregate multiple estimates, a committee vote, a median filter, is outside what F3 tests at all, and is exactly Independence Illusion’s own subject instead.

F4 (the diversification stopping rule). A cost-correlation profile satisfying Definition 8 is exhibited, and a fixed exchange rate , under which some policy other than Proposition 7’s marginal rule achieves a strictly lower value of at every .

This is the least likely of the four to fail, since the exchange argument behind it is a standard optimality proof for monotone marginal problems, the same style Post 4’s Proposition 5 already uses. The more realistic failure mode is not that the rule is wrong but that is not actually a single stable number. If what a unit of residual correlation costs itself changes with how much correlation remains, the single-exchange-rate premise the proof depends on breaks before the rule does.

What This Post Did Not Claim

Cognitive Map

  1. Two series on this blog, built independently, proved the same requirement from opposite directions: a check only counts if it draws on something the thing it checks could not also have corrupted, tested at the multi-agent committee scale in one series and the single-reasoner scale in the other.
  2. Independence and power are not two independent knobs. At matched base rates, the power margin equals the correlation between checker and object-level error exactly, , which proves rather than merely asserts why a perfectly independent checker is a coin flip, and clarifies what Definition 7 actually forbids: not correlation with the truth, which power requires, but the specific correlation that runs through .
  3. That requirement splits into two structurally different clauses, not one. C1, common-cause failure, is graded, escapable at a cost, and governs four of the five properties Portable Mind proved plus the committee case Independence Illusion proved. C2, self-reference, is binary and unconditional, and governs Awareness alone, because Loeb’s theorem binds even at zero error rate. The split was checked directly for a hidden third case and confirmed exhaustive: C1 itself has a hard-zero sub-case (Abstraction) and graded sub-cases, but both remain escapable in a way C2 never is.
  4. Diversifying a checker’s substrate away from the thing it checks is not free and does not reach zero correlation: Eckhardt and Lee proved even independently built checkers correlate whenever task difficulty varies, Knight and Leveson measured that same failure in twenty-seven independently written program versions, and forced diversity lowers the floor without erasing it. Two 2025-2026 papers confirm this is not a historical curiosity: LLM errors measurably correlate across models, and a concurrent statistical framework audits that correlation for LLM judges directly, both staying inside C1’s graded register and neither crossing into C2’s. How far to push diversification has an actual answer, not a rule of thumb: diversify through a layer precisely while its cost is below what the correlation it removes is worth, an exchange argument in the same style Post 4 used for its own stopping rule, arrived at independently because the underlying problem is deterministic where Post 4’s was stochastic, not because one theorem was stretched to cover both.
  5. A third pattern, Inherited Consequence, is not a third clause but a corollary of the first two under composition: a property with a provably sound mechanism of its own can still need a governor, because its inputs were corrupted by a different property’s own C1 or C2 failure. This is not merely definitional: a downstream mechanism with no cross-check on its input carries no structural guarantee of diluting an upstream error rate, the reason redundancy’s usual protection does not apply to a pipeline the way it applies to a committee, and Optimization’s own threshold fails to dilute for a further, case-specific reason: the bias reaching it is directional, not the symmetric noise a bare threshold would happen to absorb. Optimization’s multi-agent escalation is this pattern’s best candidate case, offered as a hypothesis consistent with the data, not a settled mechanism.
  6. None of this has passed review independent of the process that built it in the strong sense the term usually carries, and that is stated here as an open fact about this post’s own epistemic status, not a caveat to be read past.

Compute it. Before trusting any check, whether it is a second model instance voting alongside the first or a verification loop auditing a single agent’s own output, ask what is for the specific failure being checked for, and whether the check’s own computation passes through it. If it does, no amount of additional checking helps, only a genuinely different pathway does. How different is measured in prompt, weights, training corpus, and the ground-truth channel, each one a harder floor to clear than the last, and none of them free, with the task’s own difficulty landscape waiting past all four, uncrossable at any price. Before deciding how far down that list to go, put a number on what a unit of residual correlation actually costs, and stop at the first layer that costs more than it saves. Going further than that number justifies is not extra caution, it is spending past the point the spending was worth. And before trusting a property that seems to need no check at all, ask whether its inputs came from somewhere that did, and whether the mechanism in between has anything that could have caught the difference. A sound mechanism fed corrupted state and a sound mechanism fed honest state produce outputs that look identical until the state they were built on turns out to have been wrong, and by then the mechanism that failed is not the one anyone was watching.


[1] Loeb, M. H. (1955). Solution of a Problem of Leon Henkin. Journal of Symbolic Logic, 20(2), 115-118.

[2] Critch, A. (2019). A Parametric, Resource-Bounded Generalization of Loeb’s Theorem, and a Robust Cooperation Criterion for Open-Source Game Theory. Journal of Symbolic Logic, 84(4), 1368-1381.

[3] Pearl, J. (1988). Probabilistic Reasoning in Intelligent Systems: Networks of Plausible Inference. Morgan Kaufmann.

[4] Eckhardt, D. E. & Lee, L. D. (1985). A Theoretical Basis for the Analysis of Multiversion Software Subject to Coincident Errors. IEEE Transactions on Software Engineering, 11(12), 1511-1517.

[5] Knight, J. C. & Leveson, N. G. (1986). An Experimental Evaluation of the Assumption of Independence in Multi-Version Programming. IEEE Transactions on Software Engineering, SE-12(1), 96-109.

[6] Littlewood, B. & Miller, D. R. (1989). Conceptual Modeling of Coincident Failures in Multiversion Software. IEEE Transactions on Software Engineering, 15(12), 1596-1614.

[7] Ladha, K. (1992). The Condorcet Jury Theorem, Free Speech, and Correlated Votes. American Journal of Political Science, 36, 617-634.

[8] Barkett, E., Long, O. & Kröger, P. (2025). Getting out of the Big-Muddy: Escalation of Commitment in LLMs. arXiv:2508.01545.

[9] Kim, E., Garg, A., Peng, K. & Garg, N. (2025). Correlated Errors in Large Language Models. arXiv:2506.07962. Accepted to ICML 2025.

[10] Kuai, C., Jiang, J., Zhu, Z., Wang, H., Wu, K., Li, Z., Zhang, Y., Liu, C., Tu, Z., Fan, Z. & Zhou, Y. (2026). A Statistical Framework for Auditing Behavioral Dependence and Induced Bias in LLM Judges. arXiv:2604.07650.


Back to top