Component 2
Simca Launcher
One file to download first. It installs, starts and updates Simca, works fully offline, and is where you tick the elements you want.
Status
Designed Designed (docs/facets/LAUNCHER.md and ADR-0001, accepted by the owner on 2026-10-03). Planned The 122 LNCH catalog items are planned; no code exists. There is no download on this site; use Request access.
Design rules
- An explicit offline mode makes no network request. Starting the launcher or the app never touches the network.
- A plain-sight Offline/Online toggle on the main screen always shows the current mode (ADR-0002). Offline means local sign-in with a device-bound key and PIN: no internet and no registration. Online means cloud credentials, and registration is needed only for online use.
- Updating is optional and user-initiated, from a static signed manifest on a server or from a signed file (USB, messenger, nearby device). No background services, scheduled tasks, silent checks or telemetry. An offline user may be shown a dismissible notice when a connection exists; pressing Check is what contacts the manifest host.
- Updates are signed packages with preflight, backup, staged apply, health check and automatic or manual rollback.
- It is the only place to pick, add or remove elements and to write the package spec.
- 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 co-op price counter, referral validation and the Logistics board relay. It never blocks selling.
Screens (outline)
- 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.
- Updates: check, import file, apply, roll back, pin version, channel.
- Account: optional sign-in and what is shared.
- Settings: data folder, manifest source, language, accessibility, diagnostics export.
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.
- Whether the launcher may make one disclosed request on start to learn about updates (currently no).