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 tested library code; not a product you can run yet) C0239
A small JSON file written by the launcher that lists the chosen elements. A v1 schema and an example exist in the repo; the packaging engine validates and hashes it, and the launcher library has a spec writer whose output is checked against the engine's schema. There is no launcher screen yet. 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