Design stage: there is no released app yet. This site separates what exists in the repository from what is planned. See status

Component 1

Simca Packaging

The first thing being built: an engine that turns a package spec (a list of chosen elements) into a signed package. It runs on the server or developer side. It is not a customisation page on this website.

Status

Built (repo) Milestone 2 exists in the repository (simca-packaging/, Rust, version 0.2.0-dev). We ran its test suite on 2026-10-04: 220 tests passed. Planned Most of the 107 PKGR and 37 PKG catalog items remain planned. Only eight elements have real prebuilt artifacts; the other 3,427 are stubs, so the engine cannot yet produce an installable Simca. It is not a product feature a customer can use.

What exists (tested code)

  • A registry of every catalog element with a manifest, kept in step with the catalog by a check.
  • A dependency resolver with cycle and conflict detection and a deterministic order, and a package-spec validator with a deterministic spec hash.
  • A deterministic package container (the same spec gives the same bytes) built from real prebuilt artifacts for eight demo elements, with a content-addressed cache and counters that show the cache saves work.
  • Menu entries and permissions come only from the elements included in a package.
  • Signed documents (packages, update manifests, entitlements, the catalog snapshot, price tables) with expiry, rollback protection, a trusted key set and a revocation list. Ed25519, with test keys only; no production key is in the repository.
  • Delta plans that say what to reuse and what to fetch, with full re-verification, including from a local mirror or file.
  • The paired-development check: an element may claim to be built into an app only with a prebuilt artifact and a matching pin on the app side.
  • Removal planning: a dry run that lists what removing an element would touch, with keep as the default (ADR-0005), and a proof that a package holds nothing for elements outside its spec (ADR-0006).
  • A fee calculator and a public view for the quarterly cost page, using MOCK data only (ADR-0008).

What it does not do yet

  • Every element except eight still has a stub artifact. A package of most elements is not installable.
  • Logistics is not a free package (ADR-0003): it pays the same flat quarterly fee as everything else.
  • No production signing keys and no key ceremony. No hosting for manifests or downloads.
  • It has no web interface on this site: no cart, no builder, no tracking, and it does not see your business data (the spec carries no identity).

Rules it follows (ADR-0001 to ADR-0003, ADR-0006)

  • Paired development: every element is built in Simca Packaging first (thin manifest, prebuilt artifact, dependency links) and then immediately in Simca or Simca Logistics.
  • Build delivery: packages are assembled from per-element prebuilt pieces and cached by spec hash. Nothing is recompiled per customer, and identical specs give identical builds.
  • Unselected elements are left out: no code, no tables, no menu entry.

Open points

  • Hosting for manifests and downloads, and the key ceremony. Not decided.
  • Real prebuilt artifacts for the other elements.

See the PKGR and PKG modules, the package spec, the launcher and the packaging security model.