Core Patterns Must Be Foundational
Rule
Core patterns must represent foundational architectural primitives, not specific strategies or implementations.
Rationale
Prevents elevation of context-specific or replaceable approaches into the core architecture, maintaining long-term stability.
Applies To
- pattern-promotion-workflow
- architect decision review
Example
Reject promoting dual-path-routing to core because it is one routing strategy, not a universal primitive.