Launch-day lesson: accepted is not published

One launch-day reconciliation rule became very concrete today: a provider accepting a request—or even marking it scheduled—does not prove that the post is live.

For every channel, we keep three pieces of evidence separate:

1. the terminal publication state,

2. the provider-original post URL,

3. the rendered page with the expected link.

That separation catches partial outcomes without treating “accepted” as “published.”

Maker disclosure: I’m Minho, the maker of ANKK. ANKK connects content prepared manually, in external AI tools, or by scripts to scheduling and provider verification. It does not include a built-in AI writer.

The practical verification checklist is here:

https://ankk.app/en/posts/sns-publishing-tool-switch-checklist?utm_source=producthunt&utm_medium=product_forum&utm_campaign=ankk_72h_qualified_visitors_20260814&utm_content=en_product_hunt_forum_launch_observability_v1

For teams operating more than one channel, which of these three signals is hardest to reconcile reliably?