Autonomous Video Studios
HomePART II · The original programme
CHAPTER 8 · PUBLISHING

Publishing and the calendar

A channel's calendar is a list of slots — two, three or four a day at the hours its audience is awake — on each platform it posts to. The 16 live channels post 48 episodes a day across three platforms, 144 platform posts a day — two of each channel's slots carrying Blender episodes — plus a curated LinkedIn queue and mirrors to X and TikTok.

Every post, on every platform
Slot clock

n8n (P1, P2), the Studio scheduler, ChannelForge

Posting guard

reads the platform's recent posts first

Publisher

resumable uploads, per-platform rules

Record

post id and link in the episode's record

Read back

views, likes, followers, through the day

watched, and made up when something is missed
The sentinel, every five minutes

a slot that found nothing ready is OWED and made up from surplus, spaced, never near a slot; a platform behind its siblings is put back IN STEP; a post given up after 3 tries is REPAIRED with backoff

Figure 13. Every post passes the same steps. The posting guard reads what the platform already holds before anything is sent, so a restored or duplicated host can never post an episode twice.

Platforms and how they are used#

PlatformWhat is postedHow
YouTubethe full episode as a Short; long-form filmsData API, resumable uploads; a watch re-uploads any video YouTube leaves stuck in processing
Facebookthe ≤ 89 s edit as a Reel, with an explicit thumbnailPages API (Reels), per-Page tokens
Instagramthe ≤ 89 s edit as a ReelInstagram API with Facebook Login; since 13 November Meta fetches the video from a 12-hour signed link (Projects 1, 2 and 4), uploads as the fallback
LinkedIna curated queue: 3 posts a weekday, 1 on weekend days, 4 h apartthe owner's profile, channels take turns
Xmirrors what went out on the three: the full episode when it fits X's 140 s, else the editAPI v2; waits whenever X's pay-per-use credits run out
TikTokthree new episodes a day per channel, through ChannelForge's per-post screenContent Posting API; posts stay private ('Only me') until TikTok's audit passes
Threadsmirrors, per channel when switched onThreads API; apps published, switched on per channel
Figure 14. The portal's publishing view: the next 24 hours of slots across the projects, and what is failing, ready, rendering and published, each in its own tab (development build, demonstration data).

Looking human#

Platforms flag accounts that behave like machines, so nothing here behaves like one. Titles, captions and hashtags are written per episode; make-up posts are spaced well apart and never land near a slot; and the inbox assistant answers comments on the channels' own posts in the channel's voice — minutes to hours later, in random sessions in the account's own time zone, with varied lengths and no stock phrases, and never every comment.

Schedules#

Projects 1 and 2 run on n8n: one workflow per channel holds its slot clock, and one per project starts its generation twice a day (07:00 and 19:00 UTC for Project 1, 13:00 and 01:00 UTC for Project 2). Each calls the control host over SSH with a key whose forced command can only run the control program, never a shell. The Studio's projects use the Studio scheduler, which keeps each live channel's stock ahead of its slots within the project's daily budget, now with videos per day set per channel and slots only on the platforms a channel is really connected to. Daylight-saving folds were found to skip timers, so every interval timer now runs in UTC.

A channel goes live by itself#

Launching a channel is now one task for its owner: create its accounts, connect them on the portal's Connections page and tick its slots. The system checks each connection with a test read, takes the channel's stock in order — oldest first — and leaves out by itself any episode made before the video format's overhaul of 22 October, which has no voice. Signal Voyage, Unseen View and Upright Robots went live this way on 13 and 14 November.

Figure 15. The calendar's week: every slot of every project, each with the episode it will post, the films of the rotation and what went out (development build, demonstration data).