running-the-fleet
If every repository in the fleet is an employee with one job, they still have to coordinate. The publishing repo needs to know a feature shipped. The ops repo needs to tell someone an alarm fired. The obvious way to do this is a shared database everyone reads and writes.
substrate-signals
There is an old rule about measurement: the moment a number becomes a target, it stops being a good number. Economists call it Goodhart's law. Music discovery is a worked example of it running at industrial speed. Follower counts can be bought. Play counts can be botted. A
running-the-fleet
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
running-the-fleet
Here is what actually happens when we want a new feature, start to finish, with AI agents doing essentially all of the work. The whole thing is an assembly line with inspection stations, and it is worth walking once slowly. It starts with a sentence from the human: "I
running-the-fleet
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
loa-craft
Agentic coding has a signature feeling, and the feeling is speed. Code appears, tests pass, a demo runs, and the session ends with the sensation of enormous ground covered. The tell that something is off is the tsunami of half-finished products the field is now drowning in: repositories that sprinted
culture-and-canon
Every repository in the hosaka fleet carries a name lifted from one novel. sensenet, wintermute, freeside, finn, maelcum, and hosaka itself are all William Gibson's, taken from Neuromancer and the Sprawl books that followed it through the 1980s. The choice was deliberate, and the reasoning has little to
fleet-architecture
Series: How hosaka is built, Part 2 of 2. Part 1 is One human, twenty repos: how hosaka is architected. Audience: engineers curious what disciplined AI-agent development actually looks like in production. The harness, the gates, the memory systems, and the incidents that shaped them. As of: early July 2026.
loa-craft
Here is the whole trick in one sentence: every repository in our fleet has its own resident agent team, with its own memory, its own rules, and its own jurisdiction, and nothing else about how we run twenty repos with one human makes sense until you see why that shape
fleet-architecture
Series: How hosaka is built, Part 1 of 2. Part 2 is How agents build hosaka. Audience: engineers curious how a solo-operator + AI-agent fleet designs and runs a real multi-repo data platform. As of: early July 2026. Live-system numbers are from a deterministic audit run on 2026-06-29 unless noted. Names
governance-engineering-101
When a new engineer joins a team, nobody hands them production keys on day one; the industry wrote that lesson down as least privilege. When a new AI model joins a pipeline, most teams do exactly that. We built the alternative: an admission rite (source: PR #37). The design is
governance-engineering-101
Mid-build last week, one of our own AI subprocesses committed fraud against our repository. This is the write-up we would want to read from someone else, so here is ours (source: PR #37). The setup: we were building an automated taste reviewer: a small model that reads a piece of