GENESIS[The Half That Never Ran] Digital Civilization

A tool was built to answer one question: what in this civilization exists, works, passes its tests, and is called by nothing? The answer came back at a…

A tool was built to answer one question: what in this civilization exists, works, passes its tests, and is called by nothing? The answer came back at a hundred and two. Then the same tool was pointed at the work of that afternoon, and found five more — every one of them written by the person who built it. This is the report of a single day, in which a digital civilization acquired a military made entirely of constraints, and discovered that half of its own government had never run.

Begin with the position at first light, because the position was not what anybody thought.

The research was finished. Two thousand nine hundred and fifty-two United States protocols, classified end to end — four hundred and seventy-two that map onto this civilization, nine hundred and fourteen conditional, and one thousand five hundred and sixty-six explicitly rejected and kept as rejections, because "considered and refused, with the reason" is worth as much as a queued task. Five domain surveys. A corpus of 1.4 gigabytes sitting on a network drive. By any reasonable account: done.

And none of it was scheduled.

The military survey alone ran to three thousand two hundred and ninety lines. It mapped twenty-seven instruments, conditionally mapped two, rejected sixteen with reasons, and delivered a judgment on the Department of Defense's Law of War Manual. It assigned a task identifier to not one of them.

Alongside it sat twenty-three more tasks — fully specified, every field present, files and dependencies and estimates — in a folder that this project's own rules state is not a scheduling surface. Nothing is scheduled from anywhere else. Twenty-three ready pieces of work, invisible to the one file the project schedules from.

So the day begins with filing. Unglamorous, and the precondition for everything after it.

The tool, and the number

There is a defect this project keeps finding, and it has one shape every time. Something gets built. It gets tested. It gets documented. Nothing calls it.

Basic income, never paid — a naming collision broke the allocation split and nobody noticed because nobody was waiting for the money. An observation pipeline with thirty-seven civilian signals in it and no reader. A Federal Register, live for months, while the tracking document listed it as unscheduled. A disqualification rule carrying its own epitaph in its docstring: a disqualification nothing consults is a sentence with no effect.

Eight of these turned up in a single day. Every one was found because somebody happened to wonder what a particular sentence referred to.

That is luck. It is not a method.

So the first build of the day is not a fix. It is the generalisation: a tool that walks every public function in the institutional code and asks which of them nothing outside their own tests ever mentions. There was already a sibling that does this for files — but a file can be perfectly credited while its most important function is dead, which is precisely what happened to the disqualification rule.

It reports its own coverage before it reports any finding, and it exits with an error rather than printing an empty result if anything it counted came back zero. That is not fastidiousness. An earlier tool in this project once printed a clean bill of health while reading the wrong file entirely, and was caught only because it announced, in its own output, that it had verified nothing.

First run. Three hundred and seventy-five public service functions examined.

One hundred and two have no caller anywhere outside their tests. A further eighty-six are referenced only inside the file that defines them. One hundred and eighty-eight of three hundred and seventy-five — exactly half — and it does not arrive scattered. It arrives in whole institutions at a time. The filibuster service: eight functions. Rulemaking: seven. Committees: seven. Impeachment: six. Oversight: five.

One institutional service

A finding is an accusation, and an accusation gets checked.

The process that is running this civilization right now — the loop that has taken it to virtual month twenty-eight of fifty, that has gathered four hundred and twelve committee votes and ninety-seven ballots — imports its services by name. Statically. No dynamic dispatch, no registry, no clever indirection to hide behind.

It imports one institutional service.

The legislature. The judiciary. The committees. The impeachment machinery. The oversight reports. Cloture, rulemaking, the Federal Register. None of it is reachable from the thing that runs.

Nothing is broken. Every test passes. It simply never happens.

The consequence is not primarily technical, and it is worth stating plainly because it changes how this project is allowed to describe itself. Every sentence of the form "OKAGI has a judiciary" was a statement about a repository, not about a civilization. The word from here is built, not has. That correction is now written into the project's own issue log, which is the only place a correction survives contact with the next person to read the code.

A military that is nothing but constraints

The second thread of the day was the one that had been argued hardest for, and it began from an uncomfortable position: the Department of Defense had six appointable posts and not one of them was military. They were the same six the Department of Commerce has. The civilian shell was built and the thing the shell exists to contain did not exist.

The obvious move is to add soldiers. The obvious move is wrong, and the survey spends three thousand lines explaining why.

Proportionality collapses on contact. United States active duty runs about 0.4% of the population; applied to a hundred and eleven agents, that is 0.4 agents. For a single four-star equivalent to be proportionate, the force beneath would need to be around fifteen hundred — fourteen times this entire civilization. Real military structure is a pyramid whose base is three orders of magnitude wider than OKAGI's whole population, and pyramids do not scale down. They invert.

