Luna deep analysis — slate 20260901

Coverage receipt: COMPLETE · 9/8 sections; 15/15 games; 8/8 causes; 6/6 sources

1. Evidence receipt and gaps

Sources received

All seven manifest entries were checked against the supplied evidence:

SourcePathSizeStatusUse
Prediction review/app/output/reports/prediction_review_20260901.json373,178 bytesLoadedOfficial outcomes and scoring errors
Forensic deep audit/app/output/reports/PREDICTION_SYSTEM_DEEP_AUDIT_20260901.json240,806 bytesLoadedProbability, provenance, starter, and decision contracts
Continuous learning/app/output/learning/continuous_learning_daily_20260901.json1,939,278 bytesLoadedStage quality, calibration, lineage, score distribution, starter comparisons
Detailed report/app/output/reports/detailed_20260901.html355,722 bytesLoadedFull game and simulation rendering
Ultra-detailed player audit/app/output/reports/20260901_ultra_detailed_player_audit.html6,288,497 bytesLoadedPlayer-level prediction trace
Structural audit/app/output/reports/audit_report_20260901.html383,197 bytesLoadedInvariant findings
Integrity revision audit/app/output/reports/audit_report_20260901_integrity_revision.htmlNot suppliedMissingPost-remediation proof for immutable revision artifacts

The missing integrity-revision audit is the principal evidence gap. It does not, by itself, prove a prediction error, but it prevents a fully closed artifact-revision audit.

Slate coverage

The evidence reports:

The 15 reviewed games were:

ATL@WAS, BAL@COL, CHW@HOU, DET@MIN, MIA@KC, MIL@CHC, NYM@TB, NYY@LAA, OAK@TEX, PHI@ARI, SD@CIN, SEA@BOS, SF@PIT, STL@LAD, and TOR@CLE.

Internal contradictions and gaps

  1. Missing integrity-revision artifact. The manifest explicitly marks one source as missing.
  2. One material probability-lineage defect. TOR@CLE states that the publication delta has “no recorded transformation.” The delta is published probability 0.555236 versus governed/calibrated probability 0.545, a +0.010236 movement. This is a lineage/contract defect even though it did not change the winner.
  3. One structural warning. STL@LAD has a pitch-count mismatch for Michael McGreevy: summary BF 24 versus box-score BF 23.
  4. Aggregate audit contradiction requiring care. The slate-level structural summary reports zero critical and zero error findings, one warning, and 108 informational findings. That is consistent with the per-game records supplied, but “all artifacts passed critical/error gates” does not mean the slate is artifact-perfect: the warning, unexplained TOR probability delta, and missing integrity-revision source remain.
  5. Calibration-label inconsistency. The calibration object defines error as average published confidence minus observed hit rate, with positive meaning overconfidence. The 0.50–0.55 and 0.55–0.60 buckets are labeled “underconfident” despite negative errors, which is directionally consistent with the definition. The high buckets have zero hits and are clearly overconfident. However, the displayed bucket errors for the high buckets equal average confidence rather than a separately rounded confidence-minus-hit-rate field; this is mathematically expected when observed hit rate is zero, not necessarily a defect.
  6. Starter and player data are retrospective comparisons. They support diagnosis but do not establish that a pregame input was wrong unless the relevant pregame signal and transformation are shown.

2. Executive diagnosis

Overall slate result

The system went 7–8, or 46.67% winner accuracy. The continuous-learning summary reports:

A correct winner is not equivalent to a good prediction. The slate contains several correct winners with large score errors, including SF@PIT and CHW@HOU.

Winner accuracy

Winner accuracy was poor relative to the model’s historical validation:

The main winner-direction problem was not uniformly one thing:

Calibration quality

Calibration was the clearest probability-quality failure.

The low-confidence buckets were underconfident on this sample, while the higher-confidence buckets were severely overconfident. The evidence supports a bounded shadow adjustment, not an immediate permanent recalibration, because the high-bucket sample is only four games and the causal register correctly warns that a single slate is too small to establish a stable calibration curve.

Score accuracy

Score accuracy was materially poor and structurally biased toward narrow margins:

The score_margin_compression causal issue is therefore materially supported and has severity high, not critical. The do-not-infer guardrail remains important: one blowout is not enough to widen all scores. Here, however, the distributional evidence spans nine actual margins of at least four and two consecutive slates in the supplied trend record.

Starter accuracy

Starter projections were a significant source of score and winner error:

The lever-tension record says the pitcher-weight lever “helped” 10 games and hurt none by the supplied attribution, but that is a descriptive slate count, not a causal estimate.

Artifact integrity

Artifact integrity was mostly sound but not clean:

The high-severity artifact_integrity_warning issue is appropriately preserved: the warning is a presentation or contract risk, not proof that the model chose the wrong side.

Causal issue register reconciliation

