"Authority validation has fixed cost per packet; consensus coordination's cost scales with the validator set." This page makes that claim precise: under what assumptions does it hold, what does it actually mean, and what would falsify it.
Consider n participants who each hold a candidate answer to a verifiable question — say, a p-value claim, a balanced equation, or a dimensional consistency assertion.
Each participant's confidence in the answer increases as a function of how many other participants agree. Coordination cost scales with the validator set — each additional validator adds overhead. The reliability of the result is bounded by the least-reliable participant who could swing the vote. Collusion, bad-faith claims, and groupthink grow as problems at scale.
Each participant submits the candidate answer to a fixed external standard that returns CONFIRMED, MISMATCH, or NOT_APPLICABLE. The cost of each check is fixed per packet — the standard does not care how many people are asking, and the standard does not change because more people are asking. Validation cost does not scale with the number of validators.
For a class of questions Q where (a) a deterministic external verifier exists, (b) the verifier's cost per check is bounded by some constant k independent of network size, and (c) a wrong answer's cost is at least c per participant — authority validation strictly dominates consensus validation past the threshold where consensus coordination cost exceeds n · k. For most realistic cost assumptions and verifier runtimes, that threshold is small.
This is not a contested claim. It's true by inspection. The interesting work is in the assumptions.
For chemistry balance, scipy-recomputable p-values, sympy-checkable derivatives, and SI dimensional analysis, the verifier exists and is small. The Concordance Engine ships these. For "is this scientific theory true," no such verifier exists, and the claim does not apply.
If the standard itself drifts — sympy ships a bug, the standard library is compromised, your local install is poisoned — authority validation degrades to whatever the corrupted standard says. The engine hashes its dependencies via packet_manifest.yaml; tamper-evidence helps but is not a substitute for trusting the upstream.
Most decisions are partly verifiable and partly judgment. The engine handles the verifiable layer (math, units, structural completeness) and explicitly does not handle the judgment layer. A community deciding whether to fund a program will find the engine useful for the structural and computational pieces; it will not adjudicate priority.
If wrong answers are cheap, consensus is fine — fluid agreement at low stakes is normal social behavior. The authority approach pays off when wrong answers compound: published papers, board decisions, code in production, regulatory filings.
Authority validation is not magic. The claim that the Concordance Engine usefully implements O(1) authority validation could be falsified by:
The fourth is what the benchmark page is set up to test. The first three are open invitations — file an issue with a reproducible packet that breaks the claim, and we either fix the engine or narrow the claim.
Three frequent misreads, named explicitly: