Unit 9 · Ship it and keep it alive
Why localhost doesn’t mean it’s live
localhost is your own computer. A change you can see there is invisible to everyone else until it is deployed and showing on the real domain.
The mix-up
What people often think
“If it shows on localhost, it is live.”
What the tutor says
localhost is your own computer. Customers only see what has been deployed to the real domain.
How it works
The same goes for an AI agent’s summary. “I verified the change” is a claim, not evidence. Look at what it actually ran, then check the live site yourself, because once you forward “done” to a client, the claim is yours.
Asking the agent again tends to get the same claim. New evidence comes from new checks: git status, a request to the live URL, the page itself.
Close cousins of this mix-up
The tutor watches for these in the same lesson.
“Seeing it on my machine proves it is live.”
localhost is your computer. Nobody else can see it.
“If the agent says it verified the change, it did.”
An agent's summary is a claim, not evidence. Look at what it actually ran, then check the live site yourself.
“It is fine to pass on "done" if the agent said so.”
Once you forward it, the claim is yours. Check the real URL before anything goes to a client.
“Asking the agent again will catch the mistake.”
The agent will repeat its claim. New evidence comes from new checks: git status, curl, the live page.
Practise it with a tutor watching
"The agent says done"
Check an AI agent's claim of success against evidence from the live site, not against its own summary.
Free with an account. The first two units need no account.