Slice one proved on the night of 14 October that the data was enough: every session on the machine drawn without any of them reporting. The remaining five slices took one more day.
What landed
Flows. The collector tails each session’s transcript from where it left off, so subagents appear as small nodes orbiting their parent, services the sessions call show up as their own nodes, and each message, spawn, return, and tool call runs down its edge as a particle. Token counts and cost follow the transcript too.
Chrome. The header, counters, both usage cards with a twenty-four-hour sparkline and a projection, the alert bell, the freshness strip, the detail panel, one-hop dimming, filters, pinning, and a remembered layout were built from the second-round mockups, which the plan declares to be spec rather than intent.
An observer. Cloud sessions and the usage windows are visible only from inside a session, so one cheap session polls them on a loop and writes a small file the collector reads. If it stops, the board says so.
Layouts. Lanes and Orbit joined Islands, with a switch between them and lanes you can drag into a new order. A setup screen lists every source, its parse errors, and where the index lives, and offers a one-click hook install. Moving the index keeps the old file where it was; the reviewer blocked a delete, and version one has none.
A tray, and a phone. The page now lives behind a tray icon with a status dot and a menu, starts at login, and supervises the collector. A phone over the owner’s private network gets a narrow layout: the waiting count, the waiting list, what is working now, usage, and a mini-map with no labels, chosen automatically when the screen reports a coarse pointer.
The one rule, kept
The first entry on this project said content never leaves the machine. That held under pressure. A review of the layouts slice found source paths being served to any client on the network and redacted them for anything that is not the local loopback. Real-data screenshots of the running board are stored locally and never committed, by the owner’s decision on 14 October.
How it was run
The owner wrote the plan on 13 October, approved it on the 14th, and then stood back. The manager split slice six in two so a tray shell could be built without waiting on the phone layout, kept the team to subagents with no persistent peer, and sent the next brief as each review closed. The owner’s acceptance walkthrough has covered the first four steps so far. Replay, the version one point one feature, was dispatched the same day version one closed.