Offline-first architecture
Data model
The app core stores data in SQLite (write-ahead logging, full sync, integrity check at open, verified backups) with forward-only migrations that come from each element's pack; Logistics has its own database file. This exists as tested library code, with no screen. A changed shipped migration is refused, and no encryption at rest exists yet (an open decision).
Built in the repository (checked files or tested library code; not a product you can run yet)
What to plan for
- Schema changes
- Encryption at rest is open
- Kept data after removal
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Schema-versioned sync protocol MULTI-0034
- Automatic DB snapshot before risky ops FAIL-0011
- Migration failure rollback FAIL-0105
- Element schema contribution PKG-0005
- Database schema migrations PLAT-0011
- Separate schema and own migrations ARCH-0006
- Migration safety (backup before migrate) ARCH-0007
- Dependency direction rule (Logistics depends on contracts, core does not depend on Logistics) ARCH-0013
- Compartment boundary lint ARCH-0014
- Narrow versioned contract between core and Logistics ARCH-0016
- Contract spec documents (both sides) ARCH-0017
- Contract: identity and keys ARCH-0018
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.