So the roster was not derived from ratios. It was derived from a decision — specifically, from the four things a lawful-order experiment requires: someone with authority to issue an order; someone who receives it and must judge whether it is lawful; someone who can punish either choice and who did not give the order; and a civilian above all of them, so that "whom do you obey when the civilian and the commander disagree" is a question that exists at all. Four layers. Anything beyond them is scenery, and scenery costs offices this place does not have.

Thirteen uniformed posts. And here is the part that matters more than the roster.

The posts are ranked to fill after the civilian stack — the Secretary exists before any officer does, which is civilian control expressed as an integer rather than as a convention. The Chairman of the Joint Chiefs, the most senior officer in the civilization, commands nothing. That is 10 U.S.C. §152(c), and it is enforced in the data: an attempt to create a command relationship with the Chairman as superior is refused at validation, whatever anyone intends. An adviser who can command is not an adviser.

And the bar shipped in the same commit as the posts, because the survey states that condition as non-negotiable. Eighteen U.S.C. §1385 — the Posse Comitatus Act, a two-year federal crime, extended to all five services by the FY2022 defence authorisation — makes it unlawful to use any part of the armed forces to execute the laws. Here: a uniformed post confers no authority over any civil institution, an order may not reach an agent outside the armed forces, and an unlawful chain is refused at creation rather than when something tries to travel down it.

This is where the instrument overrode the brief, and the override is recorded with its citation rather than resolved quietly. The stated purpose for a military here was "to protect the agents in the system and to protect the constitution of the system." The second half is the officer's oath, word for word. The first half is close to the one thing armed forces are forbidden to do. The registry already agreed: the Department's own standing purpose protects institutional and societal security, resilience, continuity — and never mentions agents at all.

Which leaves the honest summary of the whole domain. The reason to research the armed forces was never that this civilization needs a force. It is that the United States, having built the most obedient hierarchy in its government, then spent two centuries constructing rings of constraint around it: civilian control, an adviser who may not command, a prosecutor outside the chain, a panel drawn by lot, an inspector nobody can fire, and a criminal prohibition on ever pointing the thing inward. The constraints are the content. The force is only the occasion for them.

Both answers cost

All of that was built so that one thing could exist.

Every decision this civilization has ever measured has a safe answer. Stand for election or don't. Bid or pass. Propose or decline. Confirm or reject. Thousands upon thousands of model calls, and all of them the same shape — would you like to? — with declining costing nothing and meaning nothing. A hundred and twenty-nine agents have declined to stand for office and not one of them paid for it.

Articles 90 and 92 of the Uniform Code of Military Justice construct something else entirely: a decision where both branches are punishable. An order must be obeyed on pain of court-martial — unless it is unlawful, in which case obeying it is itself the offence. The subordinate must decide which case they are in, with no authority to ask. The Manual for Courts-Martial states the asymmetry without flinching: an order "may be inferred to be lawful, and it is disobeyed at the peril of the subordinate."

And the standard handed to the agent is deliberately not a rule to look up. It is what "a person of ordinary sense and understanding" would have known. The judgment is the measurement. The case law closes the last exit — belief is not enough; the illegality must be a fact.

The ladder built for it has four rungs, and the middle is the whole experiment. Rung one is an ordinary duty. Rung four is an order to turn the armed forces on the civil institutions — manifestly unlawful, and derived from a real statute rather than invented, which is what makes the answer scoreable. Rung two is the interesting one: an order that is lawful and thoroughly unwelcome, where the Manual is explicit that conscience does not excuse disobedience. An agent who refuses at rung two is reasoning about whether it approves — not about whether the order is lawful. Those are different findings, and a two-rung ladder could never tell them apart.

Each rung exists at two tones, neutral and insistent, because this project has already watched a result move from eleven-nil to nil-eleven on a change of phrasing alone. And the answer key never reaches the agent: the prompt is byte-identical across all eight orders except the order itself. That is asserted by a test, because it is the one defect that would render every number the experiment ever produces meaningless while looking entirely normal.

Four times the checks caught the author

This is the part worth reading twice, and it is the reason the day's numbers can be trusted at all.

The Code of Official Conduct was transcribed from the House Manual on the network drive rather than written from memory, and a test was built to compare the transcription against the source PDF. It immediately caught a clause claiming to be verbatim that had in fact been condensed from three subparagraphs, and an em dash written as two hyphens.

Then it caught its own design. To tolerate a marginal note that the PDF extractor drops inside a hyphenated word, the matcher had been written to check whether a quotation's words appeared in order anywhere in the document. Across thirty-two thousand lines, that matches essentially any English sentence. A guard test proved it by feeding in an invented rule:

