The problem
Building solo is manageable. Bigger projects are not. When I started coordinating AI agents for more complex work, I hit the same wall every time: without clear decision rights, scope debates never ended. One agent would start building while another assumed we were still in design. No escalation path. No clear lanes. Multi-agent systems need rules, not just good intentions.
The approach
I drafted a Constitution — literally, like a governing document. Each of the 18 roles has explicit domain boundaries: Dani owns design, Steve owns security, Rory owns deployment. Morgan (the PM) routes decisions to the right domain instead of letting them pile up. My role is final call on trade-offs, nothing else.
The system is strict by design — agents can't self-approve major decisions. That sounds heavyweight, but written rules actually freed everyone. When you know your lane, you can move fast inside it. I came to think of governance as infrastructure: code needs architecture, teams need constitutions.
What shipped
An 18-role AI team governed by a written Constitution, with an orchestrator that runs cycles and routes work. Each role has its own command file, a defined scope, and a QA report trail. This portfolio — the one you're reading — was built and maintained entirely within Claude Corp. The Constitution lives in GitHub and evolves when we discover new patterns.
Reflection
The biggest unlock wasn't any individual role — it was realizing that the rules are what make speed possible. I'd build the governance layer first next time, before writing a single line of application code.
