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 rule is now enforced from both sides: an element may be marked built into an app only with a prebuilt artifact, and the app pins the exact artifact it was built against. Eight elements (seven in the Simca core and the Logistics root) pass it today.
Built in the repository (checked files or tested library code; not a product you can run yet)
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
- Free acquisition licence (D29) LIC-0002
- 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 open makes one disclosed update-manifest request LNCH-0036
- Launcher makes no hidden checks LNCH-0038
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.