Agent Hierarchy

Once more than two agents are working at the same time, the problem stops being capability and starts being traffic. Without a chain of command every agent can talk to every other agent, and you lose the ability to reason about who asked for what. A hierarchy fixes the routes: an agent tasks only its own subordinates and reports upward, and anything else is refused with a message naming the route it should have taken. A director reports to you; a seat marked "chain ends here" finishes in place rather than reporting up, which is exactly what you want when you write "review back to Grok, do not report to me". Because hierarchies resolve by escalation, an agent cannot open a vote to overrule its own manager. Mission Control groups every seat by derived tier, flags vacancies and orphaned branches, and offers Rebind or Promote on the spot, so a team that lost a terminal gets repaired instead of rebuilt — and a counter opens a panel showing every blocked escalation: who tried to reach whom, when, and where it should have gone. You can also write the chain of command for a single prompt, or manage a running org from your phone.