Offline-first architecture
Local database
The recommended stack uses SQLite with write-ahead logging; a spike to confirm has not been done.
Not decided
What to plan for
- Corruption recovery
- Migration
- File locks
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Price drop applies to all LIC-0019
- SQLite WAL mode with synchronous=FULL for money tables FAIL-0001
- Single-writer queue FAIL-0003
- Busy-timeout and retry policy FAIL-0004
- Periodic WAL checkpoint (PASSIVE/TRUNCATE at idle) FAIL-0005
- WAL file kept with DB on copy/move FAIL-0006
- Pin SQLite ≥3.51.3 (WAL-reset bug fix) FAIL-0007
- Monotonic clock for ordering FAIL-0034
- Wallet payment shown but never arrived FAIL-0088
- Fake payment screenshot defense FAIL-0089
- Element catalog database PKG-0001
- Local-only embedded database PLAT-0010
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.