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

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 1 exists in the repository (simca-packaging/, Rust, version 0.1.0-dev). We ran its test suite on a clean build on 2026-10-03: 65 tests passed (8 command-line, 51 library, 6 offline-guard). Planned Most 58 PKGR and 37 PKG catalog items remain planned: the catalog does not say which of them milestone 1 covers. The engine is not a product feature a customer can use, and it does not yet produce an installable bundle.

What exists (checked)

  • A Rust library and a command-line tool, simca-pack, of about two thousand lines.
  • An element-manifest schema and a registry of 3,181 element manifests seeded from the catalog; a check command fails if the registry drifts from the catalog.
  • A dependency resolver with cycle and conflict detection and a deterministic order.
  • A package-spec validator and a deterministic spec hash. We ran it on the repository example: it validates, resolves nine elements, and reports six of them as standard-class.
  • A content-addressed cache that re-verifies bytes on every read, and a build step that produces a package manifest with no timestamps or host data.
  • Ed25519 signing and verification, with test keys only. No production key is in the repository.
  • An offline guard: a test that fails the build if network crates, sockets, URLs, process spawning or URL/token environment variables appear.

What it does not do yet

  • Every artifact is a deterministic stub (all 3,181 manifests record artifact kind stub, and none records an app where it is built). A build yields a package manifest, not an installable bundle.
  • The free logistics example evaluates as standard-class because it pulls six standard-class module roots (per the packaging README). Whether to reclassify them or relax the rule is a product decision.
  • 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 and ADR-0002)

  • 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. Not decided.
  • Real prebuilt artifacts (milestone 2 and later) and the exact boundary of the free pricing class.

See the PKGR and PKG modules, the package spec and the launcher.