Project teams keep making conflicting trade-offs on master data and automation of controls. What foundational artifact should architecture publish?
Select an answer to reveal the explanation.
Short Explanation
Principles are the house rules on the fridge—master data once, automate policy where it pays off—so every project isn’t inventing new morals. Written principles make trade-offs consistent instead of random.
Full Explanation
Published architecture principles provide durable guidance for recurring trade-offs across projects, such as preferring a single mastered representation of critical entities or encoding policy in automated controls where practical. Without explicit principles, teams optimize locally and recreate conflicting patterns. A maintained catalog anchors reviews and onboarding in shared intent.