docs: define scouting search domain baseline in ADR-0005
This commit is contained in:
@ -6,7 +6,7 @@ This document will become the central architecture overview for HoopScout v2. It
|
||||
|
||||
## Current Status
|
||||
|
||||
This is still a phase-1 architecture overview, but the repository now has its first accepted concrete technical decision in `docs/adr/0001-runtime-and-development-stack.md`. Later implementation work should follow that corrected baseline unless a future ADR supersedes it.
|
||||
This architecture overview summarizes the accepted technical and domain-decision baseline for implementation. Future model, filter, and UI work should follow the current ADR set unless a later ADR supersedes it.
|
||||
|
||||
## Decision-Driven Development
|
||||
|
||||
@ -25,6 +25,7 @@ The current baseline decision is:
|
||||
- `ADR-0002`: initial project structure baseline
|
||||
- `ADR-0003`: containerized developer workflow baseline
|
||||
- `ADR-0004`: configuration and environment strategy baseline
|
||||
- `ADR-0005`: scouting search-domain baseline
|
||||
|
||||
The current baseline assumes:
|
||||
- Python 3
|
||||
@ -40,6 +41,8 @@ Future runtime and scaffolding work should also follow the developer workflow de
|
||||
|
||||
Future scaffolding should also follow the configuration strategy defined in `docs/adr/0004-configuration-and-environment-strategy.md`, including environment-variable based configuration, a repository-owned `.env.example`, local-only secrets, and a simple initial Django settings approach unless a later ADR supersedes it.
|
||||
|
||||
Future search model/filter/UI implementation should follow the domain semantics defined in `docs/adr/0005-scouting-search-domain.md`, including the separation of position vs role vs specialty, MVP filter scope, and optional vs required dimensions.
|
||||
|
||||
## Future Sections Placeholder
|
||||
|
||||
Future versions of this document may include sections such as:
|
||||
|
||||
Reference in New Issue
Block a user