Volatility Mapping

Identify architectural seams by what is likely to change, not by domain nouns or function names. This is based on Volatility-Based Decomposition (VBD) from "Righting Software" by Juval Löwy: functional/domain decomposition looks clean today but rots as requirements shift, because "what the system does" and "what's likely to change" are different axes.

When invoked

Before writing any code or proposing a module/service breakdown, do this analysis first and present it to the user for confirmation.

Steps