SCOTUSgami

A Scorigami for the Supreme Court — every possible division of the nine justices into majority / dissent / took-no-part, with squares that fill in as real cases produce each alignment. Live at scotusgami.grannis.xyz.

Covers the current natural court (Roberts–Jackson, October Term 2022–present).

The math

Each case maps to a 9-character key over the justices in seniority order (M majority, D dissent, A absent), e.g. SFFA v. Harvard is MMMDDMMMA (6–2, Jackson out). The displayed universe, grouped by number absent:

bench	squares
full bench	256
one out	837
two out	2,304
three+ / ties	only if they occur

Data

• Oyez — primary source. Case list + per-case vote matrices, QP, holding, opinion authors and joins.
• Supreme Court Database — supplements terms where Oyez hasn't entered votes yet (currently most of OT2024). Oyez records replace SCDB ones per-docket automatically as Oyez catches up.
• supremecourt.gov — the slip-opinion list (same-day authority on what has come down, and on emergency-docket per curiams Oyez never lists) and Opinions Relating to Orders, which is where interim-docket ("A") rulings live. scripts/add-interim-orders.ts codes those lineups by hand: a justice who dissented or is recorded "would grant"/"would deny" against the order gets D, silence on an order of the Court reads as assent, "took no part" is A. Only applications that drew a published writing are discoverable that way, so the interim set skews toward divided outcomes — worth remembering before reading much into how often a given division shows up.

A Vercel cron hits /api/refresh daily at 11:15 ET to re-scrape the current term into Redis. The same job rebuilds the bingo card (/bingo — opinion authorship by argument sitting, with the justices still "owed" an opinion highlighted) and, when a never-before-seen alignment lights up, sends a notification email via Resend (RESEND_API_KEY / EMAIL_TO / EMAIL_FROM; no-op if unset).

Stack

Next.js (App Router) · Tailwind v4 · Upstash Redis · Vercel.

npm run dev                        # local dev (falls back to data/*.json without Redis env)
npx tsx scripts/check-grid.ts      # combinatorics sanity checks
npx tsx scripts/backfill.ts        # scrape all terms from Oyez → data/
npx tsx scripts/supplement-scdb.ts 2024   # SCDB gap-fill for one term → data/
npx tsx scripts/load-redis.ts      # push data/ into Upstash
npx tsx scripts/build-bingo.ts     # scrape current-term argued cases → data/bingo-*.json + Redis
npx tsx --env-file=.env.local scripts/add-ot2025-pool.ts   # current term → game pool
npx tsx scripts/add-interim-orders.ts       # interim-docket orders → Redis

Note: build/dev use --webpack (Turbopack rejects projects on mapped network drives).