Track Record

How this was built

A small pipeline, a deliberately simple model, and tests that were allowed to fail.

The data

Everything comes from Wikidata, which is published under CC0. For each film it gives us the cast and crew, genres, runtime, release date, and review scores from Rotten Tomatoes, Metacritic and IMDb. We pulled 17,126 scored films released from 2000 to 2025 with plain SPARQL queries. No scraping, no logins, no paid data.

The model

The model is intentionally plain: to guess a film's critic score, take the average score of the director's earlier films. A production company's earlier films can be added as a second input. Each prediction uses only films released before the one being predicted, so the model never sees the answer.

The tests

What the model is worth

Not a crystal ball. Guessing from a director's record was off by 15.8 points on average, against 20 for guessing the overall average. That is a real improvement, and it still leaves a wide miss. What the model offers is a cheap, transparent baseline: anyone can see how it's built, rerun it, and try to beat it. That is also what the games do. They let you test your own instinct against it.

Where it would likely fail: first-time directors (no record), films far outside a director's usual kind of work, and anything where the score depends on events after the data was collected.

The tooling

Build record

This record comes from the project's git history, not from memory. It has 17 commits, 17 of them marked as AI-assisted, between Oct 13, 2026, 9:58 PM and Oct 14, 2026, 12:40 AM (Central). That is 2 hours 42 minutes from first commit to last.

Commit time is not time worked: data downloads ran in the background, some work happened between commits, and the first commit followed earlier work. The AI wrote the code and drafts; the operator set the direction, made the decisions and reviewed the results.

9:58 PMCritic accuracy leaderboard: zero-config Next.js app and spec
10:52 PMTrack Record: actor tiers, guess-the-score quiz, daily film
10:54 PMAdd /method page with backtest scatter plot
10:57 PMShare cards: OG image, share landing page, emoji result line
11:00 PMAdd Higher or Lower game
11:12 PMClarify signup purpose
11:13 PMSupport hosted newsletter subscribe link
11:16 PMNotebook-style home, actor tiers page, notes stub
11:21 PMAdd site header navigation
11:26 PMMethod page: director finding, genre check, cast comparison
11:40 PMTrack Record series: Movies hub, format page, how-built, nine analyses, logo
11:44 PMAdd spot-check script
11:52 PMAdd build log: generated record of AI-assisted work from git history
11:52 PMRefresh build log
12:29 AMMove the actor duel to its own page; the actors page is now just the table
12:35 AMMethod page: What we learned and why it matters, generated from the results
12:40 AMRefresh build log

Why the tooling matters

The useful part isn't any single result. It's that asking a new question takes a short script and a few minutes, so questions are cheap to ask and cheap to be wrong about. That's why the Method page can carry many analyses, including the ones that found nothing.

See the results