HERMOD SYSTEMS

The Robot Government Diaries · Entry 01

The Accidental Government

My AI agents now file tickets, hold hearings, and reject each other’s work. Somewhere along the way, I accidentally built a very small government.

Everyone keeps asking which AI skills to study. My honest answer is neither a skill nor a model. It’s governance — the engineering of alignment.

The failure

We build campaign software with a team of AI agents. Version one taught us the real failure mode:

44 screens stuck between “asked for” and “actually built.” Documentation in three places, quietly disagreeing. A fifth of all effort spent on process that changed nothing.

Forty-four screens stalled between asked for and actually built A horizontal span runs from a mark labelled "asked for" on the left to a mark labelled "actually built" on the right. Forty-four short tally strokes are piled up just after the left mark. The rest of the span, most of its length, is empty.
Forty-four screens, stuck between asked for and actually built. The distance is the whole problem.

So I stopped shipping features. I spent the next stretch on governance instead — studying how the frontier runs multi-agent systems, then hand-rolling a scheme that fits a bootstrapped budget.

That work changed my diagnosis:

AI doesn’t fail at writing code. It fails at matching human intent — and human intent often contradicts itself.

Untangling that loop, elegantly, is the actual engineering problem. Here is the shape we landed on.

The system

Version two runs on three rules:

  1. Git is the only memory. Intent, decisions and disputes live in writing — not in chat, not in any model’s context.
  2. Judgment and building are separate seats — held by models from rival labs.
  3. Whatever one vendor’s AI builds, the other vendor’s AI attacks. Fresh context. One mandate: break it.
Two seats held by rival labs, standing on a written record Two boxes sit side by side: a builder held by one lab, and a reviewer held by a rival lab. An arrow carries the work from builder to reviewer. A second arrow runs back underneath, labelled "attacks". Both boxes are stemmed down to a band across the bottom labelled "git — the only memory".
Neither seat grades its own work, and neither one is where the record lives.

Drift

One more failure mode nobody warned us about: drift. Long sessions slowly forget what’s true — the coordinator most of all.

The fix: every seat is disposable. Kill it mid-task, boot a successor from a context pack — the architecture drawing, the ledger, its seat’s rules.

Models, it turns out, hold one diagram better than thirty pages. So the packs are pictures, not essays.

The institution remembers. No single model has to.

A drifting seat is killed mid-task and a successor is booted from a context pack A dashed horizontal line marks what is true. One seat's line starts on it and curves away downward as the session runs, ending at a cross where it is killed. A successor's line starts back up on the true line and holds, fed by an arrow from a box labelled "context pack".
Every seat is disposable. What it was holding is not, because it was never only in the seat.

Proof

Last night: nine adversarial review rounds. Twenty-plus real defects caught before anything shipped. One feature went four criticals, two, two, zero.

One feature across four review rounds: four criticals, two, two, none Four groups of unit marks stand on a baseline. The first group has four marks, the second two, the third two, and the fourth is an empty outline. The counts read four, two, two, zero.
One feature, four rounds. Criticals found each time: four, two, two, none.

The reviewers even overturned the arbiter — the AI at the top of the hierarchy.

The honest part

Human headcount: one. But never out of the loop.

I review every new shape of the product. I watch the governance run — and when it cracks, I upgrade the rules. That is where the human hours go.

The AI writes the code. The human writes the constitution.

The bottleneck in AI-built software is no longer intelligence. It’s governance.

— The Robot Government Diaries, entry 1.

Next entry: the day the government’s own security fence arrested the mail service. (That was yesterday. Everyone survived.)