Contract-First Design

Define the interface/contract for each architectural boundary BEFORE writing implementation code. The contract is what stays stable while the implementation behind it is free to change — this is the actual isolation mechanism, not the module split itself.

When invoked

Use immediately after boundaries are identified (e.g. via volatility-mapping), for every boundary that will be built or touched.

Steps

For each boundary/component: