Luna deep analysis — slate 20260924

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

1. Evidence receipt and gaps

Sources received

All seven manifest entries were checked against the supplied evidence:

SourceStatusPurpose
prediction review — /app/output/reports/prediction_review_20260924.jsonLoaded, 301,958 bytesOfficial outcomes and scoring errors
forensic deep audit — /app/output/reports/PREDICTION_SYSTEM_DEEP_AUDIT_20260924.jsonLoaded, 196,012 bytesProbability, provenance, starter, and decision contracts
continuous learning — /app/output/learning/continuous_learning_daily_20260924.jsonLoaded, 2,023,270 bytesStage quality, calibration, lineage, score distribution, starter comparisons
detailed report — /app/output/reports/detailed_20260924.htmlLoaded, 285,081 bytesFull game and simulation rendering
ultra detailed player audit — /app/output/reports/20260924_ultra_detailed_player_audit.htmlLoaded, 25,971,500 bytesPlayer-level prediction trace
structural audit — /app/output/reports/audit_report_20260924.htmlLoaded, 1,530,211 bytesInvariant findings
integrity revision audit — /app/output/reports/audit_report_20260924_integrity_revision.htmlMissingPost-Luna remediation proof for immutable revision artifacts

The missing integrity-revision audit is a provenance gap, but it did not prevent the supplied per-game structural checks from running. It does mean immutable revision/remediation claims cannot be independently confirmed from this receipt.

Games reviewed

All 12 games in the slate were reviewed, and the coverage matrix reports complete game-level coverage:

The 12 games were:

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

Internal gaps and contradictions

  1. Missing integrity revision artifact. The manifest explicitly marks the integrity revision audit as missing.
  2. Pipeline trace contradiction for later winner direction. The stored transitions say that after enhanced_prediction, no later stage changed direction, but at least CIN@ATL is shown with an enhanced-stage score favoring CIN while the published prediction favors ATL. The probability trace also reports a published ATL probability of 0.560. This requires reconciliation in the raw trace; the supplied evidence does not fully establish whether the later winner changed, whether score and probability paths diverged, or whether the transition summary omitted a change.
  3. Stage summary versus per-game result ambiguity. historical_ml has 9/12 winner hits, variance_applied 6/12, and final stages 8/12. The aggregate transition record correctly identifies a three-game regression at variance application, but it does not list all winner states for every later stage.
  4. Calibration labels are internally consistent with the stated definition. The definition is published confidence minus observed hit rate. Thus 0.5248 − 0.75 = −0.2252 is underconfident, while 0.56 − 0.50 = +0.06 is overconfident.
  5. No market cross-check exists. No source-labelled moneyline was available for any game, so market agreement/disagreement cannot be used diagnostically.
  6. Starter identity coverage was complete, but not every per-player feed line was complete. For example, projected starter lines were missing for Eduardo Rodriguez and David Sandlin in the settled per-player feed, despite game-level starter comparisons being present.

2. Executive diagnosis

Overall result

The slate beat the stated walk-forward baseline and was directionally successful, but the score forecasts were weak, the probability buckets were poorly aligned, and the system had a material intermediate winner-direction regression.

Separate diagnoses

Winner accuracy

The final published pick was correct in 8 of 12 games. This is useful directional performance, but it does not imply that the numerical prediction was good.

The four losses were:

Two losses were classified as wrong-side conviction calls, one as a run-environment miss, and one as toss-up variance:

Calibration quality

Calibration was the most important winner-probability weakness on this slate.

The correct response is not to treat all probabilities as unusable. The evidence supports bounded confidence-cap and variance shadow experiments, not a wholesale calibration rewrite based on one slate.

Score accuracy

Score accuracy was materially weaker than winner accuracy.

The model predicted every margin at two runs or less:

The final-stage run model has near-zero holdout explanatory power. Exact scores should therefore remain low-confidence outputs. The model correctly identified several winners while badly missing the score magnitude.

Starter accuracy

Starter forecasts were mixed:

The cross-slate starter ERA finding remains nonpersistent, so a strong starter-weight change is not justified solely by this slate.

Artifact integrity

Artifact integrity was strong for the game artifacts:

However, the missing integrity-revision audit remains a receipt gap. It is a presentation/provenance gap, not evidence that the picks themselves were corrupted.

Causal issue register reconciliation

pipeline_winner_instability — High

This was a real model/process risk. The variance stage changed three directions to ties, and the subsequent enhanced stage recovered two correctly and moved one incorrectly. The intermediate regression must remain visible even where the final result recovered.

