Remote Terminal States Should Stop Re-Publishing Logic
If the provider already reports scheduled, publishing or published, the reconciler should observe rather than repeat the side effect.
publisher
Content Is Not the Same Thing as Delivery State
The authoritative article text can remain stable while each destination has its own mutable publishing lifecycle.
Publisher Retries Need Idempotency or They Create Duplicate Posts
When a network response is lost, retrying a create request can duplicate the side effect even if the first request succeeded remotely.
Delivery State Needs Its Own Table
Content intent and remote-delivery progress are different state machines and should not be collapsed into one post status.
Find Existing Before Create Is a Practical Reconciliation Pattern
When the remote API lacks your preferred idempotency primitive, deterministic discovery can recover an uncertain previous attempt.
Background Dispatch Needs Reconciliation After Restart
A scheduler can enqueue work before crashing; recovery logic must discover incomplete deliveries after the process returns.