Release discipline
ZENQIX treats rollback as part of release engineering rather than an emergency improvisation. A production change should be tied to a known source revision, immutable release artifact and health verification result.
Product and website services should be deployable independently so a public website release does not require changing Endpoint, Remote Support or the product database.
Before a change
- Identify the current release and exact rollback artifact.
- Confirm current product health before changing anything.
- Create or verify the required database backup when the product database is in scope.
- Preserve configuration and secrets outside source-control artifacts.
- Define a fail-closed health gate and rollback trigger.
After a change
- Verify application health and key routes.
- Verify dependent product services remain healthy after the change.
- Record the deployed source/image identity.
- Retain the previous known-good artifact until the new release has completed acceptance.