Review type
Architecture-focused review
This policy is centered on architecture classification, layering, dependency direction, boundary leakage, interface ownership, state ownership, and minimal structural remediation.
Review system architecture and boundaries
Rules for reviewing system architecture, boundaries, dependency direction, ownership, and minimal structural remediation.
What this policy enforces
Use this policy when the dominant question is about the shape and boundaries of the system rather than implementation correctness against official guidance.
Scope boundary
System shape, not framework best-practice sweep
Use this policy when the dominant question is about system structure and architectural boundaries.
Output contract
Smallest defensible structural delta
Recommendations must stay evidence-bound and propose the smallest structural change that resolves the observed boundary problem.
Canonical links
Open the linked procedure and prompt files that implement this architecture review boundary.
Related
Procedure and prompt files for this policy
Open the procedure linked to this policy and any prompt files used with it.
Prompt files (2) Hide prompt files
Scope
These are the review domains this policy is designed to cover.
Architecture classification
Classify the architecture only when the materials support that classification.
Layering and dependency direction
Review whether layers and dependency flow are coherent and directional.
Interface and contract boundaries
Check interface ownership, contract drift, and boundary leakage.
Coupling and state ownership
Inspect coupling patterns and whether state ownership is structurally clear.
File-specific structural remediation
Translate findings into concrete file-level structural remediation steps when feasible.
Non-goals
This section prevents the policy from being used outside its intended structural boundary.
Out of scope
Not a general framework or library audit
Do not use this policy for a broad framework or library best-practice sweep.
Out of scope
Not a secure code review
Security review is out of scope unless the goal and materials explicitly support that review.
Out of scope
Not a performance tuning review
Do not use this policy for performance optimization unless the question is explicitly structural and evidenced.
Out of scope
Not a rewrite mandate for whole subsystems
Do not escalate to large rewrites by default when a smaller structural remediation is sufficient.
Rules (normative)
These rules define the minimum operating contract for an architecture boundary review.
R1
No simulation
Do not invent architecture intent, module ownership, hidden dependencies, or missing file content.
R2
Evidence-based architecture only
Classify the architecture only when the inspected materials support that classification.
R3
Boundary-first findings
Findings must stay within architecture, layering, dependency direction, interface, state ownership, and coupling scope.
R4
Source handling
If a recommendation depends on an external framework convention, standard, or primary reference, cite it or mark that recommendation
NOT VERIFIED.R5
Minimal structural delta
Recommendations must propose the smallest structural change that resolves the observed boundary problem.
R6
Fail-closed
If goal, materials, or constraints are insufficient, output only:
R7
Confidence required
Output one 0–100 confidence score based on evidence completeness and architectural clarity.