social_post — Social Media Post

What it produces

Per-platform social media post copy (caption, hashtags, call-to-action) plus a designed image slide produced by the social-post-designer sub-agent. The output is a SocialPost record.

Pipeline sequence

social_calendar (prerequisite) ──→ social-post-writer ──→ SocialPost: dm_review
                                                                  │
                                                      [Gate 1: DM Portal — copy review]
                                                                  │
                                              dm-approve ─────────┼────── dm-reject → re-queued
                                                                  │
                                                         SocialPost: dm_approved
                                                                  │
                                                    social-post-designer enqueued
                                                                  │
                                                         SocialPost: design_pending
                                                                  │
                                                   [designer runs — GPT Image 1.5 / Azure]
                                                                  │
                                                         SocialPost: client_review
                                                                  │
                                                   [Gate 2: Dashboard — full post review]
                                                                  │
                                              client-approve ──────┼───── client-reject → re-queued
                                                                  │
                                                         SocialPost: client_approved
                                                                  │
                                                    [auto-ingest → scheduled]
                                                                  │
                                                         SocialPost: scheduled

Status machine

Fields: dmRejectionNote, dmApprovedBy, dmApprovedAt, clientRejectionNote, clientApprovedBy, clientApprovedAt, scheduledAt, version.

HITL gates

Known issue: If OPENAI_API_KEY (Azure) is not configured, the designer job fails silently and the post stays stuck at design_pending.

Deliverable status progression

Dependencies

• Requires: social_calendar — planner always schedules 1 calendar per month when social posts are planned. The calendar’s slot data is injected into the writer’s input payload (date, platform, topic angle, format).
• Activity.dependsOn is set so the social-post-writer does not start until the linked social_calendar activity is done.

DB records created

Channel requirement

Social posts do not require connected channels at scheduling time. Content is drafted and designed first; channels are only needed when the post is published to the platform. The planner always includes social posts regardless of whether the tenant has connected any social accounts.

Auto-ingest

On client_approved, the post moves to scheduled and a PublishedContent record is created. Actual publishing to the social platform occurs when the tenant’s channel credentials are present and the scheduled time arrives.

Platform distribution

Social posts are platform-specific. The platform flows through three stages:

1. Deliverable Planner (strategy.worker.ts) sets DeliverableTemplate.platforms — an array of all target social platforms (e.g. ["instagram", "linkedin", "facebook"]). Valid slugs: instagram, linkedin, facebook, x, tiktok, google_business_profile. The planner should always include all platforms the strategy targets, not just one.

2. Activity Planner (activity.worker.ts rule #11) distributes monthlyVolume evenly across platforms and creates one activity per platform per slot, setting inputHints.platform. Example: volume 12 with platforms instagram, linkedin, facebook → 4 activities each = 12 total.

3. Social Post Writer reads activity.inputPayload.platform and stores it on the SocialPost record. Default fallback is "instagram" if the field is missing.

If all posts appear as a single platform in the DM approvals queue, check DeliverableTemplate.platforms — the deliverable plan likely has only one platform listed. Fix by refreshing the deliverable plan or updating the array directly in the DB.

Key rules

• The planner must include exactly 1 social_calendar per month when social posts are planned.
• On copy rejection, the writer is re-queued with the DM’s note.
• On client rejection, the re-queue target depends on where the fault was identified (copy vs. design).
• version increments on each re-run after rejection.