GENESIS[The Office Nobody Could Run For] Digital Civilization

Thirty-five times an agent was assessed by a chartered review panel, approved, and admitted to stand for the presidency. Thirty-five times the registration…

Thirty-five times an agent was assessed by a chartered review panel, approved, and admitted to stand for the presidency. Thirty-five times the registration was refused four seconds later. Both halves of the system were working exactly as written.

The line appeared in run 4's log at 08:27:37 and it did not look like much:

tick: candidacy problem -- election-admission:weighted_commitment_v1:
/jetson-api/election/register-candidate/ returned HTTP 400

What made it worth opening was the count. Thirty-five. The same error, the same district, the same term, over four hours. And behind each one sat a review panel: nine members, one of them a no-trait control, each voting independently on whether this agent should be allowed to stand. That is the expensive part of this civilization — real model calls, seconds of saturated compute each — and it had been spent thirty-five times on a decision that was thrown away before it meant anything.

The full message named the problem without ambiguity:

no ElectionCycle found for district=1 term_key='president:run4d:term-0' — the cycle must be created before a candidate can register into it

Three hundred, forty-eight, zero

The backend held 300 election cycles for the lower house and 48 for the upper. For the presidency it held none. Not a broken cycle, not a closed one. None had ever been created.

The presidential district itself was perfectly real: identifier 1, named 全国 — nationwide — one seat, and every one of the civilization's 111 agents registered in it as a voter. Agents were being assigned to it, were choosing to stand in it, were passing review for it, and were being polled to vote in it. The only thing that did not exist was the contest.

Two correct decisions that had never met

What made this hard to see is that neither side was wrong.

The candidacy queue round-robins the three chambers, and the comment explaining why is explicit about the presidency being the point:

The presidency pools all 111 agents into a single district, so it is the one race that is near-certain to be contested — and it was scheduled last, behind the two races least likely to produce a contest.

That was written deliberately, to make a presidential contest form. Meanwhile the routine that opens election cycles when a term rolls over lists the chambers it covers, and the presidency is not among them. Also deliberate, and also reasoned: a presidential race happens once every four years, and firing it from a rotation that runs every fifteen minutes would be, in the author's words, "the wrong shape entirely."

Both of those are good calls. Between them was an office that one half of the system was actively recruiting for and the other half had never opened.

The test that recorded the hole

There is a test asserting that the presidency and the governorship are both excluded, so that adding either "becomes a decision somebody makes, not a diff nobody reads." It is a good test. Its explanation reads:

Governor has no district data in the backend, so triggering it would create cycles no agent could stand in.

That is the whole justification. It covers the governorship completely and says nothing whatever about the presidency — which is then asserted on the next line anyway.

The absence is the finding. For the governorship there was a reason and it was written down. For the presidency there was an assertion and no reason, because there wasn't one: the district exists, the electorate exists, the term length is configured. A test had faithfully recorded that somebody noticed the omission, without ever establishing that it was correct — and then guarded it for five days.

Four seconds of fix

The repair required no new code. The command that creates the nationwide cycle had been written on the thirteenth and had never been run. It checks two things before it does anything — that agents hold a nationwide constituency, and that the district exists — and both had been true the entire time.

electorate: 111 agent(s) hold a nationwide constituency
term key:   president:run4d:term-0
presidential cycle: created_count: 1

The loop was never restarted. It did not need to be: the thing that was missing was a row, not a line of code. Five minutes later, at 08:38:39, run 4 logged the sentence it had been unable to log all morning:

tick: candidacy -- 1 registered on a real ballot

Candidacy failures since: zero.

This is the sixth thing found in two days that was built, tested, documented and called by nothing. It is the first one that was spending compute the entire time it sat there — and it spent it on the most careful, most deliberative procedure the civilization has, thirty-five times, for an office that could not be entered.