hatch3r-architecture-review

To document architectural trade-offs, evaluate the options, constraints, and consequences for your platform change, then generate a template-compliant architectural decision record capturing the formalized outcome.

An architecture review for refactoring detects ambiguity, gathers prior decision context, performs trade-off analysis on options, and outputs a compliant architectural decision record to formalize the component change.

To write an ADR that supersedes previous decisions, read existing records, document the new problem and options, and update affected documentation with explicit supersession handling to resolve conflicts.

Yes, the architecture review workflow applies to greenfield software design by defining decision problems, constraints, and options to formalize new architectural directions into compliant decision records.

You need an architectural decision record for a library change when evaluating trade-offs, capturing external research, and documenting consequences to ensure repository-safe decision governance across the codebase.

The best way to formalize new architectural directions is to run an architecture review that evaluates constraints and options, producing a template-compliant decision record while updating related specs and documentation.