practice
Evolutionary Architecture
Designing for guided, incremental change rather than trying to get the structure right once, up front.
The premise is that requirements will change in ways nobody can predict, so the useful property of an architecture is not correctness on day one but the cost of changing it on day 500.
In practice this means: keep decisions reversible where reversal is cheap, defer the expensive irreversible ones until the last responsible moment, and — the distinctive part — encode the qualities you care about as automated fitness functions that run in CI. A layering rule that is checked by a test is an architecture; a layering rule that lives in a slide deck is a wish.