Do Not Merge Across Architectural Layers
Rule
Patterns must not be merged or consolidated across different architectural layers.
Rationale
Preserves architectural clarity by maintaining separation between governance, execution, contracts, and reliability concerns.
Applies To
- pattern-promotion-workflow
- pattern refinement
Example
Do not merge orchestrator-managed-pipeline (execution) with parallel-agent-execution (concurrency strategy).