State the current reality
Separate proposed, implemented, tested, and deployed behavior. A passing source check does not prove a live user journey.
Identify the exact artifacts
Record authoritative paths, repository references, versions, and relevant hashes. Preserve existing work and indicate which files changed.
Keep useful test receipts
Name the checks, their outcomes, and the conditions under which they ran. Include open findings and verification limits.
Make recovery concrete
Give a precise rollback procedure and its prerequisites. A backup is useful only when the right person can find and restore it.
A concrete starting point.
After a site release, retain the source commit, the deployed file manifest, the behavior checks, and the exact prior release that can be restored.
Your working checklist.
Mark what you have considered. This checklist stays on this page and is cleared when you reload.
Explore the related work.
General engineering guidance, not a certification, service agreement, or product-specific acceptance report.
Back to all field notes ↗