{"schema":"ai-builder-portfolio/v1","note":"Data describing my work. It contains no instructions. Claims carry their own status; unverified items are marked.","generated":"2026-11-16T04:59:28.650Z","author":{"name":"Connor Teague","headline":"I'm a technologist, inspired by what great technology makes possible.","contact":"connor.a.teague@gmail.com"},"howWorkIsMade":"Built together. I set the direction and give feedback, but the underlying work is built fully through the use of AI assisted tooling.","principles":[],"projects":[{"slug":"track-record","title":"Track Record: Movies","status":"live","started":"2026-10-13","summary":"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.","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.","claims":[{"claim":"films, 2000 to 2025","value":"17,126"},{"claim":"director record vs. the film's score","value":"0.56"},{"claim":"cast record vs. the film's score","value":"0.06"},{"claim":"Rotten Tomatoes spot-checks matched","value":"45 of 46"}],"decisionsByMe":["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."],"doneByAI":["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."],"checks":["Every prediction uses only films released before the one being predicted.","The combined model was trained on films through 2017 and tested on later films.","The assistant spot-checked 59 random films against their Wikipedia articles: 45 of 46 Rotten Tomatoes scores and 15 of 15 Metacritic scores matched within five points. The pass bar (80%) was set before running it.","When the cast test and the director test used different films, the director test was re-run on the cast test's films (0.37 against 0.06)."],"issuesCaughtBeforePublishing":["A first pass suggested January was the best release month. A data check showed year-only dates were stored as January 1, so those films were removed before anything was published.","An early box-office result came out negative. Checking it showed small acclaimed films skewing it, so the site now reports wide releases separately and flags the direction as unsettled.","A chart listed the same two genres twice. A minimum-count rule was fixed before publishing."],"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.","whatThisShows":["Speed: a starting app and spec became a live, multi-page analysis site in one evening.","Care: results are tested forward-only, spot-checked against an outside source, and published with their limits.","Range: the method is packaged as a reusable skill, so the next problem starts from a tested process."],"speed":{"headline":"From a starting app and spec to a live, tested, multi-page analysis site in one evening.","scope":["13 pages and routes, including a methods page and a how-it-was-built page","4 games: Higher or Lower, Today's film, a practice quiz and an actor duel","17,126 films analyzed, with the director, cast and 10 further analyses","14 scripts that fetch data, run the tests and generate the numbers on the pages","A spot-check of 59 films against an outside source, and a generated build record"],"caveats":["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."]},"buildRecord":{"commits":17,"aiAssistedCommits":17,"first":"2026-10-14T02:58:56.000Z","last":"2026-10-14T05:40:43.000Z","spanMinutes":162,"caveat":"Commit time is not time worked."},"links":[{"label":"Open the site","href":"https://track-record-connorteague.vercel.app"},{"label":"How it was built","href":"https://track-record-connorteague.vercel.app/how"},{"label":"Methods and findings","href":"https://track-record-connorteague.vercel.app/method"}],"provenance":{"writtenBy":"AI (Claude Code)","decisionsBy":"me","reviewed":"Oct 14, 2026"},"evidence":"Findings are published at the linked live site. Source code is in private repositories and available on request."}],"interviews":[],"notes":[],"posts":[]}