Offline-first architecture
Package spec
A small JSON file written by the launcher that lists the chosen elements. A v1 schema and an example exist in the repo; the packaging engine validates and hashes it, and the launcher library has a spec writer whose output is checked against the engine's schema. There is no launcher screen yet.
Built in the repository (checked files or tested library code; not a product you can run yet)
What to plan for
- Dependencies added automatically
- Pinned versions
- No identity data in the spec
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Regional pricing (PPP) LIC-0025
- Spare signing keys and rotation LIC-0068
- Package spec file (build recipe) PKG-0017
- Add-element-later flow PKG-0022
- Narrow versioned contract between core and Logistics ARCH-0016
- Contract spec documents (both sides) ARCH-0017
- Launcher fork/redesign decision record (from the an earlier launcher) LNCH-0017
- Launcher reuse: typed error codes and schema-versioned JSON LNCH-0023
- Launcher element picker LNCH-0075
- Launcher dependency and conflict display LNCH-0076
- Launcher presets (pre-ticked selections) LNCH-0077
- Launcher price preview LNCH-0078
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.