AuraLog is designed as a modular, API-first web application that follows clean separation of concerns. It uses a layered architecture for flexibility, maintainability, and scalability.

• Responsibility: Handle HTTP requests/responses
• Contents: Routes, request validation, auth decorators
• Example: MoodController, AuthController

• Responsibility: Business logic
• Contents: Mood calculations, user auth, summaries
• Example: MoodService, AuthService

• Responsibility: Communicate with SQLite using Dapper
• Contents: SQL queries, connection handling
• Example: MoodRepository, UserRepository

• Responsibility: Core data structures and contracts
• Contents: DTOs, database models, request/response types
• Example: MoodEntry, User, DashboardSummaryDTO

Dapper is used for performance and SQL-first control, avoiding heavy ORM overhead.

• Users
  • Id (PK), Email, PasswordHash, CreatedAt
• MoodEntries
  • Id (PK), UserId (FK), Date, Mood, Comment, CreatedAt

❗ Each MoodEntry is tied to a specific user via UserId.

AuraLog uses JWT (JSON Web Token) for stateless, secure authentication.

1. User registers or logs in
2. Server generates a JWT token
3. Token is stored on client (e.g., in localStorage)
4. All protected endpoints require Authorization: Bearer <token>

Middleware checks token validity and user identity for secure access.

• Passwords are hashed securely (e.g., using BCrypt).
• JWT tokens include expiration and are validated per request.
• Each user can only access their own data via UserId-based authorization.

Controllers → Services → Repositories → Database
                        ↓
                    Models