Architectural preparation deliberately preserves affordable responses to plausible future change without building every imagined capability today. It balances flexibility against the rigidity and cost of speculation. section 4.4
Prepare architecturally when a possible change:
- Is likely during the system’s lifetime and expensive, risky, or slow to address later. section 4.4
- Could affect important contracts, data models, security boundaries, integrations, or ownership. section 4.4
- Would be difficult to reverse, has observable signals, and can be addressed with a small seam, stable contract, ADR, compatibility rule, or test strategy. section 4.4
Last responsible moment
Make consequential architectural decisions late enough to preserve flexibility, but early enough to avoid delivery risk.
