Hardware, platform and safety / Offline-first architecture
Where does “Simca's own launcher, forked from an earlier private one” fit in Simca, especially around reuse terms of the source not confirmed?
Not decided C0251
ADR-0007: Simca gets its own launcher, copied from the author's earlier private launcher and stripped of seats, presence, polling timers, a demo key and telemetry; it is not registered in the stock launcher. A document lists what was kept and removed, and a guard test keeps those things out. The reuse terms of the source code and the shell technology (Electron with a Rust sidecar, or Flutter) are open. Plan for: reuse terms of the source not confirmed; shell technology open; no ui built. It is not decided.
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 “The launcher has no account”, thinking about offline mode governs the app only?
- Why does “What the app core can do today” matter for a small business, considering no user interface?
- Which edge cases come up around “What the Logistics core can do today”, considering reputation math is a draft?
- See it in context with the whole topic
- Search all answers