Hardware, platform and safety / Offline-first architecture
Why does “Paired development” matter for a small business, thinking about thin manifests with no business logic?
Built in the repository (checked files or developer tooling, not an app feature) C0225
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. Plan for: thin manifests with no business logic; acyclic dependency links; registry drift from the catalog. It exists only as a file in the repository, not as a product feature.
How to read this
The tag above says how real the answer is. Answers describe the plan in the repository and design documents. No app is released. Where an answer touches tax or law, treat it as a theme to verify with a qualified local adviser.
More in Offline-first architecture
- How does Simca approach “Elements, not roles”, with a focus on menu entries only from included elements?
- Where does “Build delivery” fit in Simca, with a focus on cache integrity on every read?
- Which edge cases come up around “Offline/Online toggle”, in particular regarding lost device key?
- See it in context with the whole topic
- Search all answers