MEDIA & SOCIAL AUTOMATION
agentic content creation · scheduled campaigns · multi-platform
Media generation and posting workflows. The compose panel uses your cloud bots to draft copy;
scheduling hooks in when you connect a provider in Settings → Social Accounts (direct per-platform, or a swappable aggregator).
CAMPAIGN COMPOSER
draft → review → schedulePLATFORMS
connection status X / Twitter checking…
LinkedIn checking…
Instagram checking…
Threads checking…
Facebook checking…
TikTok checking…
Connect platforms in Settings → Social Accounts —
direct per-platform (sovereign default, no middleman) or a swappable
aggregator. Once a provider is connected and the live-posting gate is
open, posts go live; until then they queue + chain-witness.
Posts queue + chain-witness immediately. Live posting is
gated — requires provider connected AND the live gate open.
Opening the live gate requires an Overwatch security pass.
AUTOMATION WORKFLOWS
draft + queue · gated, never auto-posts
Draft a post and queue it (chain-witnessed). Nothing posts live until
the social go-live gate is open — queuing is always safe.
Recurring campaigns (daily digest, weekly recap, alert broadcast) build
on this draft+queue + the scheduler. Each queued post is reviewed by you;
live posting stays behind the two-gate social safety (provider connected
+ gate open), so automation drafts but never posts unattended.
IMAGE & VIDEO
local-default · cloud is explicit opt-inchecking backends…
Sovereign by default: if a local backend (ComfyUI/SD on 127.0.0.1)
is running, generation happens locally — zero egress, your prompt never
leaves the box. Cloud is a per-use opt-in that names what leaves (prompt
+ any source draft). Video has no local fallback on this hardware, so
every video generation is a cloud egress. Every generation is recorded
+ chain-witnessed (salted prompt commitment) — you can audit which ones
egressed. Cloud provider must pass a TOS review (no training-rights /
retention) before it's wired in Settings.