Catalog section · LNCH
16 planned items in Simca Launcher (Steam-like): Offline Mode, User-Initiated Updates, Package Spec, Sign-in.
Decision: redesign the existing MiniStudios/an earlier launcher to Simca specs instead of starting from nothing; see ADR-0001 and docs/facets/LAUNCHER.md
Depends on: LNCH-0001
Stage the new files, release the single-instance lock, spawn the staged app, then quit; never overwrite the running image
Depends on: LNCH-0001
Registry of installable packages with id, version, minimum launcher version and status, plus a removal recipe for temporary options
Depends on: LNCH-0001
Verify hash and size of staged files before apply
Depends on: LNCH-0001
Keep the last working generation until the next success
Depends on: LNCH-0001
Network errors never crash the launcher or the app; they become clear messages
Depends on: LNCH-0001
Errors like SIMCA_LNCH_BAD_SIGNATURE and files like simca.package-spec.v1
Depends on: LNCH-0001
The fork removes seats, presence and last-seen entirely
Depends on: LNCH-0001
The fork must work fully with no server; no dependence on a hosted worker or KV for offline use
Depends on: LNCH-0001
No timers that poll for updates (the original polled every 30 seconds); updates are user-initiated only
Depends on: LNCH-0001
No demo keys or credentials in the repository or the build
Depends on: LNCH-0001
No telemetry, no SIEM webhook queue, no outbound reporting
Depends on: LNCH-0001
No remote scripts or fonts at runtime
Depends on: LNCH-0001
No listening sockets except an optional loopback control surface that is off by default
Depends on: LNCH-0001
No source-host token fallback for downloading updates
Depends on: LNCH-0001
Any control that applies an update says so plainly and asks first
Depends on: LNCH-0001