Offline-first architecture
User-initiated signed updates
Updates are signed packages. The launcher offers a found update in a visible, dismissible notice; applying it is always the user's action. A signed file (USB, messenger, nearby device) works with no network. There is no background service, polling or telemetry. The update logic exists as tested library code with a mock fetcher; the HTTP fetcher and the screens are not built.
Built in the repository (checked files or tested library code; not a product you can run yet)
What to plan for
- Power loss mid-update
- Rollback
- Wrong-platform package
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Offline license key (signed) LIC-0001
- Tentative flat shared fee above the profit threshold (D29) LIC-0003
- Entitlement manifest LIC-0005
- Update delivery by file/USB LIC-0010
- Update delivery by direct download (opt-in) LIC-0011
- Update signature verification LIC-0012
- Update rollback LIC-0013
- Staged update (canary on one device) LIC-0014
- Co-op tier counter LIC-0016
- Referral code redemption (signed token) LIC-0022
- Every package is sellable with an entitlement per package LIC-0037
- Entitlement file per package, signed and verified locally LIC-0038
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.