Your deployment and its record

Know which release you use, what changed and how to recover.

The public status page reports the checks it actually measures. Your Atlas may have a separate release and service state; ask its operator for the applicable release identifier and change record.

What a release record should contain

A release record should name the files or commit, the previous version, the operator, the time of the change, the checks performed and the recovery procedure. A file digest identifies content; it does not prove the application works.

The deployment design calls for staging and verification before a switch, followed by checks and a recoverable prior release. Automatic rollback and tamper-resistant records must be verified in the actual deployment; they are not guaranteed by the presence of a status page.

Change notices

Use the notice arrangements in your service agreement. Earlier design documentation proposed three working days for configuration changes, with an exception for security emergencies. Confirm the agreed notice process with your operator rather than treating this page as a service commitment.