This directory contains records of architecturally significant decisions made in this project.
An ADR documents a single decision: the context that drove it, the alternatives considered, and the consequences of the choice. Records are immutable once accepted — superseded decisions get a new ADR rather than an edit.
| ADR | Title | Status |
|---|---|---|
| ADR-0001 | Adopt Spring Boot as REST API Framework | Accepted |
| ADR-0002 | Use Spring Data JPA with SQLite | Accepted |
| ADR-0003 | Implement In-Memory Caching with Spring Cache | Accepted |
| ADR-0004 | Adopt Layered Architecture | Accepted |
| ADR-0005 | Use Lombok to Reduce Boilerplate | Accepted |
| ADR-0006 | Use SpringDoc OpenAPI 3 for API Documentation | Accepted |
| ADR-0007 | Single-Container Docker Deployment | Accepted |
| ADR-0008 | Use Football-Club-Themed Versioning | Accepted |
| ADR-0009 | Use UUID as Primary Key and Squad Number as Natural Key | Accepted |
| ADR-0010 | Full-Replace PUT, No PATCH | Accepted |
| ADR-0011 | Mixed Test Strategy | Accepted |
| ADR-0012 | Adopt Flyway for Database Migrations | Accepted |
| ADR-0013 | Adopt AI-Assisted Development Workflow | Accepted |
| ADR-0014 | Adopt Spec-Driven Development (SDD) | Accepted |