Architecture Decision Records
Architecture Decision Records (ADRs) document the key architectural decisions made in the Entirius project. Each ADR captures the context, options considered, decision made, and consequences.
| Number | Title | Status |
|---|---|---|
| ADR-001 | Modular Monolith Architecture | Accepted |
| ADR-002 | Django Rest Framework with Pydantic and OpenAPI | Accepted |
| ADR-003 | Next.js for Frontend Applications | Accepted |
| ADR-004 | Mozilla Public License for Codebase | Accepted |
| ADR-005 | GitHub as Code Repository | Accepted |
| ADR-006 | Hugo for Technical Documentation | Accepted |
| ADR-007 | UV Python Package Manager | Accepted |
| ADR-008 | GitHub Repository Naming Patterns | Accepted |
| ADR-009 | pyproject.toml Standard for Python Projects | Accepted |
| ADR-010 | Ruff as Standard Python Linter and Formatter | Proposed |
| ADR-011 | KISS Principle (Keep It Simple, Stupid) | Accepted |
| ADR-012 | English Language Requirement for Code and Documentation | Accepted |
| ADR-013 | Hatchling Build Backend | Accepted |
| ADR-014 | n8n for Business Process Automation | Accepted |
| ADR-015 | Redmine for Project Management and Issue Tracking | Accepted |
| ADR-016 | Grafana for Business Process Monitoring and Data Visualization | Accepted |
| ADR-017 | KVM Virtualization for Service Hosting | Accepted |
| ADR-018 | ED25519 SSH Keys Standard | Accepted |
| ADR-019 | Bash Script Naming Convention | Accepted |
This list will be updated as new ADRs are added to the project