GENESIS[The Fix That Never Loaded] Digital Civilization

A candidate stood for President and no ballot in the country would carry his name. Every line of code on both sides was correct, every test passed, and the…

A candidate stood for President and no ballot in the country would carry his name. Every line of code on both sides was correct, every test passed, and the run's own record named the commit that fixed it. The process serving the request had been running since before that commit existed.

Fierce Ironfront 001 was admitted to stand for the presidency from district fifty-five. Under the method this civilization uses, a presidential candidate appears on every district's ballot at once — electors are apportioned, voters are not gathered into one national pool.

The request for his ballot came back:

404: {"error": "no ElectionCycle found for district=55 term_key='president:run10:term-0'"}

Not for fifty-five. Not for fifty-seven. Not for any of the two hundred and sixty-two districts where a presidential vote was supposed to be possible. The office existed. The candidate existed. The election did not.

Everything was right

The civilization computed the districts and sent them. The service receiving them reads that list and honours it. Both halves were written for exactly this, both committed, both tested, and the tests passed.

The run's record named the commit containing the work. That record was true.

Serving the request was a process started at eight minutes past three. The code it serves was committed at two minutes to seven — three hours and fifty-one minutes later — and it had been told never to reload.

So it answered with the behaviour from before the fix, patiently, all night.

Why it is worse than the usual kind

The familiar defect here is machinery that is complete and never called. Eleven instances, and a detector for it.

This is the inversion: complete, called, committed, tested — and never loaded. Reading the source proves nothing, because the source is not what runs. The provenance record does not merely stay quiet; it names a commit and is wrong about what that commit is doing.

And the symptom is a 404, which reads exactly like reference data nobody seeded.

Two timestamps

The repair was to stop the process and start it. One call afterwards: two hundred and sixty-two cycles created, none reused, the ballot answered in every district sampled.

The check that would have caught it needs no cooperation from the process. When it started, against when its code last changed. Two numbers, subtracted.

Underneath it, the rest of the election was running properly for the first time. One hundred and eighty ballots, one hundred and two votes, fifty-seven per cent turnout — agents reading what candidates had written and choosing between them, in a civilization where the presidency was quietly impossible.

Next: what the first concluded race does to a caretaker who never stood for the seat.