architecture-diagramminglisted

# Architecture Diagramming ## Purpose Provide standardized methodology and templates for generating architecture diagrams from codebase analysis. Uses the C4 Model for hierarchical architecture views and Mermaid for diagram rendering. ## C4 Model Overview The C4 Model defines four levels of architecture abstraction: | Level | Name | Shows | When to Use | |-------|------|-------|-------------| | 1 | System Context | System + external actors | Always, the "big picture" | | 2 | Container | Applications, data stores, services | When multiple deployable units exist | | 3 | Component | Internal modules within a container | When analyzing a specific service | | 4 | Code | Classes, interfaces | Rarely, only for critical components | ## Diagram Selection Guide Choose diagrams based on what exists in the codebase: | What You Find | Diagrams to Generate | |---------------|---------------------| | Multiple services/microservices | System Overview (L1), Container (L2), Dependency Graph | | Database schemas/models | ER Diagram | | API endpoints | API Interaction Diagram | | Message queues/events | Event Flow Diagram | | Multi-step workflows | Sequence Diagrams | | Docker/K8s configs | Deployment/Infrastructure Diagram | | Monolith with modules | Component Diagram (L3) | ## Diagram Generation Process 1. Scan project structure to identify components and boundaries 2. Read config files (docker-compose, k8s, CI/CD, infrastructure-as-code) 3. Map entry points, routes, and service comm