**PROJECT OVERVIEW**
- **What's the broader product or company context this codebase belongs to?** *Give a short description of what the product does and who it's for.*
- **What's the primary goal or responsibility of this codebase?** *Describe the main functionality, domain, or feature it supports.*
- **What are 1–2 core workflows or use cases that this codebase powers?** *Think of common user flows, backend jobs, or business processes.*
**BUSINESS CONTEXT + DOMAIN KNOWLEDGE**
- **What business rules or compliance requirements shape this code?** *GDPR, SOX, industry regulations, business logic that drives technical decisions.*
- **Any industry or domain-specific terminology or acronyms we should understand?** *Define terms that would be confusing to someone new — e.g., "SKU", "TSP", "tenant".*
- **What's the "why" behind major architectural choices?** *Business reasons for tech decisions, trade-offs made, constraints that influenced design.*
**CURRENT STATUS + EVOLUTION**
- **What stage is this codebase in?** *Is it early-stage, in active development, stable and in production, or in maintenance mode?*
- **Have there been any major architectural shifts or technical constraints that shaped the current system?** *Migrations, rewrites, performance bottlenecks, scaling challenges.*
- **Are there any incomplete components, known edge cases, or areas under active refactor?** *Include workarounds, technical debt, or planned improvements.*
**AREAS TO IGNORE**
- **Are there specific file paths or directories that aren't relevant?** *List directories or files that are obsolete, unused, or can be ignored during development or analysis.*
