Coherent refactoring

← Back to concept

Identify the responsibility first

Before a significant refactoring, identify the owner, consumers, dependencies, contracts and tests. State the decision explicitly: responsibility X belongs to Y, so its contract belongs at Z.

Prefer a solution inside the established architecture. If the model contains a concrete contradiction, explain it and propose the architectural change separately. Do not redesign a boundary as an unnoticed side effect.

Preserve comments, stable identifiers and behavior. Move generated output through its source and generator. Keep the diff coherent and exclude unrelated renaming, formatting and cleanup.