Opponent scouting one-pagers

Each report reads the way a staff consumes it: the keys up top, then the evidence beneath them. The shot profile prices where a team shoots from using a model whose season-to-season transfer was validated by backtest; personnel is split into shot diet (the part that repeats year over year) and shot making (the part that is half noise), and the making numbers are shrunk by empirical Bayes before any bullet is allowed to call someone a shot-maker, so a hot month cannot drive a game plan. Lineups come from the per-team files, player impact from the opponent-adjusted RAPM model, and every claim in the keys traces to a number in a table below it.

The reports cannot silently drift: the pipeline regenerates the Phoenix report in memory on every family check run and fails unless the committed copy matches byte-for-byte.

How they're built →