Technical Architecture Document — System Design Spec

# Technical Architecture Document Generator

Generate a comprehensive architecture document for **[System/Product Name]**.

- **System Purpose**: [What it does in 1-2 sentences]
- **Scale Requirements**: [Expected users, requests/sec, data volume]
- **Team Size**: [Number of engineers who will build/maintain this]
- **Timeline**: [When does this need to be live]
- **Tech Stack Preferences**: [Any mandatory technologies]
- **Constraints**: [Budget, compliance, existing systems to integrate with]

### 1. Overview & Goals
- System purpose and scope
- Key stakeholders
- Success criteria (measurable)
- Non-goals (what this system is NOT)

### 2. Functional Requirements
- User stories or use cases (10-15 key flows)
- API consumers and integrations
- Admin/operational requirements

### 3. Non-Functional Requirements
| Requirement | Target | Measurement |
- Performance (latency P50, P99)
- Availability (SLA target)
- Scalability (peak load)
- Security (compliance requirements)
- Data retention and privacy

### 4. System Architecture
- High-level architecture diagram (described as text/ASCII)
- Component descriptions
- Communication patterns (sync vs async)
- Data flow for key use cases

### 5. Data Model
- Entity relationship description
- Key tables/collections with fields
- Indexing strategy
- Data partitioning / sharding approach (if needed)

### 6. API Design
- Key endpoints (REST or GraphQL)
- Request/response schemas for critical operations
- Authentication and authorization model
- Rate limiting and throttling strategy
- API versioning approach

### 7. Infrastructure & Deployment
- Cloud provider and services used
- Environment structure (dev, staging, production)
- CI/CD pipeline design
- Container/orchestration strategy
- Monitoring and alerting setup

### 8. Security Architecture
- Authentication mechanism (OAuth2, JWT, sessions)
- Authorization model (RBAC, ABAC)
- Data encryption (at rest, in transit)
- Secrets management
- Audit logging
- Threat model (top 5 threats and mitigations)

### 9. Reliability & Operations
- Failure modes and recovery strategies
- Backup and disaster recovery plan
- On-call and incident response process
- SLO definitions and error budgets

### 10. Migration & Rollout Plan
- Phased rollout approach
- Feature flags strategy
- Rollback procedures
- Data migration plan (if applicable)

### 11. Open Questions & Decisions Needed
- List of architectural decisions that need stakeholder input
- Trade-offs that need team discussion
- Unknowns that need research/spike

---

Generate the COMPLETE document. Use technical depth appropriate for a senior engineering audience. Include specific technology recommendations with justification.