Analyze the attached repositories thoroughly. Generate a structured, exhaustive "System Architecture & Feature Impact Reference Document".
The goal of this document is to enable an AI in the future to analyze any Business Analyst (BA) user story and determine the exact technical, architectural, and role-based impact WITHOUT reading the codebase again.
Provide the documentation in clear Markdown covering the following sections:
1. System Domain & Ubiquitous Language (Glossary)
- Core business domain breakdown.
- Domain dictionary: Define every business concept/term and map it to its corresponding code entity/model.
2. Comprehensive Role-Permission & Feature Matrix
- A complete Markdown table with:
| Role / Persona | Permitted Business Actions | Accessible UI Routes / Menus | Assigned Permissions / Policies / Claims |
3. End-to-End Traceability Catalog (The Core Feature Index)
Group by feature domain / module. For EVERY business operation/feature, provide:
- Feature Name & Business Purpose
- Triggering UI Component: Exact route, menu title, and UI file path (e.g., `src/app/pages/...`).
- Entry Point API: HTTP Method, URL Route, Controller/Endpoint class and file path.
- Core Business Logic: Handlers, Service classes, Middleware, and Background jobs involved (with exact file paths and method names).
- Data & State Layer: Entities, tables, migrations, or cache keys affected.
- Security/Authorization: Policy, role, or claim required to execute this step.
4. Data Flow & Integration Lifecycle
- Detail the end-to-end lifecycle for primary business flows (from user click -> UI state -> API request validation -> domain execution -> database commit -> external events/webhooks).
- Include sample payload schemas (Request DTO / Response DTO / Event contracts).
5. Technical Impact Blueprint (Where Code Lives)
- Directory map categorizing where to implement:
- New API Endpoints & Request validation
- Business logic & Domain handlers
- Database migrations / Repository queries
- UI Views, Routes, State management, and Components
- Specific architectural patterns used (e.g., Clean Architecture, CQRS, MediatR, Event-Driven, Repository Pattern) and conventions to follow when modifying them.
Be precise, omit generic boilerplate descriptions, and include exact class names, interfaces, endpoints, and file paths.