single_slate_calibration_instability — High

This is a real current-slate warning, but not sufficient by itself for a permanent calibration rewrite.

weak_run_model_signal — High

This is both a current-slate and persistent cross-slate model risk.

complete_slate_audit_coverage — Info

Coverage is complete; the slate is not therefore “clean” in predictive terms.

probability_publication_delta_explained — Info

This supports artifact lineage integrity for the five material movements.

simulation_inert_on_slate — Info on this slate, escalated persistent failure across slates

Cross-slate evidence now elevates this from a single-slate observation to an established code/diagnostic issue.


3. Every game

The published probability below is the probability of the published side. A home-minus-away edge of 0.12 means a 56% home / 44% away split when the home side was favored, or 44% home / 56% away when the away side was favored. It is moderate, not near certainty and not a near coin flip.

ARI@COL — correct winner, wrong score

Edges:

Starters:

Controls and score path:

Player adjustments:

Audit and causes:

CHW@KC — correct winner, wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

This game is also one of the three documented winner-direction regressions at historical_ml → variance_applied: CHW became a tie before recovering to CHW at enhanced prediction.

CIN@ATL — wrong winner and wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

CLE@BOS — correct winner, wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

HOU@OAK — correct winner and close score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

LAA@SEA — wrong winner and wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

MIA@CHC — correct winner, wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

MIL@PHI — correct winner, wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

NYM@TEX — wrong winner and wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

This is the third documented variance-stage instability game: historical evidence favored TEX, variance moved to a tie, and enhanced prediction moved to NYM—the wrong direction relative to the actual result.

SD@LAD — wrong winner and wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

STL@PIT — correct winner, wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:

TB@NYY — correct winner, wrong score

Edges:

Starters:

Controls and path:

Player adjustments:

Audit and causes:


4. Miss reconstruction

Earliest wrong-direction stages for every loss

CIN@ATL

LAA@SEA

NYM@TEX

SD@LAD

Cause classification

LossBad inputBad weightingCalibrationStarter errorOffense/bullpenRun environmentIrreducible variance
CIN@ATLNo clear defectYes: ATL season/recent conviction; pipeline trace instabilityModerate-confidence overcommitmentLimited; both starters close in ERSome player deviationsMinor; total closeSome
LAA@SEANo structural defectYes: form/quality favored SEAModerate-confidence overcommitmentNo material starter missLAA offense exceeded projectionMinorMaterial
NYM@TEXNo structural defectYes: enhanced stage moved from tie toward NYMLean call, not extremeRocker materially outperformedNYM offense underproducedMajor; actual total 4 vs projected 9Some
SD@LADNo structural defectNo strong evidence of bad weightingCorrectly treated as toss-upPivetta outperformedBoth lineups underproducedModerate low-run environmentMajor

The ARI@COL and CHW@KC stage regressions are not losses, but they demonstrate why final winner accuracy alone is insufficient: variance application lost three winner hits overall before enhanced prediction recovered two.

A 0.12 edge is moderate. It should not be described as a near coin flip, but it also does not represent a highly reliable prediction. On this slate both 0.12-confidence calls in CIN@ATL and LAA@SEA lost.

Pipeline-stage quality across all stages

StageWinner accuracyWinner hitsTeam-run MAETotal-run MAEMargin MAE
historical_ml75.0%92.57014.25042.2131
variance_applied50.0%62.50004.16672.1667
enhanced_prediction66.67%82.16673.83332.0000
embedded_savant_run_environment66.67%82.20833.75002.0833
fundamental_edge_target_review66.67%82.20833.75002.0833
capped_target66.67%82.20833.75002.0833
simulation_result66.67%82.20833.75002.0833
published_final66.67%82.20833.75002.0833

Transitions:

A later recovery does not erase the variance-stage regression. The system must preserve both before- and after-stage winner states.


5. Cross-game counterfactuals

Lever tension: widen run distributions

Lever: score.variance_multiplier / score.variance_floor

This supports a bounded shadow experiment, not an unrestricted increase. The lever primarily changes spread and tail behavior; it should not be used as a substitute for fixing the near-zero run-model signal.

Lever tension: pitcher form weights and prior-game weighting

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

The net slate count favors some investigation, but cross-slate starter_era_error is explicitly nonpersistent: only 5 of 12 prior slates had the same sign, with z = 1.04. Therefore, do not make a direct permanent weight increase yet. Use a shadow test only if the system can isolate credible venue/form evidence.

Lever tension: recent and season run-mean weighting

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

