Architecture Review

Review whether the code keeps the architecture the project itself states: its documented boundaries, dependency direction, seams and contracts. Design rules that hold regardless of a repo's own choices — indirection, YAGNI, cohesion, duplication — are design-review's.

Scope

1. Dependency structure

• runtime import cycles across split modules
• dependency direction that breaks the direction the project's docs state
• DI bags exceeding the seams the project declares
• singleton imports in library modules that should accept injected params — an application reading its own central store is idiomatic and not this finding

2. Extension points

• hard-coded behavior where project docs or an existing sibling seam establish a policy/config point
• private coupling preventing the additive providers or plugins the project declares
• an extension seam built differently from its siblings