Hardware, platform and safety / Offline-first architecture
What should owners check about “Package spec”, with a focus on dependencies added automatically?
Built in the repository (checked files or developer tooling, not an app feature) C0222
A small JSON file written by the launcher that lists the chosen elements. A v1 draft schema and an example exist in the repo, and the milestone-1 packaging tool validates and hashes the example; the launcher that would write it does not exist. Plan for: dependencies added automatically; pinned versions; no identity data in the spec. It exists only as a file in the repository, not as a product feature.
How to read this
The tag above says how real the answer is. Answers describe the plan in the repository and design documents. No app is released. Where an answer touches tax or law, treat it as a theme to verify with a qualified local adviser.
More in Offline-first architecture
- How does Simca approach “User-initiated signed updates”, considering power loss mid-update?
- What should I plan for with “Online sign-in”, with a focus on sign-in method not decided?
- How does Simca approach “Elements, not roles”, with a focus on menu entries only from included elements?
- See it in context with the whole topic
- Search all answers