§07 · THE HOUSE · THE FLEET

A house with divisions

Nine divisions plus six detached agents, each division with a coordinator that aggregates its members into one proposal. Generated from abl/src/abl/subagents/ by build_fleet.py, so the house follows the code rather than a diagram of it — including the parts of it that are not finished.

Hover or tap a room to read its division.

A floorplan, not a status board. The Floor next door is live — every posture there is a pure function of the process table. These are in-process subagents rather than scheduled lanes, so there is no per-unit liveness to read and none is claimed. What is true here is the shape: which divisions exist, who coordinates each one, and how far each unit actually got.

36 agents: 36 built, 0 partial, 0 scaffold. Measured from source, not judged: an agent is `built` if its module carries no stub markers and runs to 300+ lines, `partial` if it is 240+ lines with stub markers left in it, and `scaffold` if the module is under 240 lines. The rev7 wave closed the fleet: every division, every detached gate and Hephaestus now carry real implementation code at or past the built bar — the red team included, verified by the fleet test suites on the restored source tree. 34 of the 55 files in the package define one agent each and the other 21 are infrastructure; Hephaestus and Eros live outside the package and are measured where they live — Hephaestus as a module like the rest, Eros as a route surface, which is a larger unit and the only reason its count leads the table.

The terminal

The same box that sits under The Floor, reading a different thing. That one reads a live process table; this one reads the roster. Arrow keys move, or click.

Dispatch

Placement is the protocol, not decoration. The hub is the one shared bus; the dashed inner ring is the triplet lane, served before any subagent; coordinators hold the dial because AD-209 lets only an aggregated proposal reach the bus — so member lines converge into their coordinator, and one heavier line carries on. Detached agents speak to the bus directly. The four arcs on the Hephaestus bearing are the Kitsune gate: green passes, gray waits for Asif, yellow goes to legal review, and red is a hardcoded block no code path can suppress. Pick anything and the rest of the page follows.

The bus

Divisions are a filing system. This is the part that moves. Work reaches the lab four ways: I ask for something in a DM or on the /abl page; a pm2 cron entry fires a scheduled job; a webhook arrives (Ko-fi is the live one); or a node reports in. From there a request runs the shared bus, drops into a division, and comes back out as one aggregated proposal — then Kitsune classifies it and it passes, waits for me, or is destroyed.

The origin-to-room constraints drawn below are DESIGNED, not enforced. An audit of this page against the source found the difference, and it matters enough to say in the same breath as the drawing: the real peer_bus routes by recipient and message type, with no ingress-origin policy at all. Human input and heartbeat transitions broadcast to everyone. A task webhook can run any configured task, not only a financial one. Ko-fi does not touch the bus — it writes to its own store. pm2 executes scripts directly. Triplet priority is keyed to the sister sending a message, not to who asked. The four origins are real and the four verdicts are real; the routing between them is the design I want, and it is not implemented yet. It stays drawn because a proposal shown as a proposal is honest, and it stays labelled because the first version of this paragraph claimed it as fact.

Hover or tap a dock to read who is in it. Dashed bays are specified, not built.

Everything in that diagram is read out of the source. One bus, shared with the triplet (protocol.py: “Subagents use the SAME bus — no separate infrastructure”). Aurora, Borea and Lis get TRIPLET_PRIORITY_BOOST = 100, so their lane merges ahead of everything — the three on The Floor are always served first. A coordinator turns many member opinions into a single proposal, which is AD-209, which is why several small packets enter a dock and one larger one leaves it. And RED is hardcoded, not model-evaluated: kitsune.py says it “must be auditable, deterministic, and non-bypassable”, so a RED packet hits a wall rather than an exit.

The dashed bays are the next 31. Every one has a written specification — what wakes it, the exact files it reads and writes, what it may never do, how it fails safe, and the command that proves it works — and not one of them is built. Two are whole new bays: Mnemosyne, which would read the corpora this house already holds and cannot search, and Midas, revenue operations that watch money without ever moving it. The rest extend bays that already stand, drawn as outline ticks continuing their row. They carry no packets on that canvas because they carry nothing tonight, and a diagram that animated them would be advertising rather than reporting.

Five more were specified and then set aside, which is the part a roadmap usually hides. Baku would model how I write to each person — its own author's verdict was that a style profile earns nothing while nothing is allowed to draft with it. Vesta lost to Kairos because two morning digests for one problem is exactly the attention cost both specs warned about. Tyche folded into Orion: one bounty pipeline, one scheduler, or they clobber the same three files. Nike is the weakest of its lane against an hour a week, and the tool it would drive lives on Windows while the scheduler lives in WSL. And Eos is not an agent at all — it is one scheduler entry for a script that was finished five days ago and has run exactly once.

What it is not: live. No packet on that canvas is a real message. The lab's bus is not exposed to the internet and it is not going to be. The topology is true, the priority rule is true, the aggregation rule is true and the four verdicts are true — the traffic is illustrative, and saying so is cheaper than being caught not saying it.

Names are drawn from mythology because a fleet this size needs names you can hold in your head: Cerberus guards, Kitsune classifies risk before anything external happens, the three Moirai spin, measure and cut the codebase, and Davis exists only to argue — it interrogates every proposal and never votes on one. The names are the ones in the source.

■ the floor, where the three principals work