Catalog section · ARCH

Independence principles

15 planned items in Compartmentalization: Core/Logistics Isolation, Contracts & Independent Delivery.

Compartment principle (core and Logistics fail separately)

ARCH-0001 Planned Lite and Pro Core

A fault, update or rollback in Simca Logistics must never crash or corrupt Simca core, and vice versa

Independent codebase and repository folder

ARCH-0002 Planned Lite and Pro Core

Simca Logistics lives in its own top-level folder with its own source, tests and docs

Depends on: ARCH-0001

No shared mutable code rule

ARCH-0003 Planned Lite and Pro Core

Shared code is limited to immutable, versioned libraries (e.g. crypto, money type) vendored per side; no shared mutable modules

Depends on: ARCH-0001

No shared database tables rule

ARCH-0004 Planned Lite and Pro Core

Each side owns its tables; no cross-side joins, triggers or foreign keys

Depends on: ARCH-0001

Separate SQLite file for Logistics

ARCH-0005 Planned Lite and Pro Core

Logistics data in its own SQLite database file (WAL, synchronous=FULL), never inside the core DB file

Depends on: ARCH-0001

Separate schema and own migrations

ARCH-0006 Planned Lite and Pro Core

Logistics owns its schema version and forward-only migrations with tested rollback copies

Depends on: ARCH-0001

Migration safety (backup before migrate)

ARCH-0007 Planned Lite and Pro Core

Automatic snapshot before any migration, restore path on failure

Depends on: ARCH-0001

Independent semver for Logistics

ARCH-0008 Planned Lite and Pro Core

Logistics has its own MAJOR.MINOR.PATCH version independent from core

Depends on: ARCH-0001

Independent semver for core

ARCH-0009 Planned Lite and Pro Core

Core keeps its own versioning; Logistics never reads core internals

Depends on: ARCH-0001

Independent build pipeline

ARCH-0010 Planned Lite and Pro Core

Separate build, lint and package steps per compartment

Depends on: ARCH-0001

Independent test suite

ARCH-0011 Planned Lite and Pro Core

Separate unit, integration and property tests per compartment

Depends on: ARCH-0001

Independent release process

ARCH-0012 Planned Lite and Pro Core

Separate release notes, signing and artifacts per compartment

Depends on: ARCH-0001

Dependency direction rule (Logistics depends on contracts, core does not depend on Logistics)

ARCH-0013 Planned Lite and Pro Core

Core must run fully with Logistics absent

Depends on: ARCH-0001

Compartment boundary lint

ARCH-0014 Planned Lite and Pro Standard

Static check that forbids imports across the boundary except the contract package

Depends on: ARCH-0001

Compartment ownership map

ARCH-0015 Planned Lite and Pro Standard

Document who owns which tables, files, logs and keys

Depends on: ARCH-0001