The Elections Version Register

What this is

The 27 August audit read 23 repositories, 1,700 files and 144,915 lines. Three of its findings — M2, M3 and M4 — are the same defect wearing different clothes: the same artifact exists many times over, and nothing anywhere says which copy governs.

Four copies of one specification. Six implementations of one Merkle tree, in two mutually incompatible shapes. Seventeen site build scripts. Two election-command implementations. Three MBLTS custody implementations, one a byte-for-byte lift.

That is not untidiness. It means a cryptographer reviewing this system, a county clerk relying on it, or the next engineer to touch it cannot tell which version they are reading — and the audit found that the copy that looks newest is not always the one that is best.

The rule this register enforces

A component MUST NOT be marked superseded on similarity alone. Supersession requires an explicit statement in the artifact, or a documented decision recorded here with evidence.

Applying that rule found two defects in material that had been handed over as finished. Both are on the findings page.

Every address in the system

Observed 2026-09-10 by HTTP GET on <name>.bornbetween2generals.com. no DNS means never published — not a fault. 404 means published and broken, and there is exactly one.