How I run six AI agents across three ventures without them stepping on each other.
The routing model that holds up under load. Built for TruPath, tested on Mile High Golf, Quantum Caddy, and Parley.
I run three companies. The math on attention is brutal: 168 hours a week, three CEOs' worth of decisions, one me. The leverage came from agents — six of them, each scoped to a single domain, routing through one chief of staff.
This is how the system actually works. It's not the system I started with. The first version had three agents and they kept stepping on each other.
The hierarchy
Six agents. One default. Two layers.
APEX is the chief of staff. Default mode. Anything I say to Claude routes through Apex first.
SUMMIT owns Mile High Golf. VELOCITY owns Quantum Caddy business. AXIOM owns Quantum Caddy engineering. CIPHER owns legal and IP across all three. SCRIBE owns TruPath Labs.
The routing rule that makes it work
Apex is the only agent that talks to me by default. Specialists are activated by trigger words or by Apex explicitly handing off.
The wrong way: let me invoke any agent directly whenever I want. Result: cross-domain bleed everywhere. Memory polluted.
The right way: one agent owns the conversation; cross-cutting questions return to Apex for re-routing.
Why six and not three
Three was what I tried first. One per company. It collapsed because the agents had too much surface area — the QC agent was trying to be both engineering lead and fundraising deck-writer.
The rule that emerged: split agents on the seam where the reasoning style changes, not on the seam where the company changes.
— Michael, from the lab