This is Part 2. In Part 1 I described the architecture — the team, the tool scoping, the decision tree. Here's what I left out: what goes wrong.
Orchestration isn't magic. Four failure modes account for almost everything that's gone wrong on my team. None is exotic. All are structural — which is the good news, because structural problems have structural fixes.
1. Agents assert what they haven't verified
Klaus, my bug-hunter, once reported "SOUL.md doesn't exist." It existed the whole time — in a hidden directory his search tool didn't traverse by default. He didn't lie. He trusted a negative result from a bounded search, which is the same failure wearing better clothes.
Fix: every agent now carries one rule — never conclude absence from a single method. "Not found with X" is allowed. "Doesn't exist" is not.
