Offline-first architecture
Simca's own launcher, forked from an earlier private one
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.
Not decided
What to plan for
- Reuse terms of the source not confirmed
- Shell technology open
- No UI built
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Launcher fork/redesign decision record (from the an earlier launcher) LNCH-0017
- Launcher reuse: stage, spawn, quit apply order LNCH-0018
- Launcher reuse: package registry (id, version, minimum launcher version, status) LNCH-0019
- Launcher reuse: sha256 and size verification LNCH-0020
- Launcher reuse: keep previous generation LNCH-0021
- Launcher reuse: fail-soft network error handling LNCH-0022
- Launcher reuse: typed error codes and schema-versioned JSON LNCH-0023
- Launcher exclusion: presence and seat tracking LNCH-0024
- Launcher exclusion: cloud worker and key-value store dependence LNCH-0025
- Launcher exclusion: periodic update polling LNCH-0026
- Launcher exclusion: demo or committed launcher keys LNCH-0027
- Launcher exclusion: telemetry and webhook exports LNCH-0028
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.