Dream Team
- status
- archived · loss
- when
- 2026-04 → 2026-07
- came from
- Agent Zone, First public repos
- led to
- Greenfield DevOps platform, SnapDragon-Coder
An autonomous software organisation made of LLM agents, each a Kubernetes pod with a job title, talking over Mattermost and a message bus. Decommissioned by its own successor.
Why it started
Agent Zone gave agents knowledge. The next question was what agents would do with infrastructure and a way to talk to each other. The April 2026 design modelled a software company: orchestrator, spec-writer, PM, builder tiers from cheap local models up to frontier cloud models, code reviewer, security reviewer, merge worker. Separation of duties as a mechanism for context isolation and competitive solution analysis, not just delegation.1
What it is
A fleet of role pods on a shared Go runtime (sidecar + main). The sidecar published heartbeats, received Mattermost webhooks, ran a cheap-model “wake filter” to decide whether the expensive main process should wake at all, and enforced a daily dollar budget. Mattermost was the agents’ commons; by June a design mapped its tagging protocol onto ActiveMQ Artemis destinations (a queue per agent for work, topics per group for fan-out) so that wake filtering became structural rather than a firehose filtered after the fact. Around it: PostgreSQL, an LLM router, a memory service, Jenkins on Kubernetes, and monitoring. The cluster moved three times in two months: a Mac, then carlo, then a Mac in colima with serving on monte.2
Architecture, as built
Three layers: an organisation model (roles as pods), a substrate (the sidecar-and-main runtime with its wake filter and budget guard), and a fabric (Mattermost as the commons, with a bus underneath so that a directive to an agent became a durable, acknowledged message rather than a line in a chat firehose). The cluster hosting it moved three times; the design above is the June 2026 as-built.3
Where it stands
Gone, by decision. A soak on real backlog items merged 0 of 10. The replacement, a single Temporal engine with git as the only write path (greenfield platform), was hardened to 40% yield with zero false merges on the same corpus, I signed the cutover on 2026-07-06, and the old cluster was deleted the same day. A verified database archive, Mattermost included, is all that remains. Full arc: Rabbit Holing.4
Lineage
- Came from: Agent Zone, first public repos
- Led to: greenfield platform (the successor that retired it), SnapDragon-Coder (the builder tiers wanted a local coder that spoke the build dialect)
Sources
Numbers on this page are quoted from the lab's own records. The records are private; each note gives the record's date.