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

Launcher, packaging and logistics

ARCH: Compartmentalization: Core/Logistics Isolation, Contracts & Independent De

Questions about the Compartmentalization: Core/Logistics Isolation, Contracts & Independent Delivery module of the catalog.

Status labels: Built in the repository (checked files or developer tooling, not an app feature) Designed in a document, no code yet Planned: listed in the catalog, not built Not decided Not in the catalog yet (a gap) No claim made

Can I use “Compartment principle (core and Logistics fail separately)” today?

Planned C0518

No: there is no released app. ARCH-0001 (Compartment principle (core and Logistics fail separately)), filed under “Independence principles”, is described as: A fault, update or rollback in Simca Logistics must never crash or corrupt Simca core, and vice versa.

Open this answer on its own page

Why would a shop need “Independent test suite”?

Planned C0519

For Independent test suite (ARCH-0011) the catalog says: Separate unit, integration and property tests per compartment. It is core priority within “Independence principles” and sits in both Lite and Pro. It is not a feature yet.

Open this answer on its own page

Why would a shop need “Contract: licensing flags (LIC)”?

Planned C0520

For Contract: licensing flags (LIC) (ARCH-0024) the catalog says: Package id and pricing-class flags in the licence token. It is core priority within “Interface contracts and versioning” and sits in both Lite and Pro. It is not a feature yet.

Open this answer on its own page

Does “Own working directory and data folder” work without internet?

Planned C0521

The catalog marks it as always offline. For Own working directory and data folder (ARCH-0044) the catalog text is: Separate folders for DB, logs, cache and backups. Under “Runtime isolation and fault containment”, and not built.

Open this answer on its own page

What does “Integrity check on start (per compartment)” depend on?

Planned C0522

Integrity check on start (per compartment) depends on Compartment principle (core and Logistics fail separately). By itself it covers: SQLite integrity_check and schema version check each start. These are catalog links between planned items in “Runtime isolation and fault containment”.

Open this answer on its own page

What does “Rollback to previous Logistics version” depend on?

Planned C0523

Rollback to previous Logistics version depends on Compartment principle (core and Logistics fail separately), Independent update channel for Logistics. By itself it covers: One-step rollback keeping data compatible. These are catalog links between planned items in “Independent updates, rollback, logs and backups”.

Open this answer on its own page

How important is “Packaging element: compartment manifest” in the catalog?

Planned C0524

Packaging element: compartment manifest carries core priority in Compartmentalization, section “Development process and governance”. Description: Each compartment declares its version, contracts supported and elements it provides. Priority is only a planning label.

Open this answer on its own page

How important is “Schema registry file in repo” in the catalog?

Planned C0525

Schema registry file in repo carries standard priority in Compartmentalization, section “Interface contracts and versioning”. Description: Single folder holding all contract schemas. Priority is only a planning label.

Open this answer on its own page

Can I use “Log redaction” today?

Planned C0526

No: there is no released app. ARCH-0081 (Log redaction), filed under “Independent updates, rollback, logs and backups”, is described as: Remove personal data from logs by default.

Open this answer on its own page