Orchestration — Conceptual Overview
Audience: Implementers, Architects, SDK Authors Governance Rule: DGP-30
1. What Orchestration Refers To
Orchestration in MPLP refers to the cross-cutting coordination dimension that spans across Context, Plan, Confirm, and Trace modules during lifecycle execution.
Orchestration is not a standalone component. It is a conceptual boundary that describes the responsibility area where multiple modules interact to produce coherent lifecycle behavior.
2. Conceptual Areas Covered by Orchestration
Orchestration concerns the following areas:
| Conceptual Area | Description |
|---|---|
| Execution Ordering | Relates to how Plan steps are organized based on declared dependencies |
| Agent Coordination | Concerns the assignment of work based on agent_role declarations |
| State Consistency | Is involved in maintaining PSG coherence across module interactions |
| Lifecycle Participation | Interacts with L2 state transition rules at lifecycle boundaries |
| Event Correlation | Relates to pipeline_stage and graph_update event semantics |
3. What Orchestration Does NOT Do
Orchestration explicitly does not:
- ❌ Define specific scheduling algorithms
- ❌ Mandate centralized vs. distributed execution models
- ❌ Prescribe concurrency or parallelism strategies
- ❌ Define resource allocation policies
- ❌ Enforce specific timeout or retry policies
- ❌ Constitute an independently implementable module
4. Where Normative Semantics Are Defined
The normative semantics related to orchestration are NOT defined on this page.
They are distributed across:
| Normative Source | What It Covers |
|---|---|
| L2 Coordination & Governance | Module lifecycles, state transitions, SA/MAP profiles |
| L3 Execution & Orchestration | PSG management, event bus, drift detection, rollback |
SA Invariants (sa-invariants.yaml) | 9 rules for single-agent execution |
MAP Invariants (map-invariants.yaml) | 9 rules for multi-agent coordination |
| Golden Flows (GF-01 ~ GF-05) | Concrete execution scenarios with expected outcomes |
5. Conceptual Relationships
Orchestration interacts with the following protocol elements:
6. Reading Path
To understand orchestration-related normative semantics, read:
- L2 Coordination & Governance — Module lifecycles and state machines
- L3 Execution & Orchestration — Runtime behavior
- L1-L4 Architecture Deep Dive — Advanced topics
- Golden Flows — Concrete execution examples
7. Relationship to Other Kernel Duties
| Kernel Duty | Conceptual Relationship |
|---|---|
| Event Bus | Orchestration relates to event emission; Event Bus concerns routing |
| State Sync | Orchestration interacts with PSG updates; State Sync concerns consistency |
| Transaction | Complex orchestration may involve atomic state considerations |
| Error Handling | Orchestration relates to failed state transitions |
| Coordination | MAP orchestration involves multi-agent coordination concepts |
Governance Rule: DGP-30 See Also: Orchestration Anchor (Normative)