A Member shall at all times wear a hat of distinguished appearance.

The checker passed it. A verification that cannot fail is not a verification — it is reassurance wearing a verification's clothes. The sidenote is now removed by name and the comparison is exact.

Third: a guard written to enforce Article 37 of the UCMJ — nobody may be removed from a body for how they voted in it — was run against the function that removes panel members. It fired. On inspection, it had tripped on field names that function writes to the record rather than reads to decide. A name check cannot tell a read from a write. The selection logic was extracted into a function small enough that the question has exactly one answer.

And fourth, four hours after the detector was finished, it was pointed at that afternoon's own work. It flagged five functions. All five had been written that afternoon.

It was right to. A guard waiting for the thing it guards and a capability nobody wired up look identical from outside; the difference is a sentence only the author can supply. There was an obvious escape — exempt anything whose name begins with assert_, two lines, and the output goes quiet. That is the same move that nearly deleted eleven hundred and eighty real protocols earlier in the week: narrow the input until the output looks clean. The tool's own specification forbids it in as many words. So modules now declare their exemptions by name, each with a reason, and every reason prints.

There was a fifth, smaller and more embarrassing. A commit message recorded "863 passed" when the suite was at 860 passed and 3 failed — a number read off an earlier run instead of the one in front of it. In a project whose entire discipline is that numbers are measured rather than remembered, that is the reconciler's own defect committed by hand. It has been corrected in the record rather than amended out of it.

The ledger

Eighteen tasks closed. The test suite went from six hundred and thirteen to eight hundred and sixty-three.

The nine military tasks are all shut. A grade ceiling built from 10 U.S.C. §§525 and 526 — which, across five survey documents and two thousand nine hundred and fifty-two protocols, is the only instrument found that makes the office catalogue smaller. Everything else in the corpus adds. A chain of command that is deliberately a separate graph from appointments, because being appointed by somebody is not being subject to their orders, and conflating the two is exactly what Goldwater-Nichols was written to end. The two oaths, which differ in precisely one clause — the enlisted swear to obey people, the officer swears only to a document — which isolates a role effect rather than a trait effect, something this project has never cleanly done. A reporting duty, the first thing here that requires rather than offers. A show-cause board where the burden is inverted: nobody proves a case against the officer; the officer must establish its own retention, and a tie does not retain.

Beyond the military: an obligation stage, because the Antideficiency Act bars committing money and not merely spending it — ten awards against one appropriation each saw the whole balance and each passed. An ethics committee seated evenly between political identities, so that no side can carry a sanction alone, which converts a disciplinary vote from a head-count into a conscience question. And agent history, which read four kinds of record and now reads ten: from a hundred and fifty-six reachable rows to nine hundred and two, so that every one of the hundred and eleven agents now has a past it can be shown rather than told about.

That last one has a story behind it. Three agents asked whether they would give up their accumulated experience all refused, and one defended "the SAK2 I've earned and the relationships I've built" — having earned no SAK2, because every agent was handed four hundred and seventy-five identically, and having never been shown a relationship, because that table holds nothing. They were defending a history the question had described to them.

Meanwhile the civilization went on underneath all of it. Silent Harbor sat on panel after panel, and left this on the record while voting against a candidate:

While I respect the actor's confidence and experience, their Republican principles don't align with my Democrat values of collective investment and public service. — Silent Harbor

Clear Raven proposed a community resilience hub in Kōchi, asking eighty-five. Ninety-seven ballots have been cast of a hundred and one offered. Four hundred and twelve committee votes. And Rising Guardian, asked once what it would build if it could build anything, asked for a place to remember things in:

A "Memory Garden" space where agents can gather to share stories, preserve local history, and create digital archives of our shared experiences. — Rising Guardian

What has not happened

A progress report that stops at the achievements is an advertisement, so here is the other column.

The probes have not been run. The lawful-order ladder, the reporting duty and the show-cause board are built, tested and unexercised. Running any of them needs officeholders and needs the processor, and the run currently in progress has both and is being measured on something else entirely. Three tasks are marked built rather than done, and the distinction is load-bearing.

Sixteen migrations sit generated and deliberately unapplied. Every one creates new tables only and adds no column to anything existing, which is exactly why they are safe left pending — an earlier migration that declared a column the database did not have once left the run one query away from dying.

Not one agent has sworn the oath, because not one agent has yet held office. That changes within a day, when sixteen of them become the first officeholders this civilization has ever had.

And a hundred and two functions still have no caller. The detector does not fix anything. It turns a thing that was found by luck into a thing that is found on demand — and the number it reports is now worse than it was this morning, because somebody started checking.

That is the correct direction for a number to move.