Autonomous Video Studios
HomePART III · ChannelForge
CHAPTER 13 · NEW SINCE THE FIRST EDITION

What ChannelForge gained since the first edition

In the eleven days after the first edition ChannelForge received 873 commits — 2.7 times as many as in its first sixteen days. Most came from a method: study a mature product in the same market feature by feature, decide what ChannelForge should have, build it in parallel lanes behind feature flags, prove it in the owner's own workspaces, and only then open it to customers. 130 such features are switched on in the owner's workspaces today, on top of the 36 every customer has.

Three studies, about 160 features#

Product studiedFeatures readBuilt in ChannelForgeReleased
A social-media scheduler and composer1,35659 backlog items and a wave of ~70 smaller ones; 78 flags5–6 November
An AI content-creation suite1,62985 backlog items; 65 flags7 November
The owner's own YouTube tool6247 fixes and 17 ranked features; 17 flags8 November
No code was copied: each feature was redesigned for ChannelForge's stack, after checking what it already had. Some things were declined on purpose — a free-form composer, AI image and video generators, synthetic presenters, stock media, review gating, lifetime plans.

What a member can do now#

  • Write in the channel's voice. Channel words and style — avoid lists, preferred terms, calls to action, writing samples, brand facts — fed to every writer; topics imported from a CSV, a pasted list or RSS feeds; a channel's own documents used as sourced facts; pronunciations; an article written from any episode or film.
  • Check before it ships. Hand-edited text checked for limits, AI wording, numbers and units; a second-opinion critic that watches and hears the finished video (only a lower score holds it); films' dated and numeric facts re-checked against Google Search; library search by meaning, and an originality check that catches paraphrases.
  • Package and publish more. Thumbnails touched up with a live preview inside each platform's safe area, covers chosen from a frame, Mastodon, first comments through the official APIs, tracked short links, Pinterest Pins from carousel slides, brand plates for every platform, a post taken down from the app, connection health with a notice for every expired account, posting days, windows and pinned slots.
  • Run the inbox as a team. Assignments, private notes, labels, approved answers, digests by e-mail, Slack or Discord; a review studio for YouTube that checks a pack before it goes, compares the live description, moderates up to fifty comments in one call and keeps series playlists; YouTube's own search terms and retention against similar videos.
  • Work as an agency. Client roles, approval with a note, master downloads, a monthly report in PDF, a support desk whose tickets are tied to the job, episode or film they are about, and answers drawn only from ChannelForge's own documentation.
  • Ask the product. 'Ask ChannelForge', an in-app assistant, works through the member's own MCP tools and proposes what it would do with its price; nothing runs until the member clicks.

Every page in tabs#

ChannelForge's 139 pages were audited on 7 November; the 24 that had grown into 'God pages' — the channel page alone ran to about seventeen screens — were split into tabs on 8 November: the channel page into eight (overview, topics, look and voice, schedule, distribution, growth, earn, settings), the episode page into five. Every tab has its own address, old links still land in the right place, and a test of 147 page states proves nothing was lost. Its public pages now read the live feature flags, so the site never promises a feature that is not open.

Figure 27. A channel in eight tabs: its kit, brand and episodes, what needs the member, and what to press (development build, demonstration data).

Blender and word-timed captions, for members#

Blender episodes reached ChannelForge on 10 November, on the same terms as the original's: a choice of picture per channel and per episode, every word captioned, the opening line on screen, every asset credited on the episode's Quality tab. A GPU box sets itself up for Blender in about twelve minutes with 5.5 GB of cached skies, textures and models, because a job's box has no internet access. A Blender episode is a price class of its own, charged at cost times the plan's markup — about 700 to 1,100 credits on Pro — and never charged when it is held. It is switched on in the owner's workspaces first, where the critic holds it to the same 'nothing toy-like' bar. The word-timed captions are built, reviewed and merged behind two flags, not yet deployed; they go live after a trial.

Every failure has a lever, here too#

ChannelForge's publishing failure history went live on 13 November: one row per failed attempt, sixteen reasons in plain words, the same five views as the original's, a morning digest — and, beside every row, the button that fixes it: connect again, retry now, retry the waiting posts (spaced like a person, at most twenty a press and three on YouTube), skip, or 'it is there'.

Figure 28. Publishing › Failure history: each platform's health, then what needs the member, what is open, the full history and the reasons explained (development build, demonstration data).

The numbers against the first edition#

3 November14 November
Feature flags36, all open198: 36 open, 130 in the owner's workspaces, 32 off
Database tables142313
Publishing platforms911 — Mastodon and Telegram added (Telegram waits for its bot)
Job kinds54103
App pages (staff pages)130 (14)200 (42)
REST API route files · MCP tools32 · 2041 · 30
Public documentation pages7582
Plans and credit packs5 and 4the same, at the same prices
Counted from ChannelForge's code and, for the flags, its production database. Webhook events are unchanged at 23. Built but waiting for the launch of selling: receipts, promotions, local-currency prices, add-ons and automatic top-ups.