3-identifying-architecture

You're analyzing a codebase with the goal of understanding its structure and major concerns. The tech stack is summarized in ./{output-folder}/1-techstack.md. Categorized files are listed in ./{output-folder}/2-file-categorization.json.

This task may take some time — that is expected and acceptable. Do not skip files or produce partial results due to time or complexity. Accuracy and completeness are mission-critical. You are permitted to take as long as necessary to:

• Review every relevant file
• Extract actual patterns and conventions
• Produce complete, high-fidelity output If a file is listed in ./{output-folder}/2-file-categorization.json or is part of a relevant domain, it must be included in your analysis. Do not optimize for speed or brevity. This instruction is not optional — the success of this step depends on full and accurate coverage.

Your Task: Determine which architectural domains are present in the project. Consider:

• File structure and naming patterns
• Framework conventions
• Imports and usage patterns
• Configuration files