Release staging discipline and absence reports (ADR-0006)

Staging: snapshots first

Before any release step the engine and the launcher record a snapshot of the current build and data so the step can be undone

Depends on: PKGR-0001

Staging: data never moves with code

Releasing code never copies, moves or rewrites customer data as a side effect; data changes are separate, explicit steps

Depends on: PKGR-0001

Staging: backup before any data-touching change

Any step that changes stored data is preceded by a verified backup

Depends on: PKGR-0001

Staging: test on a copy first

A data-touching change is rehearsed on a copy of the data before it is applied to the real one

Depends on: PKGR-0001

Staging: one stage per release

A release contains one stage; stages are not combined, so a failure points to exactly one change

Depends on: PKGR-0001

Staging: previous build kept for real rollback

The previous build stays installed and verified until the next one is confirmed, so rollback is a switch and not a rebuild

Depends on: PKGR-0001

Staging: sensitive modules last

Ledger and customer-data changes are the last stage of a rollout

Depends on: PKGR-0001

Engine builds the profile absence test report

The engine can emit, per profile, the list of files, commands, menus and tables that must be absent and check them

Depends on: PKGR-0001