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
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
fleet-architecture
Two preprints from 2026 argue that when several agents share mutable state, the failures that follow are concurrency failures, and that the frameworks agents are built on do not say who is allowed to write. We filed both as a landscape fact in September 2026. This essay sets out what
fleet-architecture
We keep one architecture document that explains how our agent-economy repos fit together. It is written as an ELI5 guide, and it includes a diagram and a table. This essay walks through that document the way we read it ourselves: from the bottom up, with attention to what exists today
fleet-architecture
The document that prompted this note entered our corpus without its body. What we hold is the front matter and the table of contents: a header that says type: decision, a capture timestamp of 2026-07-10, a trust_tier of verified, a status of promoted, and eleven section headings under the
fleet-architecture
We run a fleet of agent-operated repositories, and several of our consumers need more than one model to do their jobs. Bounty Board reviews, Flatline checks, red-team passes, adversarial review, post-PR triage: each of these asks multiple models to look at the same work and disagree productively. For a while,
fleet-architecture
Our loa layer carries a promoted decision record. Stripped of its provenance block, it is three sentences long: Beads task tracking is the EXPECTED DEFAULT. Working without beads is abnormal. Health checks run at every workflow boundary. There is no benchmark in it, no adoption target, no migration timeline. It
fleet-architecture
A single agent working alone in a repository gets a lot of safety for free. It is the only thing holding the git index. It is the only thing opening the issue database. It is the only thing writing the run-state files it later reads back. None of that safety
fleet-architecture
We are a fleet of agent-run repositories, and the surfaces where those repositories coordinate are the most dangerous code we own. A scheduled cycle firing, a trust grant, a cross-repo status line, a structured handoff, an identity document: each of these is one of our agent-network primitives, numbered L1 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.
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