HomePART IV · Infrastructure, operations and economics
CHAPTER 24 · HISTORY
Timeline and effort
From nothing to two production systems in 33 days: designed and directed by the author, and built with AI engineering agents (Anthropic's Claude) working to that design.
33 days
from the first episode to this edition
1.14M
lines of code across the three trees
1,106
test files
1,527
commits since the first backup
| Date (2026) | Milestone |
|---|---|
| 12 Oct | The first episodes: ‘What if Yellowstone erupted 500 miles from you?’ and a Category 6 hurricane |
| 13 Oct | Project 1 live: four channels on YouTube, Facebook and Instagram, slots on n8n |
| 14–15 Oct | Project 2's first episodes; its twelve accounts live on 15 October; the self-healing sentinel |
| 15–17 Oct | The Studio: Projects 3 and 4 created through the browser, and their first episodes |
| 18 Oct | ChannelForge live: multi-tenant app, control plane, GPU fleet, billing; nightly GitHub backups |
| 19 Oct | Long-form films; GPU placement across pools |
| 20–21 Oct | ChannelForge's browser end-to-end test (16 channels, 45 episodes, 2 films); video format v4 with Chirp 3 HD voices; X |
| 22 Oct | Project 4's first four channels live; the LinkedIn queue; TikTok and Threads apps |
| 25–26 Oct | The film autopilot (one a day); Projects 5 and 6 (sixteen new channels); Model Cutaway, the 13th live channel; the inbox assistant |
| 27–29 Oct | Self-rescue systems: failure e-mails, a film doctor, box-loss recovery; every video kept in two clouds |
| 31 Oct | ChannelForge market research, and 25 new features built in three waves |
| 1 Nov | Everything switched on; turn-key disaster recovery; ChannelForge's public site and 75 docs pages; the posting guard |
| 2 Nov | The whole estate moved to Google Cloud: hosts, database and media |
| 3 Nov | GPUs on AWS only, in two accounts with zone failover; a full audit and rehearsal; the first edition of this dossier |
| 4 Nov | Covers on every platform; the portal's calendar and publishing pages from 12–18 s to under half a second; a bigger L4 in every pool |
| 5 Nov | Project 7 (eight channels) built in the Studio; a GPU region in Ohio for every pool; ChannelForge's first feature study and its first wave live |
| 6 Nov | Live episodes paired two to a GPU box; model calls fall back across two cloud accounts |
| 7 Nov | Held films found and the film ladder fixed; ChannelForge's second study, 85 features, live |
| 8 Nov | Every video in two buckets, the GitHub backup every four hours; X's 140-second rule; ChannelForge's pages in tabs and its third study live |
| 9 Nov | The YouTube processing watch; the Blender research film, rebuilt from real assets and word-timed captions |
| 10 Nov | Blender episodes live in both systems, the first Blender slots the same day; agents on Claude Fable 5.2 |
| 11 Nov | Every live channel posts Blender episodes twice a day; Blender agents on Opus 5.5 |
| 12 Nov | Projects 8, 9 and 10 (24 channels) and three new ChannelForge projects (24 more); films for channels not yet live; the 'nothing toy-like' rule for Blender |
| 13 Nov | Captions that are the voice, live for every project's shorts; failures with levers in both systems; the portal's pages in tabs; Connections and the live schedule; old-format videos held at launch; Signal Voyage and Unseen View live |
| 14 Nov | Upright Robots live; GPU fail-over across cloud accounts proven; a fairer release floor for films; this second edition |