IssueSeverityEvidence and affected gamesActionGuardrail
Canonical artifact warning requires reconciliationHigh1 warning, 108 info; no critical/error. No specific game list.Fix the flagged stat/presentation contract before considering the slate clean.Does not prove a wrong-side pick.
Published margins compressedHigh13/15 predicted margins ≤2; 9/15 actual margins ≥4; mean margin 1.67 versus 4.20. Affected games listed as CHW@HOU, DET@MIN, MIL@CHC, NYM@TB, PHI@ARI, STL@LAD, TOR@CLE.Check rolling-slate tail coverage and margin MAE before widening score spread.Do not widen every score because of one blowout.
Single-slate calibration instabilityHighWAC error 0.2476 across all 15 games.Monitor the same buckets over the rolling window before changing calibration weights.Fifteen games do not establish a stable calibration curve.
Weak run-model signalHighHome/away/total R² 0.0361/0.0227/0.0280 over 2,062 rows.Investigate features and target via isolated training backtest.Positive R² does not make exact scores reliable.
High raw-probability clusterMedium0/4 high-raw selections won.Track across multiple slates; preserve raw→calibrated→published lineage.Do not create a new bucket-shrinkage rule from one slate.
Complete slate audit coverageInfo15/15 structurally audited.Keep per-game audit receipts.Coverage does not cancel internal findings.
Publication delta explainedInfo9 material movements had named transformations.Continue displaying every layer and transformation.Published > calibrated is not a bypass when explained.
Simulation inert on slateInfo for current slate; escalated across slates0 flip candidates and 0 published flips.Measure simulation contribution over rolling slates.No winner flips does not prove no score reconciliation occurred.

3. Every game

Probabilities below are published probability for the selected/predicted side. The signed confidence edge is home probability − away probability; therefore negative values indicate an away selection.

ATL@WAS — Miss; wrong winner and wrong score

BAL@COL — Miss; wrong winner and wrong score

CHW@HOU — Hit; correct winner, wrong score

DET@MIN — Miss; wrong winner and largest score miss

MIA@KC — Miss; wrong winner and wrong score

MIL@CHC — Miss; wrong winner and wrong score

NYM@TB — Hit; correct winner, wrong score

NYY@LAA — Hit; correct winner, wrong score

OAK@TEX — Hit; correct winner, wrong score

PHI@ARI — Hit; correct winner, wrong score

SD@CIN — Miss; wrong winner and wrong score

SEA@BOS — Miss; wrong winner and wrong score

SF@PIT — Hit; correct winner, very wrong score

STL@LAD — Miss; wrong winner and wrong score

TOR@CLE — Hit; correct winner, wrong score; lineage defect


4. Miss reconstruction

Earliest wrong-direction stage for each loss

A later recovery cannot erase an intermediate regression. The stage audit must therefore distinguish final outcome from path quality.

ATL@WAS

BAL@COL

DET@MIN

MIA@KC

MIL@CHC

SD@CIN

SEA@BOS

STL@LAD

Error-type classification across losses

Pipeline-stage quality across all stages

StageWinner accuracyWinner hitsMargin MAETeam-run MAETotal-run MAE
Historical ML46.67%74.17693.09774.6893
Variance applied40.00%64.13333.06674.6667
Enhanced prediction40.00%64.93333.26674.6667
Embedded Savant/run environment40.00%64.86673.16674.4667
Fundamental edge target review46.67%74.80003.13334.5333
Capped target46.67%74.80003.13334.5333
Simulation result46.67%74.80003.13334.5333
Published final46.67%74.80003.13334.5333

Transition audit

The key conclusion is that the enhanced stage was the main score-quality regression versus historical ML, while fundamental-edge review recovered one winner. The recovery does not erase the earlier regressions.


5. Cross-game counterfactuals

Lever tension 1: Widen score distributions

Lever: score.variance_multiplier / score.variance_floor

Lever tension 2: Pitcher form weights and prior games

Lever: player.pitcher.v4 form weights / player.pitcher_prior_games

Lever tension 3: Recent/season run-mean weighting

Lever: recent.* / season.* run-mean weighting

Tempting one-game fixes that must not be made

  1. Do not widen every score because of DET@MIN. The causal register explicitly prohibits this.
  2. Do not permanently shrink all high probabilities because BAL@COL, MIL@CHC, SD@CIN, and STL@LAD lost. The four-game cluster is a warning, not a stable calibration curve.
  3. Do not increase venue weighting solely from MIA@KC. MIL@CHC provides supporting evidence, but the venue split must be validated across the rolling window.
  4. Do not remove recency controls because of SEA@BOS. NYM@TB, NYY@LAA, and PHI@ARI show that recency/quality information can coexist with correct winners.
  5. Do not treat the simulation as a failed winner selector solely because it produced zero flips. Its persistent inertness requires a code/diagnostic check, not an arbitrary parameter move.
  6. Do not treat the STL pitch-count warning as the cause of the STL loss. It is a data-contract issue, not evidence of wrong-side causation.

