About · how to read this dashboard
What to watch next, matched to what you actually watch.
Every ranking here comes out of Susan's own watch history: Netflix and Prime Video synced from the browser, Apple TV+ and Hulu logged from what she reports. Six services have a named source of their own for what's landing next. Only Susan's Cowork sessions rebuild the page. Reading it needs nothing, but dismissing a title or marking one watched needs the edit key, entered once per device. Putting those buttons behind a key is on the roadmap, not built yet.
This page is the reference. It covers what the dashboard does today and how it arrives at a number. The Guide has the method behind it, plus a prompt you can copy to build one for your own topic.
what it is
It ranks what to watch next. Candidates come from Susan's own watch history, every title back to 2010, scored against the genres that keep recurring there: British and European crime drama, spy thrillers, grounded action, music documentaries, prestige drama, food and food travel, LGBTQ+ film, British period drama, neo-Western, and heist thrillers. Horror, reality dating shows, superhero franchises, and science fiction are capped no matter what else a title has going for it.
BritBox, PBS Masterpiece, Apple TV+, MGM+, Paramount+ and Hulu each have their own official schedule or press page, and what turns up gets reviewed for what's coming next and badged plainly. Watch history syncs from Netflix and Prime Video only. Viewing anywhere else gets logged when Susan reports it. The page also tracks premieres months out, and whatever Susan is watching or seeing this week.
Automated upkeep is spread across the week rather than being a Monday event. GitHub Actions runs the checks on Mondays, alongside a Monday report on how stale the watch log has gone. Scheduled Claude tasks cover the rest: an artwork sweep on Wednesdays, a review across all five of Susan's sites on Fridays, a freshness sweep daily, and an audit monthly. None of them rebuild the recommendations. That happens when Susan asks Claude for one, and only then.
how it's scored
Every match percentage is worked out fresh at rebuild time, by Claude, against Susan's real watch history. No stored formula sits behind the numbers today. The rules are written down instead, and followed the same way every time.
A genre on Susan's signature list counts in full: British and European crime drama, spy thrillers, grounded action, music documentaries, and six more. Broad buckets like Comedy or Drama count at roughly a third. Shared cast with a title she loved adds a bonus on top, and a genre she has ruled out gets capped however well the rest of it scores. Anything already watched or dismissed drops out before ranking starts.
Turning this into a literal, stored equation (the same pattern Travel Intelligence already uses for flight scoring) is on the roadmap: see the roadmap.
the stack
Static HTML, plus two small Netlify Functions: dismiss (for the "not interested"/"finished" buttons) and status (for the currently-watching/watched buttons). Deploys via GitHub: pushing to main triggers Netlify's Git-connected continuous deployment automatically. Every push is Susan's call and runs from her own machine, with her credentials: she types most of them herself, and occasionally reviews a prepared batch and tells a Claude session to run it. No GitHub credential lives in the cloud session, and nothing pushes to main unattended. Poster artwork comes from four places: mostly The Movie Database (TMDB), plus Amazon's own image host, Wikimedia Commons, and a handful of files kept in this repo. None of them are endorsing this site.
This site, today
- Static HTML, no build step
- Two Netlify Functions: dismiss and status, both Blobs-backed, bounded, and storing one record per title so two quick taps can't overwrite each other
- GitHub repo, auto-deploy on push
- Dismiss and watch-status sync instantly across devices
- GitHub Actions checks every push and PR, plus a weekly live-site health check
- Removing a title, or marking it already seen, is carried into the permanent record by GitHub Actions itself: it records the title, takes the row off the page, and opens a pull request, rather than waiting for a chat confirm
- Every push checks the page against its own data: nothing recommended that's already in the watch log, no row for anything removed, no missing artwork, and a spread of genres rather than the same one twice
- The watch log, taste profile and exclusion list are guarded against silent truncation on every push, and the live watching/dismissed records are snapshotted into the repo weekly
Where it's headed
- A searchable view of the whole watch log, filterable by service, genre or actor
- A permanent "currently watching" entry created automatically too, not just flagged when it's missing. This is the one place a person is still genuinely needed: a good entry wants real artwork and accurate progress text, which is a judgment call rather than a diff
what's on the page
Right Now
What Susan's seeing in theaters and watching live this week.
Top Picks
Ranked candidates. The reason for each one sits right underneath it: matched genre, shared cast. Tap × to drop it.
Taste Profile
Signature genres set against generic ones, with actor affinity and the genres that stay capped.
Coming Soon
Premieres and next seasons, grouped by how firm the date is.
roadmap
Seven of eleven items are done: the recommendations, the dashboard, the domain, the weekly upkeep, the rebuild on the full history, the backend, and the corrected service list. One is in progress: Hulu, whose schedules are in and whose watch history is not. Three are still ahead: a searchable view of the full watch log, an edit key for the buttons, and a scoring formula on paper. The roadmap groups all eleven by status, and the guide covers how it gets built.
what it won't do
- Reading it requires nothing. No account, no password.
- Nothing here tracks you: no analytics, no advertising, no third-party scripts.
- The page never touches Susan's streaming accounts while you're on it. What you see is one published snapshot, rebuilt when Susan asks for a rebuild rather than on a schedule.
- It doesn't stop you reading anything. Browsing, filtering and the whole watch log are open to whoever has the link, with no account and no key. Changing what the page shows is the part that's gated: the dismiss and watched buttons need the edit key, and an automated pull request carries those choices into the stored records. That was open to anyone until 23 August 2026, which is what Protect saved changes closed.
- The data isn't sold or shared.