reference
Durable social scheduling
Owner-only LinkedIn, X and Instagram scheduling with member approvals, canonical intents and SQL recovery.
Eleven operations cover create (prepare), publish-now, cancel (unschedule), resume, dispatch, continuation, reconciliation, owned reads, due scans, bounded worker batches and account disconnect. Publish-now is an immediate schedule. Only the schedule owner may read or command a schedule; anyone else, including a non-member, receives NOT_FOUND.
Targets name an exact kind (linkedin_post, x_post, x_thread, instagram_image, instagram_carousel) and the reviewed account bindingHash. With acknowledgements the owner of every binding mints one member_approval per target, fenced to the connection version, digest and window; missing acknowledgements mint nothing. Create refuses SCHEDULE_CAPACITY (500 per workspace), the platform duplicate codes (LINKEDIN_PUBLISH_DUPLICATE, X_PUBLISH_DUPLICATE, X_THREAD_DUPLICATE), SCHEDULE_MENTIONS_UNAVAILABLE, SCHEDULE_PUBLISHER_RESERVED, SCHEDULE_SIMILAR_CONTENT (normalized text, 80% shingle overlap) and SCHEDULE_BINDING_CHANGED, as well as tracking-only, unqualified or unconsented accounts. Dispatch repeats these checks and the policy check, and holds the schedule instead of publishing; a disconnect or credential bump moves it to waiting. Resume needs fresh owner review.
Each dispatch claim increments a fence and leases the schedule; a stale fence's result is discarded and uncertain targets reconcile through canonical intents without a second post. Workers discover due scopes through the row-level security due-scope functions. Native provider qualification and live publication remain separate acceptance requirements.