No projection this week
John doesn't have a projection right now — either his team is on a bye, the week's slate hasn't been simulated yet, or he isn't in a position to draw usage. His game log and the usage read below are the real record either way, and this page picks him back up as soon as there's a game to simulate.
Why there are no counting stats here
John plays on the offensive line, and the box score has almost nothing to say about him — no target, carry or tackle records what a guard did on a given snap. What this page can show is availability: he's taken 78% of his team's snaps across 2 games, and for a lineman that IS the story, because the position is close to all-or-nothing. We'd rather show that plainly than invent a grade we haven't earned the data to publish.
How the model reads him
John's projection starts with the game, not with him. We simulate the matchup drive by drive — how many possessions each side gets, how far they travel, how often they score — and then ask what share of that flows through him given his role. That ordering matters: a productive player on a team that runs 55 plays a game has a lower ceiling than a lesser one on a team that runs 70.
What we'd flag
Read this knowing the limits. A seventeen-game season makes every rate noisy; game script can invert a player's usage inside one afternoon; and depth-chart changes often surface too late to be in the projection. For John specifically, John has only 2 games in our log, so every rate on this page is fragile; and his position produces almost no box-score data, so there is less here than on a skill player's page and we'd rather say so.