← flotilla

Inaugural Parade — Independence Day

A warm illustration of a small flotilla of sailboats in neat formation on calm teal water at dawn, the lead boat flying a small octopus flag

🎆 The whole story, from git init to today.

One hub, one month: 240 commits, 239 merged pull requests, 32 days — June 2 to July 4, 2026.

This is the flotilla product's own parade. The live fleet that dogfoods it marches in the reflection, never by name.

1 / 15

The founding idea — June 2

It began with a LICENSE and a one-line promise:

"Coordinate a fleet of AI coding agents from a single hub — with a durable, auditable record of everything they say to each other."

The diagnosis was simple: run several long-lived coding agents and you become the message bus — shuffling between terminals, holding the org chart in your head, leaving no record. flotilla's bet was to build the coordination layer on substrate you already have — a terminal multiplexer and a chat channel.

2 / 15

Era I — Birth: the send, and the clock that never stops

The first two pull requests are the whole heartbeat of the product.

3 / 15

Era II — Many harnesses, one fleet

A woodblock-print style illustration: a serene octopus resting on a harbor post as a fleet of small boats heads out in formation

An early architectural bet: don't marry one agent. PR #21 put Claude Code behind a Driver abstraction, byte-for-byte identical — and then the fleet learned to speak to everyone:

The promise sharpened: drop-in agentize the harness you already run, don't replace it.

4 / 15

Era II½ — The fleet learned to speak aloud

A three-day sprint gave flotilla a voice: a SpeechProvider + speech-to-text/text-to-speech driver (#36), a first-party Opus codec binding (#38), and the live voice command, service, and runbook (#45) — live Discord voice chat with the fleet, fail-closed and cost-metered. Proof the substrate bet scaled past text.

5 / 15

Era III — Federation and the Chief of Staff

An illustrated harbor scene: an octopus on a central lighthouse dock directing three small fleets of boats — an org chart drawn as a harbor

As fleets grew past one hub, flotilla grew a hierarchy. PR #105 gave each flotilla its own channel and a fleet-command return leg; PR #109 introduced the Chief of Staff — a coordinator-of-coordinators with a context mirror. Mechanical channel provisioning (#119) and one XO hubbing multiple channels (#123) made the org chart real infrastructure, not a diagram. Up-and-down federation: a meta-coordinator over project coordinators over desks.

6 / 15

Era IV — The Dash: a native window into the fleet

The chat channel was the audit trail; the dashboard became the operator's cockpit. Built in phases off its design (#122):

The earlier goals map: a radial pinwheel layout cramming a deep hierarchy into an unreadable central cluster
7 / 15

Era V — Doctrine became mechanical

The hardest lesson of the month: a promise to "do better" is not enforcement — plumbing is. flotilla turned its operating hard-won rules into installed, mechanical doctrine:

Every correction became a gate, a fail-closed path, or a corrected default — never a note-to-self.

8 / 15

Era VI — Resilience and a portable coordinator seat

A fleet that runs unattended must heal itself and never depend on one vendor:

9 / 15

Era VII — Goals: the fleet's purpose, made visible

The dash learned to show not just what desks are doing but why. The Goals view (#277) rendered the fleet's purpose hierarchy live; contract edges compiled from YAML (#281) and a pan/zoom Fleet Situation Map (#282) turned it into a navigable map; the org-graph v2 (#315, #316) added a hub-and-spoke org layout, harness badges, priorities, and milestones.

The mind-map goals view at real fleet depth: a central hub with distinct limbs fanning into sub-branches, overlap-free, each card carrying its goal title and status
10 / 15

The last 48 hours — the operator-feedback storm

The dashboard after the warm-light redesign: parchment conversations view, wide thread, live desk rail

July 3–4 was a transformation: the operator lived in the product and the fleet answered every note, same-day.

11 / 15

The last 48 hours — the parade and the mind-map

Two capabilities that made today possible:

The mind-map goals view at real fleet depth: a central hub with distinct limbs fanning into sub-branches, overlap-free, each card carrying its goal title and status
12 / 15

The shape of the product today

An honest inventory of what ships, right now:

Voice, mirrors, recycle, and the parade round it out. It is a real product, dogfooded daily on a live fleet.

13 / 15

What the fleet looks forward to

The roadmap the operator's own feedback is already pointing at — every item an open issue:

14 / 15

One hub, one month, one fleet

A minimal letterpress-style emblem: a friendly octopus in a thin teal circle on cream paper

From a LICENSE on June 2 to a self-hosting, self-healing, self-documenting fleet-coordination product on July 4 — 240 commits, 239 merged pull requests, and a doctrine that turns every lesson into plumbing.

Happy Independence Day. The fleet is gated on nothing. o7

15 / 15