Offline-first architecture
Update notice
ADR-0003 replaced the earlier rule that nothing is contacted until the user presses Check. Whenever the launcher is opened and connected it makes one disclosed update-manifest request (a plain GET of a signed static file, no account data) and shows any update in a visible, dismissible notice. There is no polling afterwards. A manual Check repeats the request. A setting to turn off even the opening request is implemented in the library as recommended and its default is for the owner to confirm.
Designed in a document, no code yet
What to plan for
- The request reveals the network address to whoever serves the file
- Dismissed until a newer version is known
- Setting to disable the request
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Free acquisition licence (D29) LIC-0002
- Entitlement manifest LIC-0005
- Revocation and key changes ship with launcher updates (honest limit) LIC-0071
- Non-binding estimate of next quarter's fee in a notice LIC-0076
- Two milestone notices before the profit threshold LIC-0083
- Notices only for users of the charged services LIC-0084
- Notices in the app always, outside the app only after registration and opt-in LIC-0085
- Threshold detection is local and sends nothing LIC-0086
- Drawer fail-to-open prompt FAIL-0048
- Antivirus/OS blocks app files FAIL-0157
- Reproducible build from manifest PKG-0018
- Signed build and license manifest PKG-0020
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.