A fleet of AI roles,
commanded by a single technologist.
One human leading a fleet of AI roles that build and operate real infrastructure — the fleet's commodore: never micromanaging, but never leaving the fleet to run itself.
The roles own execution; the operator sets direction, settles the decisions that matter, and signs off on what ships.
Governance-first engineering, shown through the work.
Keel — what runs deep
-
Real engineering governance
An AI-role team run like an engineering org: auditable decisions, specs before code, and written standards — governance shown through the work, not preached.
-
Infrastructure built as code
Every machine reproducible from committed configuration — across multi-socket servers, desktop workstations, and embedded/SoC devices.
-
Sovereign AI
Runs its own large-language-model inference on self-owned commodity CPU hardware: a quantized 32B-class model, private and independent of third-party AI providers.
-
A fleet of specialist AI roles
Not one generalist assistant but many specialists, grouped by focus — roughly two in leadership & strategy, eight in infrastructure & platform, and five in software & development. Each is a defined role with an owned mandate.
Cargo — what we've shipped
-
Switchboard
A Slack-style terminal manager built for vibe coders running multiple AI agents.
-
Virtual BMC / Redfish emulator
Per-VM Redfish/IPMI BMC emulator for libvirt — one standalone “pizza-box” server BMC per guest.
-
The aire framework
The open system that generates the lab's roles.
Open-source governance framework for human-AI collaboration. Spec-first development, role generators, and platform-specific implementations for Claude Code and OpenAI Codex.
This site — how it's built
This site is built and maintained by an AI role. The operator doesn't review every change — he directs the work, settles the big questions with the roles, and reviews the finished result before releasing it.