Social

The Social page (/social) is where every held marketing draft lands for your decision — X posts and rendered videos alike — plus the on-demand video request and a unified history of everything already posted or rejected. It replaces what would otherwise be one queue per engine on the Command Center; only a compact summary card and count stay there, linking through to this page (see Command Center).

X Post Queue

Every held X (Twitter) draft — release announcements, mention replies, feature-spotlight posts, and three Board Program sources (Megaphone's editorial calendar, Barfly's adjacent-conversation replies, War Room's release campaigns) — lands here for your decision. For each one you can:

• Edit the body inline, up to the 280-character limit (a live counter warns you if you go over).
• Approve & post — posts the draft to X immediately, using your edited body if you changed it.
• Reject — cancels the draft with a recorded reason; nothing is posted.

Populated by the X (Twitter) engine and, once armed, Megaphone/Barfly/War Room — all off by default. A War Room draft carries a recommended publish_after time as guidance in the card; it's still a normal item in this queue, decided the same way as everything else here.

Pipeline strip

Above the Video Post Queue, a strip lists every video in flight — authoring, rendering, or render-failed — each row a colored stage chip from authoring through render-failed (with the failure reason when there is one). A row for a draft that's actually reached your decision deep-links straight to it in the queue below. This is what makes an armed-but-quiet video engine legible: without it, a video mid-authoring or mid-render is invisible until it either lands in the queue or fails.

Video Post Queue

Every held video draft lands here once the render loop finishes both cuts. Each card carries a 9:16 / 1:1 cut switch so you can preview either before deciding, plus the per-platform captions:

• Preview — a live composition preview embeds the authoring task's actual HyperFrames HTML before you decide, not just the two rendered cuts.
• Edit the captions per platform.
• Approve — posts the selected cut to X (native video) and/or TikTok (inbox upload) under a heartbeat-renewed lock.
• Reject — cancels the draft with a recorded reason.
• Re-render — discards whatever's already rendered and queues a fresh render from the same composition, behind a confirm dialog. It's unconditional: available for any draft with a proposed composition regardless of whether the existing render succeeded, so you can redo a healthy render too, not just recover from a failed one. The same control also appears on an in-flight authoring task's row in the pipeline strip above, before rendering has even happened once.

Populated by the video engine, off by default.

Request a video

A Request a video button opens an on-demand dialog: a project picker (limited to projects with the video engine enabled for them), an occasion, a free-text brief, and which platforms to target. Submitting it opens a normal, assigned UX/UI authoring task directly for the chosen project, independent of the two automatic triggers (release publish, approved feature spotlight) — it works even with both of those switches off, as long as the video engine's master flag is armed. With no video-enabled project yet, the dialog says so instead of letting you submit, and points you at enabling the engine per-project on that project's settings page (Budget & Ops card). The rendered clip lands back in this same queue once the authoring task completes and rendering finishes.

History

A collapsed-by-default History section, once expanded, lists every acted-on draft across both queues — posted or rejected — newest first, merged client-side from the X and video history endpoints. A posted X entry links out to the tweet; a posted video entry lists each platform's posted id (an X id links out, TikTok's inbox upload has no public URL so only the raw id shows); a rejected entry of either kind shows the recorded reason.

Next

→ X (Twitter) engine and Video engine for what populates these queues · Board Programs for Megaphone, Barfly, and War Room · Command Center for the summary card that links here · Settings for credentials and feature flags.

llms.txt