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.
Small does not mean unfinished; it means each boundary has a clear job and a visible owner.
One root, one file_server, and a small header policy make a static deployment easy to inspect.
Verify the artifact before replacing the live directory, and keep the checks close to the release command.
Staging avoids file-by-file overwrites, but this two-step switch briefly removes the live path and still requires compatible assets for older pages.
One aggregate digest is useful, but a sorted per-file manifest tells you exactly what changed or went missing.
Two small read-only helpers turn the public endpoint into evidence you can inspect before and after a release.
Validate one staged artifact, publish it, then compare representative public responses with those exact bytes.
Prepare the TTL ahead of time, observe authoritative and recursive answers, and keep both endpoints valid through the cache window.