generated from john/python-template
32 lines
1.0 KiB
Markdown
32 lines
1.0 KiB
Markdown
# ADR-0003: Persistence baseline and transition path
|
|
|
|
- **Status:** accepted
|
|
- **Date:** 2026-06-25
|
|
|
|
## Context
|
|
|
|
Architecture targets PostgreSQL baseline (optional MongoDB), while MVP currently runs on SQLite by default. V1 needs a clear transition path without destabilizing ongoing work.
|
|
|
|
## Decision
|
|
|
|
1. Preserve database URL configurability through centralized settings.
|
|
2. Keep SQLite functional for local dev/test and fast feedback.
|
|
3. Treat PostgreSQL as production baseline target for V1 completion.
|
|
4. Keep persistence access behind `transcription.db` runtime/session access points.
|
|
|
|
## Consequences
|
|
|
|
### Positive
|
|
- Clear migration path without immediate broad rewrite.
|
|
- Controlled risk while preserving velocity.
|
|
|
|
### Tradeoffs
|
|
- Temporary dual-path assumptions (SQLite local vs PostgreSQL target).
|
|
|
|
## Alternatives Considered
|
|
|
|
1. **Immediate forced PostgreSQL-only migration**
|
|
- Rejected: higher short-term disruption risk.
|
|
2. **Remain SQLite-only for V1**
|
|
- Rejected: inconsistent with architecture and requirement trajectory.
|