deepthoughtswithbots

All projectsStarted 2026-10-13

Track Record: Movies

A series of small tests of whether the past predicts what comes next. Volume 1 asks whether a film's director, cast or studio predicts how critics will review it, using 17,126 films and public data from Wikidata.

Drafted by a bot from my own words. I’ve edited and approved everything that is on this site.

Problem
Does the past predict what comes next? Specifically: do the people behind a film (cast, director, studio) predict how critics will review it?
Approach
Use public Wikidata, build every prediction forward-only, compare with a plain baseline, check the data against an outside source, and publish every result, including the ones that showed nothing.
Solution
A live site with four games, a methods page with ten further analyses, and a generated build record, plus a reusable skill and this portfolio so the next question takes less work.
Result
The director's record predicts a film's score far better than the cast's (0.56 against 0.06), yet the best guess is still about 16 points off. Several popular hunches (stars, runtime, experience) showed little. The site is live; there is no usage data yet.
17,126films, 2000 to 2025
0.56director record vs. the film's score
0.06cast record vs. the film's score
45 of 46Rotten Tomatoes spot-checks matched
Open the siteHow it was builtMethods and findings

What this shows

Speed

From a starting app and spec to a live, tested, multi-page analysis site in one evening. The build log shows 17 commits between Oct 13, 2026, 9:58 PM and Oct 14, 2026, 12:40 AM Central (2 h 42 min from the first commit to the latest).

The first commit already held a starting app and spec from an earlier session, so the timeline counts the work after it. Commit time is not time worked: data downloads ran in the background, and I reviewed and steered between commits. Counts verified against the repo on 2026-10-14.

Decided by me

  • Moved from a critic leaderboard to actors, then to directors, when the data pointed there.
  • Kept real-money betting out and made the prediction games free to play.
  • Launched free with no paywall, because the free hosting plan is non-commercial.
  • Named it Track Record and made it a series, with movies as volume one.
  • Asked for plain wording in the games and a notebook look for the site.
  • Asked for a generated record of what the AI built and when.

Done by the AI

  • Wrote the data pulls, the analyses, the site and the games.
  • Ran the tests and reported the results, including the ones that showed nothing.
  • Drafted the pages and copy for review.
  • Flagged limits and risks: licensing, hosting terms, and where claims went further than the data.

Decisions that shaped the build

Insisted on a clean, openly licensed data source.No legal risk, and every result can be reproduced.
Pushed past a data blocker to find a legal route.Led to Wikidata: no key, public domain, and 17,126 films.
Checked the hosting terms before launch.Spotted that the free plan is non-commercial, which shaped a free, compliant launch.
Made ownership and security a requirement.Private repos, accounts in my name, and a domain I control.
Pushed for friendly, plain wording.The games use an approachable 'cast-only guess' instead of technical jargon.
Set a distinct design direction.A line-printer look that stands apart from template sites.
Cut feature creep and refocused on what's fun.Shipped one-tap Higher or Lower.
Asked the sharper question about production quality.Led to the director analysis, the strongest finding in the project.
Tested the site like a visitor.Added navigation on every page.
Asked for a verifiable record of the work.A build log generated from git, shown on the site.
Turned the method into a reusable skill.New ideas can run through the same tested process.
Spotted a game that gave away its own answer.Moved the duel to its own page.
Chose openness about AI's role.Every page states who wrote what.

How it was checked

Issues caught before publishing

Build record

From the project's git history: 17 commits, 17 marked as AI-assisted, between Oct 13, 2026, 9:58 PM and Oct 14, 2026, 12:40 AM Central (2 h 42 min). Commit time is not time worked: background jobs ran between commits and some projects began with earlier work. Refreshed Oct 14, 2026, 12:40 AM.

Oct 13, 2026, 9:58 PMCritic accuracy leaderboard: zero-config Next.js app and specAI-assisted
Oct 13, 2026, 10:52 PMTrack Record: actor tiers, guess-the-score quiz, daily filmAI-assisted
Oct 13, 2026, 10:54 PMAdd /method page with backtest scatter plotAI-assisted
Oct 13, 2026, 10:57 PMShare cards: OG image, share landing page, emoji result lineAI-assisted
Oct 13, 2026, 11:00 PMAdd Higher or Lower gameAI-assisted
Oct 13, 2026, 11:12 PMClarify signup purposeAI-assisted
Oct 13, 2026, 11:13 PMSupport hosted newsletter subscribe linkAI-assisted
Oct 13, 2026, 11:16 PMNotebook-style home, actor tiers page, notes stubAI-assisted
Oct 13, 2026, 11:21 PMAdd site header navigationAI-assisted
Oct 13, 2026, 11:26 PMMethod page: director finding, genre check, cast comparisonAI-assisted
Oct 13, 2026, 11:40 PMTrack Record series: Movies hub, format page, how-built, nine analyses, logoAI-assisted
Oct 13, 2026, 11:44 PMAdd spot-check scriptAI-assisted
Oct 13, 2026, 11:52 PMAdd build log: generated record of AI-assisted work from git historyAI-assisted
Oct 13, 2026, 11:52 PMRefresh build logAI-assisted
Oct 14, 2026, 12:29 AMMove the actor duel to its own page; the actors page is now just the tableAI-assisted
Oct 14, 2026, 12:35 AMMethod page: What we learned and why it matters, generated from the resultsAI-assisted
Oct 14, 2026, 12:40 AMRefresh build logAI-assisted

Limits

The findings are correlations. Only films with a score and a director on Wikidata are included, and directors need three earlier films, which favors established ones. The prediction model is a transparent baseline, around 15 points off for established directors, not a forecast.