This is directionally favorable on the slate, but it must be reconciled with the persistent cross-slate finding that projected lineup runs are too high. The safer response is to lower the projected run environment or widen tails in a bounded experiment, not simply increase recent/season weight without examining feature bias.

Tempting one-game fixes that must not be made


6. Data and contract defects

Audit findings by severity

Across all supplied structural audits:

Every individual game reported structural audit PASS with zero critical, error, and warning findings.

Critical and error defects

There are no critical or error findings in the game artifacts.

The missing integrity_revision_audit is a manifest-level missing source, not a reported critical finding inside the game audits. It remains a provenance deficiency.

Warnings

There are no warning findings.

Informational findings

The principal informational findings are:

  1. Eight to nine informational notes per game regarding forecast-file integrity and related diagnostics.
  2. Five material calibrated-to-published probability movements with named transformations.
  3. Zero simulation winner flips on this slate.
  4. Complete 12/12 structural coverage.
  5. Starter experience and venue-split diagnostics where applicable.
  6. Large Savant run-environment swings on several games.

Prediction-model defects versus presentation/artifact bugs

Prediction-model/process defects

Presentation/provenance defects

These presentation/trace defects matter because they limit forensic reproducibility, even though they do not prove that the published forecast artifact was corrupted.

Coverage reconciliation

The slate is structurally covered:

“Complete coverage” means every game was audited; it does not mean every prediction was good. The coverage finding is therefore valid but cannot override the high-severity model findings.

Probability-lineage audit

The supplied lineage includes:

  1. Raw model pick probability.
  2. Calibrated pick probability and empirical sample size.
  3. Governor input and output.
  4. Score-coherence probability.
  5. Recency guardrail.
  6. Published probability.

Material examples:

The evidence records named transformations for all five material movements and marks unexplained_material_delta: false. No probability-governor bypass is established.

There is, however, a separate probability-reversion event:

This was not a final prediction failure, but it warrants continued trace visibility.


7. Cross-slate persistence

The evidence includes 10 prior slates and an 11-slate trend window from 2026-09-14 through 2026-09-24.

Finding streaks

FindingConsecutive-slate countPresent now?Interpretation
high_raw_probability_cluster0NoAppeared in 3 slates within the window, but not consecutively present now
pipeline_winner_instability1YesCurrent-slate issue, also incidence in 6/11 slates; not yet escalated as a persistent streak
simulation_inert_on_slate11YesEstablished persistent failure
single_slate_calibration_instability1YesCurrent-slate issue; incidence in 8/11, but not an 11-slate consecutive streak
weak_run_model_signal11YesEstablished persistent failure

Escalated findings

Simulation inertness

The self-assessment gives a concrete suspected root cause: the simulation distribution is built from the same draws used to find a target-realizing play-by-play path; the loop can early-exit after roughly two selected draws. That makes the derived win rate non-probabilistic and explains repeated zero flip candidates.

Weak run-model signal

The recommended action is a code/data change, not nightly hyperparameter tuning. Candidate features named in the evidence are:

Metric trends

Every supplied metric trend is labeled improving, but the levels remain weak:

“Improving” does not mean solved. In particular, the current weighted calibration error is still 0.1701 and run-model \(R²\) remains near zero.

Top-confidence-pick streak

Cross-slate structural blocks

Margin distribution

Current slate:

Pipeline transitions

The recurring concern is not simply final accuracy; it is intermediate winner-direction regression. Current slate evidence directly confirms the variance-stage regression.

Calibration monitoring

Current bucket behavior is mixed:

High raw cluster

Simulation control


8. Adjustments for today

Recommendations are ranked by persistence and scope.

1. Fix and independently validate simulation — highest evidence strength

This is the safest persistent-pattern action because the evidence identifies an architectural cause and explicitly says not to force a parameter move.

2. Isolated run-model feature/target backtest — persistent model weakness

This is a code/data action because the evidence explicitly states that no bounded nightly knob can repair near-zero signal.

3. Bounded shadow increase in run variance — strongest single-slate actionable driver

This is not a claim that wider variance would have changed the actual winners. It is a bounded calibration/spread experiment motivated by the 3/12 large-margin outcomes and 0/12 predicted margins above two runs.

4. Hold pitcher-weight changes

5. Do not change confidence calibration weights permanently


9. Bottom line

Known

Uncertain

Single safest next action

Run the bounded simulation code/diagnostic repair in shadow: separate independent winner-probability draws from target-realization draws, remove the early-exit dependence, register the batch size, and compare its winner/Brier/run-metric contribution against the current control before changing model parameters.