Offline-first architecture
Offline guard test
A test in the packaging crate fails the build if network crates, sockets, URLs, process spawning or URL/token environment variables appear, or if a denied crate enters the lockfile. It passed when we ran the suite. It guards the packaging tool only, not the future app.
Built in the repository (checked files or developer tooling, not an app feature)
What to plan for
- New dependencies need an allowlist entry
- Applies to the tool, not the app
- 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.