Code review: choose the right policy
Routing page for code review policies: architecture review or implementation review against official guidance.
Purpose
This page is the policy router for the code review family.
Use it when you know the task is code review, but you have not yet chosen the correct rule set. Do not treat this page as the normative contract for a concrete run. Choose one of the two policies below and use that as the active policy.
Option 1 — Code Review: Architecture & Boundaries
Use this when the dominant question is about:
- system structure,
- layering,
- dependency direction,
- boundary leakage,
- ownership,
- interface contracts,
- minimal structural remediation.
Open:
- Architecture Boundary Review — policy
- Run the architecture boundary review — procedure
- architecture-boundary-review.system.txt
- architecture-boundary-review.user.txt
Option 2 — Code Review: Implementation vs Official Guidance
Use this when the dominant question is about:
- code or config correctness,
- framework/library/runtime/platform guidance,
- API misuse,
- version-sensitive implementation issues,
- source-backed remediation.
Open:
- Standards-Backed Implementation Review — policy
- Run the standards-backed implementation review — procedure
- standards-backed-implementation-review.system.txt
- standards-backed-implementation-review.user.txt
Quick decision rule
- If the main question is “Is the system structure correct?”, choose Code Review: Architecture & Boundaries.
- If the main question is “Is this implementation correct according to official guidance?”, choose Code Review: Implementation vs Official Guidance.
- If you need both, run them separately, in this order:
- Code Review: Architecture & Boundaries
- Code Review: Implementation vs Official Guidance