Orchestration is where identity fabrics quietly fail. Admin flows and user journeys get built by different teams on different timelines, and the technical integrations underneath them are usually somebody’s third priority. What emerges is what Martin Kuppinger calls “vibe coding chaos”: ad hoc automation that works until it doesn’t. Agentic AI makes that much harder to live with, because software that initiates its own actions needs orchestration somebody can actually govern.
In this opening keynote, Martin Kuppinger makes the case for treating orchestration as a design discipline in its own right. He looks at the administrative and user-facing layers separately from the technical plumbing underneath, points out where each of them tends to break, and sets out how to keep orchestration governed as fabrics get larger and more agentic. The closing section offers a rough test for how much of your own orchestration was designed, and how much of it simply accumulated.
