Offline-first architecture
Offline guard tests
Tests in the Rust workspaces fail the build if network crates, sockets, URLs, process spawning, demo keys, default network binding or remote asset loads appear. The workspaces' test suites passed when we ran them on 2026-10-04 (460 tests in total across packaging, core, Logistics and launcher). They guard the code in the repository, not a shipped app.
Built in the repository (checked files or tested library code; not a product you can run yet)
What to plan for
- New dependencies need an allowlist entry
- Applies to the code, not a future UI
- Passing today says nothing about later commits
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.