Offline-first architecture
Core and logistics isolation
The ARCH module keeps logistics separate from the core POS so a fault in one cannot corrupt the other.
Designed in a document, no code yet
What to plan for
- Contract versioning
- Independent rollback
- Process isolation (not decided)
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Voice input for search (device) L10N-0032
- Product deleted with open tickets FAIL-0079
- Element search/browse in launcher PKG-0026
- Element sandboxing (WASM/permissions) PKG-0033
- Full-text search index (FTS5) PLAT-0021
- 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
- Contract: inventory (INV) ARCH-0019
- Contract: pricing (PRC) ARCH-0020
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.