Choose a review policy for code or system design

Routing page for choosing the correct review policy for architecture, boundaries, or implementation against official sources.

Choose the correct code review policy

Use this page when the task is clearly code review, but you have not yet chosen whether the dominant problem is system structure or implementation correctness against official guidance.

Routing rule

Do not treat this page as the normative contract for a concrete run. Choose one of the two policies below and use that policy as the active contract.

System structure
Choose Architecture & Boundaries
Use this when the main question is: “Is the system structure correct?”
This path is for structural diagnosis, ownership, and boundary correctness.
Implementation correctness
Choose Implementation vs Official Guidance
Use this when the main question is: “Is this implementation correct according to official guidance?”
This path is for framework, runtime, API, and source-backed implementation checks.
When both are needed
Run them separately and in order
If both review types are needed, do not merge them into one run.
Order: 1) Code Review: Architecture & Boundaries → 2) Code Review: Implementation vs Official Guidance.

Choose the exact policy contract

Each option maps to one policy, one procedure, and the matching prompt files.

Option 1
Code Review: Architecture & Boundaries
Use this when the dominant question is about system structure, layering, dependency direction, boundary leakage, ownership, interface contracts, or minimal structural remediation.
This path is for architecture and boundary review, not for implementation-vs-docs checks.
Option 2
Code Review: Implementation vs Official Guidance
Use this when the dominant question is about code or config correctness, framework, library, runtime, or platform guidance, API misuse, version-sensitive implementation issues, or source-backed remediation.
This path is for implementation correctness against authoritative guidance.