Hardware, platform and safety / Offline-first architecture
Where does “Packaging engine” fit in Simca, thinking about spec validation?
Built in the repository (checked files or tested library code; not a product you can run yet) C0230
Per ADR-0001 and ADR-0002, Simca Packaging is a server-side or developer-side engine that assembles and signs a package from a package spec. It is not a website builder. Milestone 2 exists in the repository as Rust code with a command-line tool: a registry of every catalog element, a dependency resolver, a package-spec validator, a deterministic package container with a content-addressed cache, signed documents, delta manifests and a paired-development check. Only eight elements have real prebuilt artifacts; the other elements still have stubs, so the engine does not yet produce a full installable product. Plan for: spec validation; reproducible output; dependency resolution. 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
- What should owners check about “Core and logistics isolation”, considering contract transport not chosen?
- Why does “Performance goals” matter for a small business, in particular regarding old hardware?
- How does Simca approach “Data model”, especially around schema changes?
- See it in context with the whole topic
- Search all answers