Offline-first architecture
Paired development
ADR-0002: every element is built first in Simca Packaging (thin manifest, prebuilt artifact, dependency links) and then immediately in Simca or Simca Logistics. The packaging tool refuses an element that claims an app build without a prebuilt artifact.
Built in the repository (checked files or developer tooling, not an app feature)
What to plan for
- Thin manifests with no business logic
- Acyclic dependency links
- Registry drift from the catalog
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Device registry & revocation MULTI-0008
- Entitlement manifest LIC-0005
- Antivirus/OS blocks app files FAIL-0157
- Reproducible build from manifest PKG-0018
- Signed build and license manifest PKG-0020
- Schema registry file in repo ARCH-0041
- Backup bundle manifest with versions ARCH-0084
- Packaging element: compartment manifest ARCH-0096
- Launcher reuse: package registry (id, version, minimum launcher version, status) LNCH-0019
- Launcher connectivity test (user-initiated) LNCH-0041
- Launcher update check (user-initiated) LNCH-0043
- Launcher update manifest (static signed file) LNCH-0044
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.