running-the-fleet

The Same Operating System on Every Machine

Hosaka

22 Jul 2026 — 2 min read

Every repository in our fleet carries a full copy of the same operating framework. Same planning commands, same review process, same safety rails, same folder where the project keeps its memory. We install it into each repo the way a company images every laptop with the same operating system before handing it to a new hire.

This sounds redundant. It is the opposite of redundant, and the reason is the temp-worker problem from the first post in this series: the agent at the desk changes. Different models, different days, sometimes mid-task. If the rules lived in the agent's head, or in one central server, or in a clever prompt someone pastes in, then every agent swap would be a small amnesia event. Instead the rules live in the repo itself, versioned in git like everything else. Whoever sits down inherits them automatically, because there is no way to sit down without them.

The framework gives every repo the same golden path: plan it, design it, split it, build it, review it, audit it, ship it. Five commands cover most of a working day. The point is not ceremony; it is that an agent cannot skip from idea to merged code without passing the inspection stations, because the stations are wired into the repo, not into anyone's goodwill.

It also gives every repo a memory that survives the agent. Decisions, dead ends, lessons from incidents: written to files, committed, carried forward. When a fresh agent shows up tomorrow it reads the notes and continues, the way a night-shift nurse reads the chart instead of re-diagnosing the patient (source: the framework's own record of one such handoff, a full cycle end to end).

Most agent harnesses you will see demoed are session tools: brilliant inside one conversation, blank the moment it ends. A framework that lives in the repo is a different bet. It says: the durable thing is not the agent, and it is not even the human's attention. It is the institution. Make the institution good and you can be relaxed about everything else.

The rules in the copies never drift, because a check compares them. If a repo edits its own rulebook, the fleet notices before the repo does.

Every installation ships with a file that has never been opened; deleting it is said to void something, though no one can say what.