Luzardo Was Filthy, Boston Was Chaos, and We Went 2-1

Fifteen games on a Tuesday slate is a lot of baseball, and the universe gave us a little bit of everything — a gem in Philadelphia, a blowout at Fenway that made our under look like a crime scene, and two quieter games that did exactly what we thought they would. The moneyline card came up empty; no material edges cleared our bar on that side, and that's fine. We don't manufacture conviction. On totals, we went 2-1, and the one loss was loud enough that we should probably talk about it before anything else.

The short version of Tuesday: disciplined construction on two of three totals paid off. The exception — Chicago White Sox at Boston Red Sox — was a reminder that baseball does not care about your model, your line, or your feelings. A 14-2 final will do that.

No moneyline plays published Tuesday. Nothing cleared the five-point threshold. Moving on.

Totals went 2-1. Here's the honest accounting:

• CHW @ BOS — Under 9 — LOSS. Final: Boston Red Sox 14, Chicago White Sox 2. Total runs: 16. Look, we liked the pitching matchup, we liked the number, and then Boston's offense decided Tuesday was the night. Sixteen runs. Seven over the line. The loss stings less as a methodology failure and more as a this-is-baseball reminder — one team can go completely sideways and there's no hedge for it. We own it.
• MIA @ ATL — Under 9 — WIN. Final: Atlanta Braves 4, Miami Marlins 2. Total runs: 6. Clean. Three runs under the line, exactly the kind of low-possession game the number suggested. No drama.
• DET @ SEA — Under 8.25 — WIN. Final: Detroit Tigers 8, Seattle Mariners 0. Total runs: 8. This one squeaked through — eight runs against a line of 8.25, with all eight coming from one side. The shutout made it a win, but we'll acknowledge it was closer to the margin than the MIA/ATL game. A win is a win; we don't get to pick the aesthetics.

Season totals record on Tuesday: 2-1-0. We'll take it, all things considered, given what happened in Boston.

441 players scored across the slate. Our model matched 146 of them to projections. Here's where it got interesting.

Top Scorers

• Jesus Luzardo, Philadelphia Phillies — 32.4 DraftKings points. Eight innings, seven strikeouts, zero earned runs. That's the kind of outing that wins DFS contests outright. We don't have a projection on file for Luzardo Tuesday, so we can't claim the call — but we can appreciate the performance. That was a genuinely elite start.
• Caleb Durbin, Boston Red Sox — 32.0 DK points. 2-for-3, one home run, four RBI, one stolen base. Our projection had him at 7.74 points on a $3,400 salary. That's a 24-point beat at the cheapest price point on the list. Whatever lineup construction you used Tuesday, if Durbin was in it, your night got a lot better.
• Wilyer Abreu, Boston Red Sox — 30.0 DK points. 2-for-4, two home runs, two RBI. We projected 9.91 points at $4,500. Another substantial beat — 20 points over projection. You see a theme here: the Boston blowout that killed our under made two Red Sox hitters among the best plays of the slate. That's baseball doing baseball things.
• Luis Torrens, New York Mets — 28.0 DK points. 3-for-3, one home run, four RBI. Our projection was 5.32 — a significant beat. No salary on file for context, but 28 points from someone projected at 5.32 is the kind of outcome that moves tournament results dramatically.
• Liam Hicks, Tampa Bay Rays — 27.0 DK points. 2-for-5, one home run, four RBI. Projected at 9.64. No salary on file. A 17-point outperformance — a legitimate best-call situation.

Where We Hit

• Caleb Durbin — projected 7.74, scored 32.0. The clearest value call on the board, and at $3,400 it was accessible in nearly any construction.
• Wilyer Abreu — projected 9.91, scored 30.0. Two home runs at $4,500. Both Boston hitters were identified by the model as undervalued; the blowout context just made it louder.
• Liam Hicks — projected 9.64, scored 27.0. A Tampa Bay Rays hitter who delivered in a quiet way — no headline game, just production.

Where We Missed

This is the part we don't skip.

• Freddy Peralta, Tampa Bay Rays — projected 16.5 DK points, scored negative 5.7. The line: 3.7 innings, three strikeouts, seven earned runs. That's a bad night by any measure, and we had him projected as a mid-tier SP anchor. He was not that on Tuesday.
• Eduardo Rodriguez, Arizona Diamondbacks — projected 14.38, scored 4.2. Five and two-thirds innings, four strikeouts, five earned runs. Serviceable inning total, terrible run suppression. We were wrong about the run-prevention part.
• Davis Martin, Chicago White Sox — projected 13.67, scored negative 12.5. Five innings, one strikeout, nine earned runs. The same Boston offense that blew up our under also put a -12.5 DK score on our SP projection. If you rostered Martin in any format Tuesday, that's a rough one. We missed on the game environment, and Martin made it worse.

The pitcher misses were real. Three starters projected in the 13-to-17 DK point range combined for significantly negative value. That's worth noting going forward on how we weight SP upside in high-variance environments.

Two things Tuesday made clear, and neither requires a lot of spin.

First: when one team's offense goes completely off the rails in a blowout, the under is obviously going to suffer — but it also tends to create enormous DFS value on the hitting side that the projection probably underweighted going in. Durbin and Abreu were both identified as value plays, and the blowout context amplified it. That's not a miss on our end, but it's a calibration point: when we see a high-upside offensive environment for one team, we may want to weight the hitting projections more aggressively alongside the total lean, rather than treating them as separate conversations.

Second: the SP projection misses weren't random. Three pitchers we liked at mid-range salary points all gave up multi-run innings, two of them severely. When we're anchoring DFS builds around a projected 13-to-16 point SP, we need to be more honest about the variance band on that number — especially with pitchers who don't have a long track record of run suppression. The projection can be right in expected value terms and still produce -12.5 a meaningful percentage of the time. We'll look at how we're communicating that range to you.

We went 2-1 on totals Tuesday. The DFS slate had real hits and real misses, and we're naming both. That's the only way this works.