architecture-review

Architecture review identifies whether new code fits within module boundaries and aligns with design intent. Provide your PR diff and architecture documentation—ADRs, design docs, or README—to validate that changes respect established architectural boundaries and dependency direction.

Review boundaries when introducing new modules or services, when existing components' responsibilities expand, or when dependencies increase or cycles are suspected. This prevents architectural drift and ensures design decisions remain enforced as the codebase evolves.

One-way dependencies follow design intent—Component A depends on B, but B doesn't depend on A. Cyclic dependencies create tight coupling and maintenance risk. Architecture review confirms dependencies flow in the intended direction and identifies unexpected cycles before they degrade system structure.

Yes. Architecture review ensures design decisions are documented through ADRs (Architecture Decision Records) and design documentation. It validates that boundary definitions and responsibility assignments match the actual implementation and remain aligned as the system grows.

Architectural drift occurs when code changes incrementally violate boundaries or create unintended dependencies. Architecture review prevents drift by validating each PR against established boundaries, ensuring consistent enforcement of design intent throughout development.