Only evidence I can point to is that over a year ago I built a custom ai harness for a corp with no usage caps on anthropic models. Claude taught me all the buzz words as I built long before they were publicly discussed anywhere. From that period try searching for "Orchestrator" hits on google/github etc. My code has it for the agent with the subagent calling toolset, Claude's recommendation. It performed long horizon tasks really well too. Almost exactly like Fable, same persistence, with worse performance of course/accuracy/hallucination. Just had a watchdog script and a validation agent that ran when the main orch claimed it was done and yell at it about what it didn't complete, all on 250k context sonnet.
Now, bundle that basic format with a nice conversational LLM that Anthropic keeps pretending is its own model doing everything by itself with its much bigger context and you get what we have today.
Essentially providers specialize their AI stack + LLM personality + backend fuckery they pretend isn't 90% of model capability into their api spigot. Openai has been focused on 'better chatbot' for the most part and Google appears to have been sitting back and waiting to see what worked first.
Then, quickly with the big perf upgrade with the 'orchestration layer' path, Google had a target to quickly RL on. Thats why you should only be using Agy on Carbon with /Swarm on IMO. Its great. Carbon is fine tuned for orch work. Same reason Fable often performs worse at benchmark tasks than Opus. Its meant to be an Orch not a worker.