Composition

Overview

Why one pattern per workflow does not mean one pattern per organisation

• A common objection to the framework's "one pattern per workflow" discipline is that real organisational workflows are too complex to fit a single pattern. The objection is correct at the level of the named workflow and wrong at the level of cognitive units. The real workflow is a composition of component workflows, and each component workflow can be separately allocated to one of the four cognitive patterns.
• The composition itself is governed by the orchestration discipline. The canonical example is the underwriting platform: Encapsulated Utility ingests and enriches submissions, Autonomous Agency triages routine cases within a defined mandate, Cognitive Partnership supports the underwriter's reasoning on the cases that warrant deeper attention. Three patterns, one platform, each pattern's allocation defensible at its own component workflow. Orchestration holds the seams between those patterns.
• The cognitive work at the seams is itself meaningful: the Delivery phase of one pattern's workflow is the Frame phase of the next, and the handoff has to be designed as deliberately as either of the patterns it joins. The composition principle is what makes multi-pattern orchestration coherent rather than chaotic, and what gives the framework purchase on enterprise-scale work that no single pattern would describe honestly on its own.