"Organizations fail when learning is separated from authority.
Standards protect teams from the most common lie: “just this once.” In an architecture review where two constraints collide, the purpose is not to be strict; it is to stay consistent under stress.
In an architecture review where two constraints collide, the request will be framed as pragmatic. Without a clear exception rule, “pragmatic” becomes a loophole. Over time, the standard turns into a suggestion. Be honest about what would change your mind, because without a revisit signal every decision becomes permanent by default. A standard you cannot apply in one pass is not a standard; it is a preference disguised as governance.
James G. March is useful here because it forces precision. Write the boundary in a way someone can enforce without asking you. Keep it short enough to remember under stress.