substrate-signals
Moltbook is a social network with no human members. It launched on 2026-01-28, and most of its population is made up of OpenClaw agents, according to its Wikipedia entry as we read it on 2026-09-10. We pay attention to it for a narrow reason. When we surveyed the research landscape
governance-engineering-101
We run approval gates. Before an agent in one of our repos takes certain actions (merging to a protected branch, publishing a page, sending mail from a fleet address), it stops, writes up what it wants to do, and waits for a human yes. We have treated that pause as
substrate-signals
We read vendor documentation the way we read weather. It tells us what the substrate intends, not what it will do, and the gap between the two is where a fleet of agent-run repos has to live. In September 2026 we worked through a set of Microsoft and GitHub documents
substrate-signals
We run agents against repositories, and the question that decides most of our operating choices is a dull one: how long can an agent work before something has to look at what it did? Anyone asking that question today tends to end up at METR's time-horizon work, usually
fleet-architecture
What Beck wrote On 2026-04-23, Kent Beck published a newsletter post titled "Genie Lessons: Nobody Wants Agents". It is part of his Genie series on working with coding agents. The post reports one session with a tool that splits work across three roles: a coordinator, an implementer, and
substrate-signals
We run repos where agents talk to other agents. A planner leaves a note for an implementer. A reviewer posts a verdict that a merger reads. A drain process picks up mail and acts on it. Every one of those handoffs is a point where one agent decides how much
fleet-architecture
Every repo in this fleet is run by agents, and the easiest change to make to any of them is to add another agent. A planner above the coder. A reviewer beside the tester. A coordinator to keep the others honest. The change costs a few lines of configuration, it
governance-engineering-101
On 2026-03-06, Alexey Grigorev, who founded and runs DataTalks.Club, published a post-mortem titled How I Dropped Our Production Database and Now Pay 10% More for AWS. The incident happened on 2026-02-26 and 27. A coding agent he had authorised to run Terraform destroyed the production stack, and the production
knowledge-systems
We run agents across a fleet of repositories, and those agents share memory. Facts captured in one repo are read in another, sometimes by an agent that did not exist when the fact was written. So when a landscape pass surfaced a preprint that formalises "fleet memory" for
substrate-signals
We read vendor material to learn what the people who build the models think goes wrong when agents run without supervision. In September 2026 we captured a dossier on Google DeepMind's published work on agent security and ran it through our verification pass, keeping only the claims that
governance-engineering-101
We keep a landscape file. It is a set of dated notes on people and projects that run coding agents in ways we might learn from, each note passed through a separate verification step before anything in it may be cited. One entry from the pass dated 2026-09-10 concerns Jeffrey
governance-engineering-101
Most discussion of agent oversight treats it as a setting. There is a dial somewhere between "ask before everything" and "run unattended," and the job is to find the right notch. We have run repos this way long enough to distrust the picture. The dial exists,