A publication is only real when something outside the system can be fetched and checked. A queue receipt is not a publication.
This piece exists to prove that claim by traveling the whole line: capture, brief, draft, review gate, staged, released. No shortcuts. Every one of those stages either happened or the gate stops. That is the entire job of this fixture, release gate 20260724-224359.
The destination for this piece is a place nobody reads. That is deliberate. The audience is not the point. The point is the chain: a real repository commit, a real deploy, a real live URL. When that URL is fetched, it must return 200. It must carry this piece’s own prose, not a placeholder, not a cached stand-in. If the words on the page match the words drafted here, the chain held. If they do not, the chain broke, and no internal status field gets to argue otherwise.
Internal status fields lie by omission. A dashboard can say “released” while the actual bytes sitting behind the URL are stale, wrong, or missing entirely. Confidence built on those fields is optimism wearing a badge. Confidence built on an external fetch is verification. Those are not the same thing, and treating them as interchangeable is how releases quietly fail while every internal signal stays green.
So the standard here is simple: fetch the URL, check the status code, check the content. Not “the pipeline said done.” Not “the queue accepted the job.” The artifact, in the world, matching the draft.
Proof beats optimism because proof does not care what anyone hoped would happen.