architecture-design

Document software architecture decisions by formalizing reasoning into Architecture Decision Records (ADRs) and mapping system constraints, actors, and data flows using the C4 model. This ensures decisions are traceable, versioned, and auditable for future governance and reviews.

Design brownfield code migrations by applying architecture reasoning to existing system structures, mapping current boundaries and data flows with the C4 model, and capturing migration trade-offs in ADRs to ensure constraints are traceable throughout the transition.

The two-pass review process enforces architecture design doc quality by first checking completeness for problem coverage and traceability, then evaluating simplicity and better alternatives to prevent premature convergence on a single pattern before finalization.

Use ADRs and C4 diagrams for feature planning when you need to formalize system boundaries, capture fitness evaluations, and ensure architecture decisions are versioned and auditable before development begins.

Yes, the C4 model works for greenfield system design by mapping context, containers, components, and code levels to formalize architecture reasoning, identify actors and data flows, and capture decisions in ADRs for future traceability.

Evaluate architecture fitness during PR reviews by mapping proposed changes against existing ADRs and C4 diagrams to verify constraints, actor definitions, and data flows remain consistent and traceable with the established system design.