Principlev1PR-962
Select collaboration patterns by analyzing task dependencies
Select collaboration patterns by analyzing task dependencies first—pipeline for sequential dependencies, fan-out for independent tasks, consensus for reciprocal dependencies—rather than by preference or habit.
Why This Is a Principle
Derives from The behavior of a system arises from its structure… (structure determines behavior) and The mind operates as multiple semi-autonomous processes… (multiple agents). This is Thompson's and Malone/Crowston's core insight operationalized: given that different dependency types have different coordination costs, analyze dependencies before selecting patterns. It's prescriptive, general, and actionable.