The Conductor Protocol treats flow graphs not as programs to execute, but as blueprints of intent that can be compiled into optimized execution strategies before a single node runs.

Traditional platforms interpret flows imperatively — "do this, then this, then this." The Conductor interprets flows declaratively — "here is what needs to happen; let me figure out the fastest way to make it happen."

The compilation step produces an ExecutionStrategy: a sequence of phases, where each phase contains units that run concurrently, and each unit represents one or more original nodes merged or classified for optimal execution.