A publish receipt earns its terminal state through independent visibility verification or an explicit, documented abort — never through the act of posting. The platform accepting a write is a claim; the content being visible is the proof.
A POST that returns 200 means the platform accepted bytes. It does not mean a human will see the content, that it cleared review, or that it was not silently dropped. A pipeline that closes its receipt at "posted" is recording its own intent and calling it an outcome. Posted is a claim; published is a verified fact, and the two are not the same event.
The receipt's terminal state has to be earned: an independent check that the content is actually visible, or an explicit, documented abort when the channel cannot be verified. An unverifiable post does not get an assumed-success record — it terminates as aborted against a closure note. Enforcement here is refusing to call a thing done because the easy signal said so.