The market can rank games. It cannot rank receivers without receiver rows. The old version published an ordered board from a total, a spread, and team notes. That looked decisive because the missing evidence was hidden in the prose.
Data limit: no receiver projection, route share, target share, active-status row, scoring format, or consensus rank was supplied. This module publishes no WR order and no weekly betting lean.
The Melbourne market is real and team-level
The 49ers and Rams are scheduled to open Week 1 in Melbourne, Australia . The captured market lists the Rams favored by 2.5, a 48.5-point total, and moneylines of Rams -148 and 49ers +124 .
That row can identify a game worth inspecting for fantasy volume. It does not identify the receivers, their routes, their target competition, or the scoring format. A healthy total can support a passing environment and still leave the production concentrated, split, or routed through other positions.
The old copy also called the Rams an underdog after citing them as the favorite. That contradiction is removed. The source says Rams -2.5 . The article does not reverse the sign to make a late-game narrative work.
Travel is a season note, not a Week 1 receiver rank
The 49ers are listed at 38,105 travel miles, described as a single-season record, and at 58 time zones, also described as a single-season record . The Rams are listed at 34,847 miles .
Those facts may matter across the schedule. They do not tell us which receiver gains or loses a target in Melbourne. Both teams travel to the opener, and the source supplies no player effect. Calling travel a second-half dock or a Week 1 non-factor would be another unsupported projection.
A travel feature belongs in a model after its timing and effect are tested. Until then, it belongs in the notes column.
The Chiefs note does not identify a beneficiary
Kansas City is recorded at 6-11 in the 2025 regular-season window, a sample of 17 games . The source also says Patrick Mahomes is rehabbing a serious left knee injury and Travis Kelce may be near the end of his career .
That is an offense to monitor. It is not evidence that a discounted receiver inherits a specific number of targets or belongs in a Week 1 tier. Targets can move across several players, the offense can change shape, and the quarterback context can reduce the total opportunity.
The correct next step is to read the current depth chart, practice participation, and route expectations. “The targets have to go somewhere” is a question, not a ranking.
A WR board needs player-level rows
A defensible receiver projection starts with active status, route participation, target opportunity, depth of target, red-zone role, quarterback availability, opponent context, and scoring format. The game market can then constrain the team environment.
Every receiver should be evaluated in the same decision window. A consensus comparison also needs a named source captured at that time. Without both sides, “our board versus consensus” is a headline the data cannot cash.
The WR rankings and projection surface are where current player rows belong. The model-versus-consensus guide explains how to inspect a real difference.
What would make the order publishable
A current player feed would. It must identify the receivers, their roles, health, quarterback context, scoring format, and market timestamp. The model output should include uncertainty rather than only a point estimate.
Then the board can be ordered, compared with a named consensus, and updated when a real input changes. Until that contract is met, the honest Week 1 WR ranking is no ranking at all.
The game notes remain useful. They just stop pretending to be receivers.
DFS outcome leverage versus recorded ownership
This chart remains empty until a verified source binds ownership projections to settled lineup outcomes for the same contests.
Prop hit rate versus recorded line distance
This chart remains empty until a verified source binds a player projection distribution, the offered prop line, and the settled result.
