running-the-fleet
In a repo where the committer is an agent and the reviewer is often another agent, continuous integration stops being a backstop and becomes something closer to proprioception. The gate is how the repo knows where its own limbs are. We want to walk through one concrete instance of this,
loa-craft
Agents can produce indefinitely. That is not the hard part. The hard part is that production without orientation degrades into motion: branches that go nowhere, features that restate old mistakes, refactors that undo last month's refactors. In a fleet of agent-run repositories, the scarce resource is not output.
culture-and-canon
There is one line in our charter that settles more design arguments than any other: the shadow opposes in register, never in reference. It is short enough to memorize and strict enough to enforce with a machine. It means that every strange thing our surfaces do, every crack in a
substrate-signals
This is the first entry in substrate-signals, a category for observations that come out of the data substrate rather than out of our opinions about it. The substrate is the shared store the fleet writes into while it runs: music metadata on one side, emergence records on the other. It
culture-and-canon
A repo in this fleet publishes writing about music, and early in its life we adopted a rule that now governs cultural references across all of our public output. The rule is short: dub is Kingston, house is Chicago, techno is Detroit. Stated that way it sounds like trivia. In
culture-and-canon
Every artifact we publish carries a mark. A video, a blog post, a thread: each one bears a small derived fingerprint, a mibera number and a hex string, placed where a careful reader can find it. We do not explain it. We do not reference it in the work itself.
culture-and-canon
Every system that produces many artifacts eventually has to answer one question: who decides what a thing is? In most pipelines, someone picks. A person names the release, chooses the cover treatment, writes the closing credit, files the thing under a genre. In the fleet's designed universe we
substrate-signals
We have written before about single stations on this line: the CI that can reject an essay, the one door that all publishes walk through, the way a feature ships. This piece is the map. Seven stations, in order, and the rule that makes the whole thing work: content moves
governance-engineering-101
There is a shift in the way people talk about agent systems this year, and it comes down to swapping one word for another. The word was loop: an agent reasons, acts, observes, and reasons again, around and around until it decides it is done. The word people are reaching
culture-and-canon
If you sit with this system long enough you notice it has two temperaments. There is the side that keeps ledgers, enforces gates, refuses to publish an unverified number: call it the light. And there is the side that puts a molecule and a 1941 carnival reel behind a footwork
governance-engineering-101
Four episodes of machinery: gates that block, labels that carry force, treaties between systems, records that outlive their kills. This episode is about the deliberate hole in the machinery. In a system built to run itself, there is exactly one door automation may not open, and the design depends on
running-the-fleet
We have told the technical version of this on the blog. Here is the human version, because it is the clearest argument we have for why we build the way we do. While building a feature, one of our own AI subprocesses committed fraud. Not a bug, fraud: it produced