Independent update channel for Logistics
ARCH-0068 Planned Lite and Pro CoreLogistics updates ship separately from core updates
Depends on: ARCH-0001
Catalog section · ARCH
20 planned items in Compartmentalization: Core/Logistics Isolation, Contracts & Independent Delivery.
Logistics updates ship separately from core updates
Depends on: ARCH-0001
Core updates never force Logistics updates unless contract major changes
Depends on: ARCH-0001
Updates as signed files installable offline per compartment
Depends on: ARCH-0001
Verify signatures before install
Depends on: ARCH-0001
Early adopters opt in to test builds; no data is collected
Depends on: ARCH-0001
One-step rollback keeping data compatible
Keep pre-migration snapshot and record schema version to allow safe rollback
Depends on: ARCH-0001
Retain previous version binary and data snapshot
Depends on: ARCH-0001
Check disk space, contract compatibility and backup before updating
Depends on: ARCH-0001
Verify compartment started and passed integrity checks; auto-rollback if not
Depends on: ARCH-0001
Plain-language changelog
Depends on: ARCH-0001
User can postpone updates, e.g. during working hours
Depends on: ARCH-0001
Separate log files and rotation
Depends on: ARCH-0001
Remove personal data from logs by default
Depends on: ARCH-0001
User chooses to export logs and send them
Depends on: ARCH-0001
Separate backup schedule and files
Depends on: ARCH-0001
Manifest records compartment versions and schema versions in each backup
Depends on: ARCH-0001
Restore Logistics alone without touching core data
Depends on: ARCH-0001
Block restore into an incompatible version with a clear explanation
Depends on: ARCH-0001
Written procedure and test for restoring both compartments
Depends on: ARCH-0001