System Proposes, Architect Decides
Rule
All architectural decisions must be proposed by the system and explicitly accepted, rejected, or deferred by an architect.
Rationale
Maintains human-in-the-loop control to preserve architectural integrity and avoid incorrect automated decisions.
Applies To
- pattern-promotion-workflow
- decision records (ADR)
- AEM generation
Example
A promotion output sets decision.status = "proposed" and requires manual update to "accepted".