Component 2
Simca Launcher
One file to download first. It installs, starts and updates Simca, has no account of its own, and is where you tick the elements you want.
Status
Designed Designed (docs/facets/LAUNCHER.md and ADR-0001 to ADR-0004, ADR-0007). Built (repo) The launcher logic exists as a tested library (64 tests passed when we ran them): the package-spec writer, settings, signed update check with a mock fetcher, staging, rollback and offline install. Planned The 176 LNCH catalog items are planned. There is no screen, no HTTP fetcher and no installer, and no download on this site; use Request access.
Design rules
- The launcher is a regular program with no account of its own: no login, no profile, no cloud state (ADR-0003). It is free.
- When it is opened and connected it makes one disclosed update-manifest request and offers any update, even if the app is set to Offline login. No account data, no telemetry, no polling afterwards. See updates and privacy.
- A plain-sight Offline/Online toggle shows the app's login mode (ADR-0002). Offline means a local device-bound key and PIN, no internet and no registration, and the app makes no network request. Online means cloud credentials, and registration is needed only for online use.
- Updating is optional and user-initiated: a verified signed package with preflight, backup, staged apply and real rollback, or a signed file passed by USB, messenger or nearby device. Updates are never applied at start.
- It is the only place to pick, add or remove elements and to write the package spec. Removing an element asks what to do with its data: keep (the default) or toss, after a backup (details).
- Online sign-in exists only for Tap to PayCard acceptance on a phone via NFC, through a certified payment-provider SDK. Planned as an adapter; Simca does not read or store card numbers. Glossary, the shared-price counter, referral validation and the Logistics board relay. It never blocks selling.
Screens (outline, none built)
- Library: installed packages, version, mode, update status.
- Elements: browse, search and tick; dependencies, conflicts and support shown.
- Build / get package: write the spec; request online or export a file.
- Removal: every removed element with its data, keep as the default.
- Updates: check, import file, apply, roll back, dismiss, channel.
- Settings: data folder, manifest source, a switch for the opening request, language, accessibility, diagnostics export.
A forked launcher
ADR-0007 decided that Simca gets its own launcher, copied from the author's earlier private launcher with seats, presence, polling timers, a demo key and telemetry removed, and not registered in the stock launcher. A document lists what was kept and removed and a guard test keeps those things out. No working shell exists yet.
Platforms
Windows first (installer), then Android sideload, then Linux. The iOS launcher must look and work like the others (ADR-0002); Apple rule limits are checked later and recorded as per-feature exceptions.
Not decided
- Sign-in method (recommendation: challenge-response with the business key, no password).
- Whether a launcher-less portable start is allowed.
- Hosting for manifests and downloads.
- The default of the switch that turns off the opening request, and the shell technology (Electron with a Rust sidecar, or Flutter).
- Whether the code of the earlier launcher may be reused: its reuse terms are not confirmed.