Helm

Running several channels at once turns into an administrative problem long before it turns into a creative one. Where did that idea go? Was it researched? Did it have a source? Has it been covered? Which of this week’s ideas are ready enough to go in the newsletter?

Helm is the answer to those questions. It’s a private, self-hosted application that models everything the studio makes as one kind of object moving through one lifecycle — idea, developing, outlined, scripted, recorded, edited, published — with a research layer feeding new material in from the outside world.

The design ideas worth stealing

One table, typed. Ideas, episodes, projects and bookings are all the same kind of record with a type on them. New structure gets added as data rather than as database migrations, so extending it doesn’t mean rebuilding it.

Nothing hard-deletes. Everything archives, everything is reversible. A bad idea kept is a bad idea you can reconsider in six months when the news changes.

The stream queue is ranked, not scheduled. Items are put in priority order, never pinned to a calendar day. A heavy news day means you get through the top few and the rest simply wait — carry-over is free because nothing was ever promised to a date.

The newsletter is a view, not a copy. It queries the week’s material live rather than duplicating it, so it can’t go stale when something gets edited.

Status

Built, running, and private — it holds unpublished work, so the source stays closed. The intake side is being rebuilt before the channels go live, which is the honest state of it rather than “in production.” If the generic parts of it ever earn their own release, they’ll get one; that isn’t a promise, it’s a maybe.