An architectural decision chooses whether a service should exist, which trade-offs a system accepts, and whether an earlier direction still fits new evidence. It is judgment, not merely coding. section 10.8.1
Evaluate an architectural decision by asking:
- Does the proposed service solve the right user problem, including needs hidden behind stated requirements? section 10.8.1
- Does its trade-off remain correct after incidents and new system knowledge? section 10.8.1
- Could automation propagate the decision into dependent services before anyone detects the mistake? section 10.8.1
Fast construction, expensive mistake
An agent builds a service in an afternoon, and other services integrate with it before review. If the architectural decision is wrong, the cost includes discarded code and subtle downstream effects—not merely the afternoon spent building. section 10.8.1





