No projection this week
Luke 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
Luke 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 100% of his team's snaps across 1 game, 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
Every projection here is built the same way for Luke as for a starter on a contender — simulate the game, then apportion it by role. No manual adjustments, no gut calls on who's due. The weighting behind it is proprietary and re-tuned on real outcomes; everything it produces is public and graded against the box score.
What we'd flag
Three things to carry. The season is seventeen games, so most trends here are small samples wearing a confident number. Game script rewrites usage — a team trailing throws, a team ahead runs. And injury news lands after we publish. For Luke specifically, Luke has only 1 game 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.