Growing a Topology Organically
You don't have to design your rig upfront. Start small, add agents as you need them.
The Insight
Start with one agent. It does everything — implementation, review, research. When you notice it spending too much time on QA, add a QA agent and put them in a pod. When you need background research, add a research pod. Each addition solves a specific bottleneck.
You do not need to design the perfect topology upfront. Most good topologies emerge from usage. You discover what works by running agents and noticing where they struggle. The topology evolves to match the actual work.
rig discover fingerprints your existing sessions and drafts a RigSpec from what is already running. If you have agents in tmux sessions, it detects them, infers their roles, and generates the YAML. Your organic topology becomes managed infrastructure — persistent identity, shared memory, snapshot and restore.
When This Applies
When you are new to multi-agent topologies and do not know what shape your rig should take. Also when you have existing agents running ad-hoc and want to formalize them.
When This Doesn't Apply
When you already know exactly what topology you need. If you have built rigs before and have a proven pattern, start with a RigSpec instead of growing into one.