Paired development rule and build delivery

Paired development rule (Packaging first, then the app)

Every element is built first in Simca Packaging (manifest, prebuilt artifact, dependency links, kept thin) and then immediately in Simca or Simca Logistics; no element is marked built in the app without its packaging side

Depends on: PKGR-0001

Element manifest schema (simca.element-manifest.v1)

Thin per-element manifest: id, name, module, version, tier, priority, pricing class, network access, dependencies, conflicts, platforms, privacy, artifact, where built

Depends on: PKGR-0001

Element registry seeded from the catalog

Registry manifests are seeded from the catalog and re-seeding keeps versions and artifacts already recorded

Depends on: PKGR-0001

Paired development check

Check that an element marked built in the app has a prebuilt artifact and valid dependency links in the registry

Depends on: PKGR-0001

Build assembled from per-element prebuilt pieces

A package is assembled from prebuilt, content-addressed element artifacts; nothing is recompiled per customer

Depends on: PKGR-0001

Build cache keyed by spec hash

Finished packages are cached under the hash of the normalised package spec

Depends on: PKGR-0001

Identical specs give identical builds (determinism test)

Test that two builds of the same spec produce byte-identical package manifests, independent of element order in the spec

Depends on: PKGR-0001

Cache object integrity verification

Every cached piece is re-hashed on read and the cache can be verified in full

Depends on: PKGR-0001

Package manifest signature (Ed25519)

Package manifests are signed with Ed25519; test keys only in development

Depends on: PKGR-0001

Offline-guard test for the packaging tool

Test that the packaging tool has no network crates, sockets or URLs in its source

Depends on: PKGR-0001