Development process and governance

Compartment-scoped issue tracking

Issues labelled core, logistics or contract

Depends on: ARCH-0001

Contract change proposal process

Written proposal and review by both sides before changing a contract

Depends on: ARCH-0001

Architecture decision records (ADR)

Store decisions such as sandbox model and sync approach

Depends on: ARCH-0001

Fault-injection tests

Tests that kill, hang and corrupt one compartment and assert the other survives

Depends on: ARCH-0001

Chaos test: contract version mismatch

Test all combinations in the compatibility matrix

Depends on: ARCH-0001

Chaos test: power loss during migration

Verify recovery from interrupted migration

Depends on: ARCH-0001

Static analysis and dependency audit per compartment

Separate dependency lists, audits and licences

Depends on: ARCH-0001

Reproducible builds per compartment

Same inputs produce identical artifacts

Depends on: ARCH-0001

Packaging element: compartment manifest

Each compartment declares its version, contracts supported and elements it provides

Depends on: ARCH-0001

Packaging rule: Logistics requires contract, not core internals

Simca Packaging checks contract compatibility instead of core internals

Depends on: ARCH-0001

Documentation: compartment boundaries diagram

Diagram of processes, files, contracts and update channels

Depends on: ARCH-0001