Autonomous Video Studios
HomePART II · The original programme
CHAPTER 11 · THE OWNER'S COCKPIT

The content portal

content.storeswiki.com is where the owner runs the programme: a Next.js application with its own Postgres database, two-factor sign-in and rate limiting, which reads the control host over SSH every five minutes.

SectionWhat it is for
Dashboardtoday across all projects: the newest episodes, what needs attention, views, likes and live posts
Channels and episodesevery channel in tabs (overview, episodes, brand and words); every episode with its video, scores, captions word by word, Blender assets, facts, cost and posts; retry, hold, release
Studio and Buildercreate projects, find niches, draft channels, build kits and brands, generate code or Blender episodes, schedule videos per day per channel — by pressing buttons
Publishing and calendarevery slot of every channel, what went out and what is owed, in tabs; the week and month
Failuresevery publishing failure with its lever (the chapter 'Every failure has a lever')
Connectionsevery account of every project with its health and levers, and which account each channel posts as
Long-formfilms, their acts and quality, the rotation, approvals and publishing
Analyticsviews, likes, comments, shares and followers per post, channel and platform, over time
R&D wingmeasured intelligence per video: what works, findings, forecasts, playbooks
Eagle Eyethe automation console (the chapter 'Self-healing operations')
Settingssessions, two-factor authentication, recovery codes

Every page in tabs#

A portal that grows with a programme grows 'God pages' — pages that show everything at once and take a minute to read. On 13 November the 24 such pages among the portal's 58 were split into tabs, sections and drawers, in four lanes released one at a time; every tab has its own address, so a link opens exactly the view it names. 'Goldens' taken before the move — 105 states of the 58 pages, each recording every heading, field, action and link — prove that nothing was lost. The same rules were applied to ChannelForge first.

Figure 18. The dashboard: the newest episodes with their scores, what needs attention, and the three platforms' numbers (development build, demonstration data).
Figure 19. A channel in tabs — overview, episodes, brand and words — with its three accounts and its numbers (development build, demonstration data).
Figure 20. An episode's captions tab: every caption with its timing and pace, beside the video and its scores (development build, demonstration data).
Figure 21. The Studio: projects, niches, channels and jobs, driven by buttons (development build).