6. Data and contract defects

Critical findings

Error findings

Warning findings

  1. STL@LAD: pitch-count mismatch
  2. Player: Michael McGreevy.
  3. Rule: PITCH_COUNT_PITCHER_MATCH.
  4. Summary BF: 24.
  5. Box-score BF: 23.
  6. Source: simulation.
  7. Severity: warning.
  8. Game risk score: 10.
  9. This is an artifact/data-contract warning, not established prediction causation.
  1. Canonical artifact warning
  2. Slate structural totals: 0 critical, 0 error, 1 warning, 108 info.
  3. The exact aggregate warning above is the only supplied warning-level finding.

Informational findings

The evidence supplies an aggregate count of 108 informational findings but does not enumerate their individual messages. The major named informational categories are:

Because individual info messages are not present in the supplied JSON, they cannot be exhaustively itemized without inventing data.

Prediction-model defects versus presentation/artifact defects

Prediction-model/process risks

Presentation/artifact defects

Coverage reconciliation

The slate cannot be called completely clean despite full coverage:

Probability-lineage audit

The required chain is raw model → calibrated → governor → score coherence/recency → published.

Games with generally recorded lineage

The following games show named transformations and no unexplained material delta:

ATL@WAS, BAL@COL, CHW@HOU, DET@MIN, MIA@KC, MIL@CHC, NYM@TB, NYY@LAA, OAK@TEX, PHI@ARI, SD@CIN, SEA@BOS, SF@PIT, and STL@LAD.

The continuous-learning finding states that nine material movements were explained by named score-coherence and/or recency transformations. The high-raw cluster specifically records all four movements as explained.

Bypass/defect


7. Cross-slate persistence

Four prior slates were loaded, creating a five-slate window from 2026-08-28 through 2026-09-01.

Finding streaks

FindingConsecutive-slate countPresent now?Interpretation
high_raw_probability_cluster1YesCurrent slate has the cluster, but the streak itself is not persistent.
pipeline_winner_instability0NoNot present now; incidence in window is 2 but no current consecutive streak.
score_margin_compression2YesCurrent and prior consecutive slate; persistent emerging run-model issue.
simulation_inert_on_slate5YesEstablished failure across all five slates.
single_slate_calibration_instability2YesCurrent and prior consecutive slate; persistent emerging calibration issue.
weak_run_model_signal5YesEstablished failure across all five slates.

The escalated_findings entries must be treated as established failures, not single-slate noise:

  1. Simulation inertness
  2. Streak: 5 consecutive slates.
  3. Target lever listed: simulation.allow_score.
  4. Metric group: run model.
  5. Metrics hurt: team_run_mae, total_run_mae.
  6. Direction: confirm simulation is running and not silently no-oping.
  7. Parameter actionability: false; this requires code/diagnostic action rather than forced tuning.
  1. Weak run-model signal
  2. Streak: 5 consecutive slates.
  3. Target levers listed: training.xgb.n_estimators, training.xgb.max_depth, training.xgb.learning_rate.
  4. Metrics hurt: team_run_mae, total_run_mae.
  5. Direction: investigate features and target with an isolated training backtest.
  6. Parameter actionability: false in the registered finding; do not force a hyperparameter change from this report.

Metric trends

All reported directions must be stated explicitly:

Top-confidence-pick streak

The top-confidence pick history is:

Current loss streak: 1. The top pick is not on a multi-slate losing streak, but the current miss is consistent with the separate high-confidence cluster concern.

Raw structural blocks


8. Adjustments for today

Recommendations are ranked by evidence strength and persistence. These are bounded shadow or diagnostic actions, not promotions.

1. Diagnose the inert simulation path — highest persistence, code action

2. Run an isolated run-model feature/target backtest — highest persistent model weakness

3. Bounded score-tail shadow experiment — persistent compression

4. Bounded calibration-confidence shadow — current calibration and high-raw cluster

5. Pitcher-form/venue shadow — material but less persistent than run-model failures

6. Single strongest current-slate driver: run-environment underprojection

The strongest single-slate aggregate driver is run-environment compression/underdispersion, because it affected the largest errors and is supported by a two-slate streak and five-slate regressing margin bias.

The bounded score.variance_multiplier recommendation above is therefore the safest direct single-slate parameter experiment. Do not separately tune a one-game DET/MIN-specific factor.


9. Bottom line

Known

Uncertain

Safest next action

The single safest next action is:

Run a non-promoting diagnostic/shadow audit of the simulation path and probability/score lineage, while testing a small increase to score.variance_multiplier only in shadow.

This addresses the five-slate simulation/run-model persistence, directly tests the current score-compression failure, preserves rollback ability, and avoids making an irreversible one-game calibration or winner-side correction.