Orchestration Economics: The Third Law: Workflow Intelligence Secures Control (Chapter 10)
The first two laws describe what you own. The Third describes how you work and whether that matters.
This is the latest excerpt from AGNT: The Orchestration Economics Manifesto - An Investment Framework for the Agentic Era. Each Thursday, I explore a major theme of the Manifesto and unpack the frameworks, adding extra context with more recent developments. Note: The figures and sequential references are taken directly from the larger Manifesto.
Consider the insurance workflow once again.
The master agent has processed 50,000 claims over eighteen months. Its pricing agent has been invoked on all 50,000. Both have learned. Both are better than they were on day one. But they have learned different things, and the difference is structural.
The pricing agent has learned to price better. Its risk models have sharpened. Its calibration has improved. It handles edge cases with increasing precision. This is specialist learning: deep, narrow, and subject to diminishing returns. There are only so many ways to improve pricing. The capability curve flattens.
The master agent has learned something else. It has learned coordination. It knows which specialists work well together and which combinations produce errors. It has been discovered that certain claim types need medical records enrichment before pricing, while others can proceed directly to adjudication. It has been noticed that claims submitted in Q4 from manufacturing clients require a different decomposition than identical-looking claims submitted in Q2, because year-end inventory adjustments change the risk profile in ways the pricing agent alone cannot detect.
This is meta-expertise: the knowledge of how to make domain experts effective together. It is the accumulated workflow intelligence of the Orchestration Layer that now directs routing logic, exception handling, specialist sequencing, and failure recovery. Every interaction teaches the coordinator something the specialists never see. The specialists see their inputs and their outputs. The coordinator sees the entire workflow: what was tried, what failed, what succeeded, why the sequence mattered, and how the context affected the outcome.
A new competitor can license every specialist agent in the system. It cannot download the coordination intelligence that enables those specialists to work effectively together. It must learn it from scratch, one orchestrated interaction at a time, while the incumbent continues to compound.
This is the Third Law: workflow intelligence is the accumulated operational choreography of how work gets coordinated. It creates switching costs that grow with every interaction.
The question is: How strong are those switching costs?
The Weakest Law
The claim that coordination compounds while specialist capability flattens is intuitive. It is also, as a universal law, overstated.
The Google-DeepMind-MIT study, which reported an 81% relative improvement in structured financial reasoning, also found the opposite pattern in other domains. Across all benchmarks, the mean multi-agent improvement was -3.5%. In sequential planning tasks, every multi-agent architecture tested performed 39-70% worse.
Coordination did not compound. It destroyed value.
The study also found that coordination benefits are task-contingent. They depend on whether the problem is decomposable and parallelizable, not on universality. It identified a capability saturation threshold: once single-agent baselines exceed approximately 45% accuracy, adding coordination yields diminishing or negative returns.
More troubling for the Third Law is what happens when specialists learn to coordinate themselves.
In December 2025, Meta FAIR published Self-play SWE-RL, a study in which a single software agent, with no coordinator or multi-agent orchestration, autonomously learned to navigate complex codebases through self-play. The agent generated its own bugs, solved them, and generated harder bugs based on its failures. It required only access to the raw codebase: no human-curated issues, no test suites, no workflow documentation. Through sustained interaction with the environment alone, the agent outperformed the human-data baseline across the entire training trajectory, improving by 10.4 points on SWE-bench Verified.
The implications for the Third Law are inescapable. If an agent can learn the workflow logic of a complex software repository through observation and interaction, then what prevents a sufficiently capable agent from learning the workflow logic of a claims processing system? Or an integration layer? Or a supply chain?
The answer is not “nothing”. Real barriers exist. But the barriers are weaker than those protecting the first two laws. Intent capture (the First Law) requires a relationship with the human who expressed the goal. You cannot learn that from observation. Operational context (the Second Law) requires years of accumulated experience. You cannot synthesize 50,000 claims outcomes from scratch. Workflow choreography (the Third Law) requires an understanding of how processes connect. That, as Self-play SWE-RL demonstrates, is increasingly learnable.
The Third Law is real. It is also the law most likely to be tested by the market.
When Workflow Holds
If the Third Law does not hold universally, the investment question becomes: under what conditions does it hold? Three conditions determine whether workflow intelligence creates a durable advantage:
When workflow embeds operational context that emerged from practice rather than documentation. The claims processing logic encoded in an insurance platform is not merely a sequence of steps. It includes exception handling paths that emerged from thousands of edge cases, regulatory compliance requirements that proved necessary through actual enforcement actions, and specialist routing patterns that were refined by observing which combinations produced errors. This is workflow intelligence that cannot be learned from a manual because it was never written in one. It emerged from sustained operational interaction. It is, in effect, the Second Law expressing itself through workflow.
When switching costs are behavioral rather than technical. Traditional software lock-in is technical: data migration costs, integration reconfiguration, and user retraining. Orchestration lock-in is behavioral. When an organization’s operational rhythm has adapted to how one orchestrator decomposes intent, validates outputs, and handles exceptions, switching means rewiring the operational patterns of every process that adapted to the incumbent’s coordination intelligence. The new system does not just lack data. It lacks the judgment that emerges from years of orchestrated experience. It begins as a stranger who is technically capable but operationally naive.
When the domain involves decomposable, multi-step workflows rather than sequential reasoning. Recall that research has demonstrated that centralized coordination produced dramatic gains on parallelizable tasks such as financial reasoning involving multiple data sources, cross-reference synthesis, and distributed analysis. However, it destroys value on sequential constraint-satisfaction tasks where coordination overhead fragments reasoning capacity. The Third Law holds in insurance claims, supply chain logistics, enterprise procurement, and regulatory compliance. It fails in domains where a single capable agent outperforms any coordinated team.
These conditions produce a diagnostic that maps directly to investment decisions. Consider an integration middleware platform. This company’s entire value proposition is connecting System A to System B with the correct data transformations and sequencing. Its moat is integration choreography. That is precisely what MCP and A2A dissolve.
The platform coordinates workflows but does not accumulate any proprietary operational context. Its moat is integration friction. When protocols standardize connectivity, the workflow knowledge becomes replicable. An agent using MCP can discover and connect to the same endpoints. The choreography the platform has encoded over the years can be learned in weeks.
This is the most exposed position in the agentic economy: workflow orchestration without context.
Now consider a vertical insurance platform that has amassed decades of encoded claims-processing logic, underwriting rules, and policy-administration choreography. This looks like a deep workflow moat. But examine what is defensible. It is not the workflow sequence. It is the domain knowledge embedded in the workflow: the understanding of how insurance works in practice, the exception paths that emerged from millions of claims, and the regulatory requirements discovered through enforcement rather than documentation.
Strip away the context, and the workflow is learnable. The moat is context (the Second Law) expressing itself through workflow (the Third Law). The position holds due to the Second Law’s advantage, not because of the Third.
The same pattern appears outside software. In February 2026, Goldman Sachs revealed it had spent six months embedding Anthropic engineers within its teams to build Claude-powered agents for KYC compliance and trade accounting. These are document-heavy, rule-intensive workflows that combine data extraction with regulatory judgment217. The bank’s CIO described the agents as “digital co-workers” for processes that are “scaled, complex, and very process-intensive”. The agents review documents, extract entities, assess ownership structures, and trigger compliance checks. Internal tests showed that onboarding timelines collapsed by approximately 30%.
This is a direct test of the Third Law. KYC compliance is a multi-step workflow involving identity verification, sanctions screening, beneficial ownership analysis, and ongoing monitoring. A third-party compliance platform that merely choreographs these steps by connecting document scanners to screening databases and case management systems holds a workflow moat that agents can learn from. Goldman’s agents are learning it now.
However, the bank’s decades of compliance outcomes represent an invaluable advantage because they are an asset that the agent platform cannot replicate:
Which edge cases triggered regulatory action?
Which documentation patterns correlated with genuine risk versus administrative friction?
Which client structures required enhanced due diligence not because the rules said so, but because enforcement history revealed it.
That operational context was accumulated through millions of onboardings across every jurisdiction where the bank operates. It is what makes Goldman’s own orchestration position defensible, even as third-party KYC platforms face exposure. The workflow is learnable. But this kind of institutional memory is not.
The pattern for the Third Law, then, requires an important nuance: workflow moats are defensible to the extent that they embed operational context. The choreography, the routing logic, and the integration patterns: these elements of pure workflow are learnable and therefore vulnerable. Workflow that encodes irreplaceable operational intelligence is defensible because of the context it contains, not because of the workflow itself. That makes the Third Law a derivative moat.
The Switching Cost Asymmetry
Even where coordination learning is moderate, switching costs are real, and they compound over time. Traditional software lock-in is largely static: migration costs remain relatively constant, driven by data transfer, integration reconfiguration, and user retraining. These are significant, but they are visible and quantifiable.
Orchestration behaves differently. It is dynamic. Each interaction deepens the system’s embedded knowledge through every optimized workflow, learned exception, and validated combination of specialists. The gap between what the incumbent system knows and what a replacement must reconstruct widens continuously.
Crucially, this lock-in is not immediately visible. Unlike traditional systems, its cost cannot be fully modeled upfront because it resides in accumulated context: decomposition logic, exception handling paths, and coordination patterns that only emerge through sustained operation. Organizations only grasp the magnitude when they attempt to switch and discover that their operational rhythm depends on capabilities that exist nowhere else. Orchestration lock-in is invisible until you try to switch.
Most importantly, the nature of the lock-in shifts. Traditional lock-in is technical. These Traditional systems bind through technical dependencies while leaving underlying processes intact. When an organization switches from Oracle to SAP, the underlying business processes.
Orchestration systems bind through behavior. Switching does not simply require moving data. It requires reconstructing the decision-making patterns and operational habits that have evolved in response to the incumbent’s coordination intelligence. The new system does not just lack information. It also lacks judgment.
This is the genuine contribution of the Third Law to the investment framework. Even in domains where the coordination learning curve is moderate rather than exponential, where agents can, in principle, learn the workflow, the switching cost still grows with operational history.
The question investors must ask is not: “Does coordination compound forever?” Rather, what matters is: “Do switching costs compound fast enough to create a defensible position before the next generation of agents learns to replicate the workflow?”
The Contestability Window
The Third Law creates urgency even though it is the weakest of the three conditions. That’s because, unlike previous technology cycles, the Orchestration Layer is not reserved for technology companies. Orchestration is defined by owning the control plane where intent enters and coordination happens. That control plane can live anywhere. Workday can be the orchestrator for HCM workflows. But so can an insurance company for claims processing, a bank for credit analysis, a manufacturer for supply chain optimization.
For the first time, the strategic layer of the stack is contestable by companies that own domain expertise, customer relationships, and operational context, and not just companies that write software. Physical-world operators possess inherent advantages precisely because their workflow intelligence arises from irreplaceable operational reality. The insurance company that builds its own Orchestration Layer accumulates coordination intelligence that no third-party platform can replicate because the platform does not process claims, does not see adjuster patterns, does not experience seasonal variations, and does not learn the exception paths that emerge from actual operations.
The risk for these companies is not their capability. It is speed.
Early orchestrators compound their advantage with every interaction. Later entrants start from zero in a market where the leading orchestrator has thousands of workflows of accumulated learning. The gap is not just difficult to close. In domains where the Third Law holds, it may become structurally unclosable. This is why the Third Law matters despite its weakness. It is not the foundation of defensibility. It is the accelerant. Proximity to user intent tells you where to stand. Context tells you what to accumulate. Workflow tells you that the window for doing both is closing.
The views and opinions expressed in this publication are those of the author alone and are based on publicly available information. The expressed views and opinions do not constitute investment advice, a solicitation, or a recommendation to buy or sell any security or financial instrument. The author may hold positions in the securities of companies mentioned. Certain companies referenced may be current or former clients of, or counterparties to, the author or affiliated entities; such relationships will be disclosed where applicable. Past performance is not indicative of future results. To the fullest extent permitted by applicable law, the author does not accept any liability for any loss or damage arising from reliance on this content. Readers should conduct their own independent due diligence and consult a qualified financial advisor before making any investment decision.