abstraction-architect

Unify duplicated logic into a shared abstraction only after passing evidence-based gates like the Rule of Three, confirming stable recurring patterns, and verifying that call-sites share the same bounded context to avoid premature coupling.

To decide whether to extract or inline duplicated code, evaluate call-site spread, context boundaries, and pattern stability using decision frames like AHA and Locality of Behaviour to determine if centralization outweighs the risk of premature abstraction.

The difference between DRY and WET principles centers on abstraction risk: DRY mandates unifying duplicated logic to prevent redundancy, while WET and AHA principles prioritize inlining code until evidence confirms a stable, necessary shared abstraction.

Avoid the wrong abstraction during refactoring by applying structured evidence-gathering to assess call-site counts and bounded contexts, using Tidy First to sequence changes, and choosing CUPID over rigid SOLID constraints to maintain flexibility.

Bounded context directly affects centralizing duplicated logic by defining context boundaries: unifying logic across disjointed contexts causes harmful coupling, making inlining the correct architectural decision even when code appears syntactically duplicated.