How the modular monolith divides identity, records, operations, and presentation.
Django application boundaries
Application map
| App | Responsibility |
|---|---|
| accounts | Custom users, sign-up/login, reset flows, and memberships. |
| projects | Project metadata and categories. |
| regressions | Regression definitions, runs, forms, and run services. |
| results | Test results, failure signatures, and grouping behavior. |
| milestones | Milestones and status updates. |
| dashboard | Cross-project and project-level summaries. |
| api | Hashed tokens, scope permissions, serializers, endpoints, and ingestion. |
| common | Choices, shared models, middleware, utilities, and demo commands. |
Current persistence boundary
SQLite is the default local and current deployment profile. PostgreSQL support is on the roadmap, along with finer project-level roles and broader import paths.
API v1 mutation policy
Write endpoints expose POST and PATCH for projects, regressions, and runs. PUT and DELETE are intentionally not enabled in API v1. GET /api/v1/health/ is the only unauthenticated API endpoint.