The episode is a database row

Mamba Smith is the founder of Queen City Garage, which produces The Grand National Show: a weekly NASCAR panel show on Grand National Today where broadcasters and drivers argue about the last race and pick the winner of the next one.

An episode of The Grand National Show is not a folder. It is a row in a database, and everything else hangs off it.

That sounds like a small distinction. It is the whole reason the show can be made week to week by a team you can count on one hand.

When we shipped Episode 1 at the end of August, the pieces lived where they landed: the recording in one place, the rundown on a laptop, the graphics in a render folder, the clips in a ZIP, the emails in a sent folder. The episode was fine. Finding its pieces afterward was not, and the four of us spent real time doing it. We wrote that up in The show is not done when it publishes. The lesson underneath it was that nothing owned the episode.

So before Episode 2 we gave the episode a record and made it the owner.

What the record holds

One episode row carries the number, the title, the show it belongs to, when it was recorded, its production status, the finished video, the published article, and the headline that runs on the Grand National Today homepage. Hanging off it, in linked tables, are the working documents (the rundown, guest notes, story packets), the picks each panelist made, the people who appeared, and every delivery package that went out to them.

As I write this the show's records hold 9 working documents, 17 picks, 8 people links and 17 delivery packages across the 11 episodes planned or made so far. Every one of them points back to an episode.

The point is not tidiness. The point is that a question like "what did Davey pick at Daytona" or "which files did we send after Episode 2" is a lookup, not a search through someone's laptop.

What reads from it

The website does. The episode page on Grand National Today reads the record: the video, the chapters, the panel credits. The "coming soon" pages for the episodes we have not recorded yet read the same table, one page per remaining race in NASCAR's ten-race Chase for the championship, each with its date and a countdown line. When we added those pages we checked every date's day of the week before writing it down, because a wrong weekday on a schedule page is the kind of error nobody catches until a guest shows up on the wrong day.

Our internal production desk, a screen in the same system we run the newsroom on, reads it too. That is where the rundown is edited in place, where the clip shelf lists every race clip we have marked for the episode with its rights and its topic, and where the picks scoreboard from the last race sits at the top, because scoring last week's picks is how every episode opens.

The first version of that screen taught us something about checks. The clip shelf rendered blank, even though twelve marked clips existed, because the query behind it was ambiguous. The type check passed. The build passed. The shelf looked empty rather than broken, which is worse than an error, because an empty shelf is a plausible state. Now a failed section shows the failure. We would rather see red than see nothing.

Why the rundown moved

The rundown started as a file. It was a good file. It was also on a Mac, and the show is run from a website, and the person who needed the rundown was not standing at the Mac.

The rule we wrote first was "if you ask about it across episodes it is a record, if you read it once during prep it is a document." That was half right. It reasoned about the data and ignored where the people work. The revised rule is simpler: everything about a specific episode lives in the production desk, prose included. The vault keeps only the thinking that spans episodes.

So the rundown, the guest notes and the story packets went into the episode record as editable documents. They render as formatted text, table and all, and a save from the desk is attributed to the person who made it, not to a system account.

What this buys us

A weekly show is a race against the next race. A recording on Tuesday has to be edited, checked, packaged and published before Saturday makes the picks stale. Every minute spent finding a file is a minute not spent making the show better.

One record, everything attached, everything readable by the site and the desk. That is the foundation. The next thirteen posts in this series are about what we built on top of it.

What a person did: decided what an episode is, and where its pieces live. What the machine did: kept every piece attached to the right episode, and answered the question when asked.

This is No. 01 in How We Make the Show, the Queen City Garage build log on producing The Grand National Show. Watch the show at Grand National Today.