Settled model recap · 2026-10-03
MLB Pitcher Prop Picks Recap for October 3, 2026: 1-1, -0.13 units
Review 2 pitcher-prop Picks from October 3, 2026 with the exact saved sportsbook prices, model probabilities, lineup or player values, final results, and plain-English postgame review.
Published after the saved Picks settled. The original prices and inputs stay attached.
One-minute recap
One-minute recap
The card finished 1-1 for -0.13 units. The result was mixed, so the individual price and projection reads matter more than the headline record.
Decision coverage note
Decision coverage was incomplete in the additional pitcher props lane (4 opportunities expired without a decision). This recap is complete for the 2 settled Picks that were actually recorded, but the slate does not meet full-lifecycle acceptance. No missing decision was reconstructed, and these incidents do not count as Picks or change the record above.
Saved Picks and reviews
Open any Pick for the why
MLB Player Props
2 pitcher-prop Picks, covering strikeouts and reviewed from the saved workload, opponent, and price snapshots.
Pitcher propParker Messick Under 6.5 strikeouts
CWS at CLE · 6 strikeouts · under 6.5
Betonlineag -115winSee the review ↓
Parker Messick Under 6.5 strikeouts
CWS at CLE · 6 strikeouts · under 6.5
Postgame review
Won: Parker Messick Under 6.5 Ks
Parker Messick finished with 6 strikeouts, cashing the saved under 6.5 and adding +0.87 units to the prop record.
At Betonlineag -115, the model gave the under 54.3% against a 53.5% break-even mark, a +0.8-point gap. The saved projection was 6.0 strikeouts across 23.4 batters faced. The pitcher graded 59.0/100 and the opponent strikeout matchup graded 66.1; the confirmed lineup carried a 26.6% strikeout rate.
The actual result landed almost exactly on the projection. The ticket and the point projection told the same story. We will compare the same workload, opponent, line, and price profile before changing production weights.
Saved pregame inputs
Frozen pitcher-prop inputs
Parker Messick vs. CWS
- Projected Ks
- 6.0
- Actual Ks
- 6
Pitcher and opponent values use the frozen 0–100 rolling scale. Projection standard deviation: 2.67 Ks. Robustness: 80%.
Pitcher propTarik Skubal Under 6.5 strikeouts
ATL at LAD · 7 strikeouts · under 6.5
DraftKings +120lossSee the review ↓
Tarik Skubal Under 6.5 strikeouts
ATL at LAD · 7 strikeouts · under 6.5
Postgame review
Lost: Tarik Skubal Under 6.5 Ks
Tarik Skubal finished with 7 strikeouts, leaving the saved under 6.5 on the wrong side of the line for a 1.00-unit loss.
At DraftKings +120, the model gave the under 50.1% against a 45.5% break-even mark, a +4.6-point gap. The saved projection was 5.9 strikeouts across 23.8 batters faced. The pitcher graded 63.3/100 and the opponent strikeout matchup graded 61.3; the confirmed lineup carried a 21.8% strikeout rate.
The actual result finished 1.1 strikeouts above the point projection. The projection supported the ticket, but the actual result crossed to the other side of the sportsbook line. We will compare the same workload, opponent, line, and price profile before changing production weights.
Saved pregame inputs
Frozen pitcher-prop inputs
Tarik Skubal vs. ATL
- Projected Ks
- 5.9
- Actual Ks
- 7
Pitcher and opponent values use the frozen 0–100 rolling scale. Projection standard deviation: 2.64 Ks. Robustness: 80%.
Parker Messick: What had to hold
Strikeout count: the saved expectation was 3.35915 to 8.69868 strikeouts. The pregame model centered on 6.0 strikeouts, with uncertainty around that estimate. The case becomes weaker if: the actual count falls outside the saved descriptive range; this alone does not diagnose the cause.
This range was frozen before the game as a descriptive check, not a calibrated confidence interval.
Parker Messick: What actually happened
The saved decision settled as a win, with +0.87 units on 1 units of reference risk.
Strikeout count finished at 6 strikeouts, inside the saved 3.35915 to 8.69868 range.
Parker Messick: What enters model review
These are checks of the original assumptions, not proof of what caused the result. A win does not validate every assumption, and a loss does not invalidate every forecast.
The measured observations can enter a source-verified review dataset. This recap changes no model weights; any proposed change requires separate chronological and prospective evaluation.
Tarik Skubal: What had to hold
Strikeout count: the saved expectation was 3.26265 to 8.53999 strikeouts. The pregame model centered on 5.9 strikeouts, with uncertainty around that estimate. The case becomes weaker if: the actual count falls outside the saved descriptive range; this alone does not diagnose the cause.
This range was frozen before the game as a descriptive check, not a calibrated confidence interval.
Tarik Skubal: What actually happened
The saved decision settled as a loss, with -1.00 units on 1 units of reference risk.
Strikeout count finished at 7 strikeouts, inside the saved 3.26265 to 8.53999 range.
Tarik Skubal: What enters model review
These are checks of the original assumptions, not proof of what caused the result. A win does not validate every assumption, and a loss does not invalidate every forecast.
The measured observations can enter a source-verified review dataset. This recap changes no model weights; any proposed change requires separate chronological and prospective evaluation.
What comes next
What we take forward
Each result can raise a useful question, but no single game rewrites the model. Any adjustment has to repeat across comparable frozen reads and survive a prospective test first.
Technical receipt
Fact pack: 4827f87174511988450c24ce5184e9aac74c3a384cd924226cca9f41cf2e0ea3
Decision receipts: mlb-k-prop-c9e713277fc9194d499698f0, mlb-k-prop-2a250e72f92e8a831f0a934b
Settlement receipts: 60eeab137524a3c5337d64e0035a70a4025402fc32ba1113afb0bd8c9ffa10ca, 3bd1fea7d4658c4b7238b254c5f19e93bbc370279d09591e201292fa426f344d