Hardware, platform and safety / Offline-first architecture
How does Simca approach “User-initiated signed updates”, considering power loss mid-update?
Built in the repository (checked files or tested library code; not a product you can run yet) C0238
Updates are signed packages. The launcher offers a found update in a visible, dismissible notice; applying it is always the user's action. A signed file (USB, messenger, nearby device) works with no network. There is no background service, polling or telemetry. The update logic exists as tested library code with a mock fetcher; the HTTP fetcher and the screens are not built. Plan for: power loss mid-update; rollback; wrong-platform package. 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
- Which edge cases come up around “Offline mode”, in particular regarding clock skew?
- What should owners check about “Package spec”, with a focus on dependencies added automatically?
- What should I plan for with “Online sign-in”, with a focus on sign-in method not decided?
- See it in context with the whole topic
- Search all answers