Orchestrator

One session that routes work into lanes, audits what comes back, owns integration, and never implements. The rules that make it work are the non-obvious ones: exactly one live orchestrator at a time, because two of them routing the same board is the same collision class as two sessions building the same item; delegation moves the executor and never the standard; and context is the orchestrator's scarcest resource, which makes delegation a context-preservation technique before it is a throughput one.