Why Anthropic’s "Agent Teams" is missing the most important part: Governance.

We’ve been shipping multi-agent orchestration since January. Here is why orchestration is the easy part—and why "Trust" is the real boss battle. Anthropic just announced Agent Teams. It’s a great validation of the category, but while the giants are focusing on the how of connecting agents, we’ve been obsessing over the should. ​I’ve been building Rigovo Teams for months. 37K lines of code, 8 specialized agents, and one Master Agent later, I’ve realized one thing: The hard problem isn’t orchestration. It’s trust . ​1. Memory without Governance is just "Accumulated Hallucination" ​Most multi-agent systems use a shared memory bank. If Agent A hallucinates an API call and Agent B reads that memory, the mistake is now "institutional knowledge." ​In Rigovo, we built flat semantic memory using pgvector, but with a twist: ** **The Quality Gate . Every memory entry must pass through 24+ deterministic gates—checking for phantom APIs, secret leakage, and structural violations—before it’s allowed