Offline-first architecture
Crash and power-cut safety
Atomic writes and journaling so a failure never loses a completed sale.
Planned: listed in the catalog, not built
What to plan for
- Printer prints but sale lost
- Half-written receipt
- Battery drains
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- SQLite WAL mode with synchronous=FULL for money tables FAIL-0001
- Foreign keys and CHECK constraints enforced FAIL-0002
- 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
- Single-process DB access rule FAIL-0008
- Integrity check at startup (quick_check) FAIL-0009
- Periodic full integrity_check FAIL-0010
- Automatic DB snapshot before risky ops FAIL-0011
- Dual-write journal (event log file) FAIL-0012
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.