Offline-first architecture
Build delivery
ADR-0002: packages are assembled from per-element prebuilt pieces and cached by spec hash; nothing is recompiled per customer and identical specs give identical builds. A deterministic container, a content-addressed cache, build counters that show the cache saves work, and delta plans exist as code. Only eight elements have real prebuilt pieces; 3,423 still have stubs, so a package of most elements is not installable.
Built in the repository (checked files or tested library code; not a product you can run yet)
What to plan for
- Cache integrity on every read
- No timestamps in manifests
- Stub pieces make a package not installable
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Full resync from hub MULTI-0036
- Offline licence semantics: updates_until (reserved, enforcement open) LIC-0044
- Fee lapse consequence (open) LIC-0051
- Revocation and key changes ship with launcher updates (honest limit) LIC-0071
- Journal replay recovery FAIL-0013
- Website front door (product info, launcher download, read-only catalog preview) PKG-0015
- Package spec file (build recipe) PKG-0017
- Reproducible build from manifest PKG-0018
- Build artifacts per platform PKG-0019
- Signed build and license manifest PKG-0020
- Image cache & compression PLAT-0022
- Independent build pipeline ARCH-0010
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.