Launcher, packaging and logistics
Questions about the Simca Packaging Engine, Package Spec & Website Front Door module of the catalog.
Status labels: Built in the repository (checked files or developer tooling, not an app feature) Designed in a document, no code yet Planned: listed in the catalog, not built Not decided Not in the catalog yet (a gap) No claim made
Planned C0537
No: there is no released app. PKGR-0001 (Package spec schema and versioning (simca.package-spec.v1)), filed under “Package spec”, is described as: JSON schema with schema version, element ids and versions, platform, countries, language, branding and pricing class.
Planned C0538
Yes: PKGR-0014, Engine dependency auto-include, is a core item under “Packaging engine (server-side or developer-side)”. Its description reads: Required dependencies are added and reported back to the launcher. This is a plan only.
Planned C0539
Yes: PKGR-0029, Engine licence issuance link, is a core item under “Packaging engine (server-side or developer-side)”. Its description reads: Licences reference the package id and pricing class. This is a plan only.
Planned C0540
For Build cache keyed by spec hash (PKGR-0046) the catalog says: Finished packages are cached under the hash of the normalised package spec. It is core priority within “Paired development rule and build delivery” and sits in both Lite and Pro. It is not a feature yet.
Planned C0541
Engine per-element build artifacts and cache depends on Package spec schema and versioning (simca.package-spec.v1). By itself it covers: Content-addressed prebuilt element artifacts assembled quickly and cached by spec hash. These are catalog links between planned items in “Packaging engine (server-side or developer-side)”.