DEPLOYMENT CHECK / PRINT OR SAVE A LOCAL COPY
What does this release actually serve?
One application. One artifact. One check that a responder can follow.
Download the two-page worksheet PDF
Complete this in your own case record. Keep tokens, keys, full response bodies, and private infrastructure details out of a shared copy.
01 / Name the release
Application and owner
Artifact ID / digest and deployment date
Public routes and cache owner
02 / Inventory private files
Tools and file locations in scope
Files approved for publication
Artifact-check result and evidence reference
03 / Check the response
Approved path and test time
Status, content type, size, and cache behavior
Actual content reviewed by / restricted reference
04 / Close the loop
Serving or packaging fix / owner / due date
If a secret was exposed: revoke and investigate
Retest result / monitoring owner / next release check
Decide what the evidence supports
- Path request only: retain the event and review the request pattern.
- Unexpected file served: preserve restricted evidence and correct the deployment.
- Real secret exposed: revoke or rotate promptly and investigate use through provider records.
