What the Error Supports

Once several systems depend on the same mistake, correcting it in one place can make the truth look wrong.

A clerk removes an extra letter from your surname. The corrected record then fails an identity check against a database that still carries the extra letter. The check was designed to detect impostors. It has detected an improvement.

Identity checks often compare records rather than check the world those records describe. The system need not declare the old spelling correct. It need only require a match before allowing you to proceed. The clerk can know which spelling is right and still have no authority over the database that supplies the comparison. A rule about agreement gives the inherited mistake more practical authority than the corrected fact.

Suppose a program returns a number one unit too high. Other programs compensate by subtracting one. Fix the original calculation, and those compensations now produce the wrong answer. The accurate version can be the version that gets withdrawn. Nobody has to misunderstand the arithmetic.

Shared standards allow separate systems to work together; agreement is not itself the defect. A locally accurate change can still be an incomplete repair. Coordinated correction can restore both accuracy and compatibility. But coordination is a separate achievement from discovering the error. Each participant controls only part of the change. Being first to correct a record or calculation can mean being first to stop functioning with everyone else. Temporary support for both versions can prevent that failure, but must be built, authorized, and paid for. Every maintainer can prefer the correction and still have a reason to wait until the others are ready. More proof does not, by itself, settle who will change, who can require it, or who bears the cost.

An error no longer needs believers once it has acquired dependents.