Your estimate is optional. Your review compares it with how long it took; nothing is scored.
After a push, "it's deployed" means nothing until you've seen the new version answer. You'll add a version number and a build time that the live site reports, so you can tell in one request whether the server is running what you think.
This came straight out of one of our incidents: the deploy job was green and the site was down.
You'll needSomething deployed (JR-1 or later). Prices checked this month are on Tools.
One version constant
Step 1 of 3, about 5 min
Paste this to your agent
Add a VERSION constant in one file, starting at 0.1.0, and show it in the page footer.
The part of a video worth watching for this step
YouTube, John Kim. Published Sep 2026.Checked 19 Nov 2026
Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.
Stamp the build time
Step 2 of 3, about 10 min
The build time has to come from the build, not from your laptop. On a static host, write it during the build (for example a build command like date -u > build.txt && <your build>). In a Docker image, add RUN date -u +"%Y-%m-%d %H:%M UTC" > /app/build_date.txt after copying the code. Show it next to the version.
The part of a video worth watching for this step
YouTube, Tech With Tim. Published Jul 2026.Checked 19 Nov 2026
Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.
Bump to 0.1.1, push, and confirm from outside that the live site says 0.1.1 with a fresh build time. Write the command you used into AGENTS.md under "Before saying deployed".
The part of a video worth watching for this step
YouTube, Jason Lee. Published May 2026.Checked 19 Nov 2026
Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.