Orchestration d'agents

On 17 June 2026, Fred Plais (co-founder and CEO of Archie, previously CEO of Platform.sh) described a profile he calls recent and still rare: someone who knows the failure modes of agents, knows how to chain them, and can catch an error before it propagates. A day later at DevSummit, Mathieu Grymonprez, Global CDO of the Adeo group (Leroy Merlin, Obramat, Weldom), named the same thing as a hole in the software stack: the missing open source brick covering registry, lifecycle, permissions and skills. The claim recorded against it is blunt: "rien en open source ne marche bien pour ça".

Plais pairs orchestration with a second scarcity, articulating a vision precise enough for an agent to execute without derailing. An agent builds exactly what it is asked and nothing more, so knowing what to ask is the hard part. His reading of the market is that teams keep recruiting for code output, the resource that stopped being scarce.

Grymonprez's worry sits further out: lock-in of enterprise intelligence, the agentic harness, the "adeo.md" file. That is why he watches standard Kubernetes, API portability and memory. Responsibility stays human in his framing: "ce n'est pas la faute de l'agent".

The two notes leave a gap open. One treats orchestration as a competence held by people who are hard to find, the other as software nobody has shipped. Neither says which shortage closes first.