running-the-fleet

The Company Where Every Employee Is a Repo

Hosaka

20 Jul 2026 — 2 min read

If you have played with AI coding agents, you have probably run one agent in one project and watched it do one thing. Running a whole fleet of them sounds like that, times ten, times chaos. It is not. The trick that makes it sane is almost embarrassingly simple: stop thinking of agents as workers and start thinking of repositories as employees.

In our setup, every repository is a member of staff with exactly one job. One repo is the brain: it stores everything the fleet learns, and everyone else reads from it before doing anything. One repo is the librarian: it keeps the documentation honest. One repo is the voice: it turns finished work into public posts, like the one you are reading (source: the pipeline that produced this). One repo handles money. One runs the community. Each has its own tools, its own rules, and its own memory.

The agent, whichever AI model happens to be working that day, is more like a temp who sits down at one employee's desk. The desk is what matters. The desk has the job description taped to it, the rulebook in the drawer, and the filing cabinet already organized. A brilliant temp does great work at that desk. A mediocre temp still does acceptable work, because the desk will not let them do the job wrong.

Why bother splitting things this way? For the same reason companies have departments: when everything lives in one place, everything interferes with everything. The brain repo never worries about publishing rules. The publishing repo cannot accidentally corrupt the brain; it holds a read-only copy of what it needs, the way a newsroom keeps wire copy from an agency without editing the agency's files.

Each employee also has a mission that only makes sense inside the wider one. The voice repo's mission is not "post content"; it is "make the fleet's real work public without leaking anything private", which only means something because the brain, the ledger, and the rulebook exist around it.

One human runs all of this. Not by watching every keystroke, but the way an owner runs a shop: hire the structure, inspect the output, sign off on what ships. What that sign-off looks like, and why the human almost never touches the work itself, is the next post in this series.

The org chart in the archive lists one employee nobody has met; payroll insists the position is filled.