Use this path when the question is not only “does it work?” but also “what evidence lets us replace it or recover it?” The notes keep artifact boundaries, rollback windows, and routine maintenance visible.
Scheduling is only half the job; operators also need to see when the task last ran and how it ended.
One aggregate digest is useful, but a sorted per-file manifest tells you exactly what changed or went missing.
Visitors should see the old release or the new release, not a file-by-file mixture of both.
Verify the artifact before replacing the live directory, and keep the checks close to the release command.
Build once, inspect the output, then exercise representative public routes before replacing the live directory.
One root, one file_server, and a small header policy make a static deployment easy to inspect.
Choose a small recovery unit, verify it, and practice restoring it somewhere disposable.
Prepare the TTL ahead of time, observe authoritative and recursive answers, and keep both endpoints valid through the cache window.