Identify your distribution
Record the installed version and signed release identity. Use the matching reviewed release instructions, backup and migration plan; do not extract another full installer over a running database.
The current signed-source distribution verifies its complete immutable inventory. Legacy partial-core updates and development updater paths are rejected by that distribution. A historic updater command is not a supported way to bypass the full-release guard. Obtain the reviewed whole-release procedure before changing signed files.
Review update rights and data changes
The signed entitlement determines updates. Subscription and lifetime purchased-version rights differ; an optional purchase for a selected later version does not create a second product-use licence.
Before an approved update, create and verify a complete backup, stop persistent workers as required, and review any database migrations. File rollback does not restore financial/database contents. Keep the original encryption and licence identities.
If an operation is interrupted, retain maintenance markers, original-file snapshots and private journals. Follow the exact release's recovery procedure; do not delete locks, edit signed hashes or switch to development mode to force boot.
Move to another domain
Prepare HTTPS and the target host, keep the old installation restricted and use Orbit's reviewed licence-transfer process. A backup or domain change does not authorise simultaneous production copies. Verify the new installation and external routing before retiring the original.