Launcher, packaging and logistics
How Simca is meant to be installed and updated.
Status labels: Built in the repository (checked files or developer tooling, not an app feature) Designed in a document, no code yet Planned: listed in the catalog, not built Not decided Not in the catalog yet (a gap) No claim made
Designed C0022
The single download. It installs, starts and updates Simca packages, runs fully offline, shows a plain-sight Offline/Online toggle and is the only place to pick, add or remove elements. It is designed in documents and has no code.
Designed C0023
No. Updating is user-initiated: the user presses Check or imports a signed file. There are no background services, scheduled tasks, silent checks or telemetry.
Designed C0024
Updates are signed packages verified against keys embedded in the launcher, with preflight checks, a backup, staged apply, a health check and rollback. This is a design, not an implementation.
Designed C0025
Yes by design: a signed package can travel on a USB drive, by messenger or from a nearby device and works exactly like a downloaded one.
Designed C0026
Not offline. Offline mode uses a local device-bound key and PIN with no registration. Registration is needed only for online use, and online sign-in is never required for selling, printing or shifts.
Not decided C0027
Not decided. Replacing app files may not be allowed by the platform, so iOS update mechanics are an open point. Windows comes first.