review-arch-consistency

To review architectural consistency, provide a description of the architectural decision and a list of affected components. The review assesses whether changes affecting module boundaries, contracts, or integrations align with established principles and the existing system landscape.

Checking module boundary violations involves verifying that proposed changes adhere to architectural rules and patterns. You need to supply the architectural decision description and affected component list to identify potential conflicts with existing module contracts.

You need an architectural compliance review before merging significant backend changes to confirm they do not introduce circular dependencies or violate the established layering principles of the application.

Yes, you can assess new dependency justifications by reviewing how code changes affect existing layers. The review process identifies new dependency justifications and evaluates their compatibility with the current system landscape.

Evaluating changes to API contracts and integrations is supported by applying the review to modifications affecting contracts or integrations. It assesses compatibility with existing layers and identifies potential architectural drift.

Architectural drift occurs when features violate established architectural principles. Identifying potential conflicts with existing architectural decisions and module contracts helps prevent this drift and maintain system coherence.