canon-design-review

To review architecture risks in a pull request, evaluate design quality across bounded contexts, layering, dependencies, and APIs. This process identifies blocking issues grounded in specific file and line evidence before producing a merge recommendation.

Evidence-based design review is a structured assessment that replaces ad hoc architecture checks with rigorous evaluation. It produces PASS, WARN, BLOCK, or N/A verdicts grounded in specific file and line findings for design quality and operational readiness.

Assess bounded contexts and dependency direction by applying a 15-practice evaluation covering layer separation, cohesion, and interface compatibility. This yields explicit scoring and structured verdicts for architectural boundaries in your code changes.

Yes, this architecture review evaluates API versioning and database migrations. It assesses evolutionary design, API compatibility, and schema changes within service boundaries to identify operational and consistency risks before merge.

The best way to score operational readiness and resilience is through weighted scoring across 15 practices including consistency, backpressure, and health checks. This generates an overall merge recommendation based on explicit evidence and rules.

You need an architecture review for evolutionary design when changes involve service boundaries, infrastructure, APIs, or schemas. It ensures long-term evolvability by checking ADR coverage, team ownership, and API compatibility against evidence.