Architecture and product decisions
Architecture and product decisions
Section titled “Architecture and product decisions”The app is deliberately small, local-first and content-driven. The supporting engineering choices are documented in Research decisions, while the detailed constraints live in their respective implementation specifications.
Major accepted directions
Section titled “Major accepted directions”- Local-first mobile experience: spelling attempts work offline.
- Optional account and cloud sync: providers authenticate; cloud state supports backup and convergence.
- Shared TypeScript learning engine: client and server replay the same deterministic evidence rules.
- Immutable content plane: word packs, schedules and audio can be versioned, cached and consumed offline.
- Simple service topology: a small Node API and Azure SQL, not presumed Kubernetes/microservice infrastructure.
- Documentation as code: ADR 0001 and interactive Structurizr diagrams.
Choices requiring further validation
Section titled “Choices requiring further validation”Some accessibility, native UI automation, audio distribution and operational sizing choices remain deliberately open. See UX implementation, Implementation plan and Quality checklist.
A decision described as proposed is not a completed implementation.