Conduct a Code Architecture Review

Conduct a comprehensive code architecture review for the following project:

Project description: [what the application does]
Language and framework: [specify]
Current team size: [number of developers]
Age of codebase: [months / years]
Scale: [current users / requests per day]
Growth expectation: [stable / 2x in 6 months / 10x in a year]
Biggest current pain points: [what slows development / causes bugs / makes onboarding hard]
What you are most proud of architecturally: [where it works well]

Paste key architectural files for review:
[Directory structure / key configuration files / sample module / database schema — paste what you have]

Review across these dimensions:

1. OVERALL STRUCTURE
- Does the folder structure reflect domain boundaries?
- Is the separation of concerns clear?
- Coupling assessment (tight vs loose)
- Cohesion assessment

2. DATA LAYER
- ORM and query patterns
- N+1 query risks
- Transaction management
- Migration strategy

3. BUSINESS LOGIC
- Where does business logic live? Should it?
- Fat controllers / anemic models / other anti-patterns
- Testability of business logic

4. API AND INTERFACE LAYER
- Consistency of API design
- Input validation approach
- Error handling consistency

5. DEPENDENCY MANAGEMENT
- Dependency injection usage
- Third-party dependency risks
- Circular dependency risks

6. SCALABILITY CONCERNS
- Bottlenecks at current scale
- Bottlenecks at 10x scale
- Stateless vs stateful components

7. SECURITY ARCHITECTURE
- Trust boundaries
- Sensitive data handling
- Authentication/authorisation architecture

8. TESTABILITY
- Current test coverage assessment
- What is hard to test and why
- Recommended testing strategy

DELIVERABLES:
- Findings prioritised as: Critical / High / Medium / Low
- For each finding: problem, impact, recommended fix, effort estimate
- Top 3 architectural improvements ranked by impact vs effort
- A 6-month technical roadmap based on findings