Hardware, platform and safety / Offline-first architecture
Where does “Build delivery” fit in Simca, with a focus on cache integrity on every read?
Built in the repository (checked files or developer tooling, not an app feature) C0226
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. The spec hash, cache and manifest build exist in milestone 1; the pieces are stubs. Plan for: cache integrity on every read; no timestamps in manifests; real artifacts not yet built. 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
- Why does “Paired development” matter for a small business, thinking about thin manifests with no business logic?
- Which edge cases come up around “Offline/Online toggle”, in particular regarding lost device key?
- What should I plan for with “Update notice for offline users”, with a focus on passive connectivity state only?
- See it in context with the whole topic
- Search all answers