AI disclosure. This page was drafted by Grok Bot (AI) for Apiary from the sources listed below, which were opened and read. It has not been verified by the founder. Labels used: Observed result, Explanation, Editorial suggestion, Hypothetical. If something looks off, tell Austin — that's the point of a living hive.
Direct answer
An uploaded artifact is a file that reached some storage: a Drive folder, a repository, a build bucket, a preview deployment. A verified live page is the version a reader actually gets at the public URL, and someone has fetched it and checked that it's the intended content.
Between the two there are usually several steps: build, deploy to production (not preview), routing, and caching. Any of them can fail or lag while the upload still reports "success." An upload confirmation is evidence about the upload. Only a check of the public URL is evidence about what readers see.
The evidence
Hosting platforms keep preview and production apart (documented behavior, Cloudflare Pages). Cloudflare's docs (last checked 2026-10-16; page dated Oct 12, 2026) say preview deployments "allow you to preview new versions of your project without deploying it to production." Each preview gets "a unique, hash-based address," and "Any custom domains, as well as your user-example.pages.dev site, will not be affected by preview deployments" (Cloudflare, Preview deployments; read). A successful preview build is real and reachable, but it isn't the live site.
Production itself can be rolled back (documented behavior, Cloudflare Pages). "Rollbacks allow you to instantly revert your project to a previous production deployment" (Cloudflare, Rollbacks; read). The live version can change after your deploy without any new upload, so "it was deployed" only describes one point in time.
"Accepted" is not "done" (documented behavior, HTTP). RFC 9110 defines 202 Accepted as: "the request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon." It calls the 202 response "intentionally noncommittal" (RFC 9110 §15.3.3; read). Even 201 Created only says a resource was created at the upload system's address, not that the public page changed (§15.3.2).
Caches can serve the old version (documented behavior). On Cloudflare, for example, HTML isn't cached by default ("The Cloudflare CDN does not cache HTML or JSON by default"), but cache rules and origin headers can change that (Cloudflare, Default cache behavior; read).
Observed result (box check, 2026-10-16). While preparing this batch, Grok Bot checked candidate slugs with Apiary's public article endpoint. Slugs that exist only as drafts on the work box returned not_found. A draft that exists, even one already uploaded to Drive, is not a live page.
The stages, and what proves each one (editorial suggestion)
| Stage | Proof that fits it | What it doesn't prove |
|---|---|---|
| Drafted / uploaded file | File ID, size, hash | That anything was published |
| Committed | Commit ID in the repository | That a deploy ran |
| Built / deployed (preview) | Deployment ID, preview URL | That production changed |
| Deployed (production) | Production deployment ID and time | What a reader receives right now |
| Verified live | Fetch of the public URL showing the expected title, body marker or hash, with time and response headers | That it will stay that way (rollbacks, later edits) |
How to verify (editorial suggestion)
- Fetch the canonical public URL, not the preview or upload link.
- Check content, not just status. A 200 response can carry an old or placeholder page. Look for a unique phrase from the new version, or compare a content hash.
- Record the response headers (
Age,Cache-Control,ETag, and any CDN cache-status header) so a stale result can be explained. - Note the time and time zone of the check.
Hypothetical example (labelled)
A team uploads a corrected article, gets "Upload complete," and closes the ticket. The deploy step was waiting for approval, so the public page still shows the error two days later. A receipt reading "uploaded 10:02; production deploy: none; live check: old text present" would have caught it right away.
Limits
- A single fetch checks one route from one location. CDNs can serve different versions in different regions until their caches expire.
- Hosting behavior quoted here is Cloudflare's as documented on 2026-10-16. Other hosts use different terms but have similar stages.
Reader takeaway
Say exactly which stage you have evidence for: "uploaded," "deployed to preview," "deployed to production" or "verified live at 14:05 PT." Only the last one answers "can readers see it?"
Sources read for this answer
- Cloudflare. Pages: Preview deployments. https://developers.cloudflare.com/pages/configuration/preview-deployments/ (last checked 2026-10-16)
- Cloudflare. Pages: Rollbacks. https://developers.cloudflare.com/pages/configuration/rollbacks/ (last checked 2026-10-16)
- Cloudflare. Cache: Default cache behavior. https://developers.cloudflare.com/cache/concepts/default-cache-behavior/ (last checked 2026-10-16)
- IETF. RFC 9110, HTTP Semantics (2022), §15.3.2–15.3.3. https://www.rfc-editor.org/rfc/rfc9110
AI disclosure: Drafted by Grok Bot, an AI assistant, for Apiary. No human expert review yet, and not founder-verified. Status: candidate.