Luna deep analysis — slate 20260911

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

1. Evidence receipt and gaps

Sources received

The manifest contains seven expected artifacts:

SourceStatusSizePurpose
prediction reviewLoaded377,381 bytesOfficial outcomes and scoring errors
forensic deep auditLoaded240,613 bytesProbability, provenance, starter, and decision contracts
continuous learningLoaded2,544,895 bytesStage quality, calibration, lineage, score distribution, starter comparisons
detailed reportLoaded352,194 bytesFull game and simulation rendering
ultra detailed player auditLoaded32,629,527 bytesPlayer-level prediction trace
structural auditLoaded1,840,289 bytesInvariant findings
integrity revision auditMissing—Post-remediation proof for immutable revision artifacts

The missing integrity-revision audit is the only explicit source gap. It prevents verification of post-Luna immutable-revision artifacts, but the game-level structural audits report clean saved artifacts.

Slate coverage

All 15 expected games were reviewed:

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

Coverage is complete:

Gaps and internal contradictions

  1. Player-level actuals are unavailable for the entire slate. Every game states that the player feed had no rows for 20260911. Player adjustments can therefore be reviewed as forecast inputs, but player-level realized outcomes cannot be used to verify those adjustments.
  2. The missing integrity-revision artifact is a contract gap. It is not evidence that the prediction artifacts were altered, but it prevents independent verification of immutable-revision remediation.
  3. Probability-lineage contradictions exist in three games: CHW@STL, COL@DET, and LAA@WAS. Their published probabilities differ materially from calibrated/governed values without a recorded transformation.
  4. The high_raw_cluster correctly identifies two games, but its threshold is 0.65, while the broader slate includes other probabilities above or near that level at intermediate stages. This is not necessarily an error, but the cluster definition should be checked against whether it uses raw, calibrated, or published probability.
  5. The calibration bucket labels are internally consistent with the stated definition: negative calibration error means underconfidence and positive means overconfidence. However, the single 0.65–0.70 bucket has only one game, so its 0.6529 error is not statistically stable.

2. Executive diagnosis

Overall result

Winner accuracy

Winner accuracy was acceptable and above the validated baseline, but it was not uniformly strong:

Pipeline winner accuracy was not monotonic:

The variance stage caused a one-win regression before later recovery. That intermediate regression must not be erased by the final score.

Calibration quality

Calibration is the largest probability-quality concern.

The correct diagnosis is not simply “lower all probabilities.” The calibration evidence is unstable on this slate, but the high-confidence miss and the trend record justify a bounded shadow test of confidence moderation.

Score accuracy

Score accuracy is weak and structurally compressed.

The run-model issue is a high model risk, not a critical contract failure. The data explicitly says not to infer that exact-score tuning alone will solve it.

Starter accuracy

Starter projections were mixed:

Cross-slate starter ERA error is not persistent: only 6 of 12 slates share its sign, with z = 0.26. No broad starter-weight change is justified from that trend alone.

Artifact integrity

Artifact integrity was strong at the game level:

Causal issue register reconciliation

IDSeverityEvidenceGamesActionGuardrail
unexplained_probability_publication_deltaCriticalThree games have unexplained calibrated-to-published deltas ≥2 percentage pointsCHW@STL, COL@DET, LAA@WASBlock promotion until the missing transformation is recorded and reconciledDo not assume governor bypass before tracing pick-side math
single_slate_calibration_instabilityHighWeighted absolute calibration error 0.2091 over 15 gamesAll 15Monitor the same buckets over the rolling window; do not immediately retune calibration weightsOne slate is too small for a stable calibration curve
weak_run_model_signalHighRun R² approximately 0.012–0.021 on 2,165 rowsAll 15Investigate features/target with isolated training backtestPositive R² does not make exact scores reliable
complete_slate_audit_coverageInfo15/15 structurally auditedAll 15Retain per-game audit receiptsCoverage does not cancel internal findings
simulation_inert_on_slateInfo on this slate, escalated cross-slateZero flip candidates and zero published flipsAll 15Measure simulation contribution across rolling slates; cross-slate evidence now requires code/diagnostic actionNo winner flips does not prove no score reconciliation occurred

3. Every game

Notation:

1. BAL@TOR — miss; toss-up

2. CHW@STL — hit

3. CIN@MIL — correct winner, wrong score

4. CLE@MIN — miss; toss-up

5. COL@DET — hit

6. HOU@TB — hit; toss-up went right

7. KC@BOS — high-conviction miss and correct-winner/wrong-score failure

8. LAA@WAS — hit

9. LAD@MIA — hit; correct winner, wrong score

10. NYM@NYY — hit; correct winner, wrong score

11. PHI@ATL — hit; correct winner, wrong score

12. PIT@CHC — hit; correct winner, wrong score

13. SD@SF — hit; toss-up went right

14. SEA@OAK — miss; toss-up

15. TEX@ARI — miss; moderate away edge


4. Miss reconstruction

Loss-by-loss earliest wrong-direction stage

GameEarliest wrong-direction movementClassificationReconstruction
BAL@TORhistorical_ml already favored BAL: 4.35 away vs 4.19 homeBad weighting / near-toss-up directionVariance moved to 4–4, then enhanced prediction moved toward TOR 4–5. The model ended on the wrong side with only a 0.01 edge. Starter miss, especially Scherzer allowing 6 ER instead of 3, reinforced the loss.
CLE@MINhistorical_ml favored CLE: 4.64 away vs 4.04 homeBad weighting / later winner-direction regressionVariance retained CLE at 5–4, but enhanced prediction flipped to MIN 4–5. The actual result was CLE 5–2. Both starters outperformed ER projections, especially Bradley, but that does not explain the winner-direction flip by itself.
KC@BOShistorical_ml favored BOS and the model remained on BOSRun-environment miss plus overconfidenceNo winner-direction regression occurred. BOS was backed with real conviction, but actual total was 5 versus projected 10. The score distribution was too narrow and the model overtrusted season/recent edges despite the pitcher edge being slightly against BOS.
SEA@OAKhistorical_ml was essentially tied, 5.24 SEA vs 5.19 OAKBad weighting / score-stage regressionVariance tied the game; enhanced prediction moved to SEA 7–6. The actual result was OAK 6–5. The blend temporarily favored OAK, but later stages/publication selected SEA. This is an intermediate winner-direction regression even though the final result was a toss-up.
TEX@ARIhistorical_ml favored TEX, 4.76–3.69Bad input or weighting, then starter errorThe model remained on TEX through all stages, increasing TEX to 6 runs after Savant adjustment. Kelly allowed 1 ER rather than 5, a 4-ER projection error; ARI scored 9. This was not a near coin flip: the away edge was 0.136.

Cause categories

A 0.12 home-away confidence edge is moderate, not a near coin flip. The record supports treating TEX@ARI differently from the three 0.01 toss-ups.

Pipeline-stage quality across all stages

StageWinner accuracyTeam-run MAETotal-run MAEMargin MAE
historical_ml60.0% (9/15)2.40492.87534.1176
variance_applied53.33% (8/15)2.40002.93334.1333
enhanced_prediction66.67% (10/15)2.43332.73333.9333
embedded_savant_run_environment66.67%2.40002.53333.8667
fundamental_edge_target_review66.67%2.40002.53333.8667
capped_target66.67%2.40002.53333.8667
simulation_result66.67%2.40002.53333.8667
published_final66.67%2.40002.53333.8667

Transitions:

The later recovery does not erase the variance-stage winner regression or the enhanced-stage CLE@MIN regression. The simulation generated no independent winner intervention on this slate.


5. Cross-game counterfactuals

Lever tension 1: widen run distributions

Lever: score.variance_multiplier / score.variance_floor Target metrics: Brier score and calibration error.

Lever tension 2: pitcher form weights/prior games

Lever: player.pitcher.v4 form weights / player.pitcher_prior_games Target metrics: starter ER MAE and starter outs MAE.

Lever tension 3: recent/season run-mean weighting

Lever: recent.* / season.* run-mean weighting Target metrics: team-run MAE, total-run MAE, accuracy.

Tempting one-game fixes that must not be made

  1. Do not reverse all toss-ups after BAL@TOR, CLE@MIN, and SEA@OAK; the slate also contains correct toss-up calls in HOU@TB and SD@SF.
  2. Do not eliminate recency controls because TEX@ARI missed; recency guardrails were recorded and helped preserve correct direction in other games.
  3. Do not increase every high-confidence probability solely because LAD@MIA hit after a large adjustment; KC@BOS was a high-confidence loss.
  4. Do not increase variance enough to erase the CHW@STL moderate correct call.
  5. Do not globally change starter priors from this slate; the 6-versus-5 lever tension is nearly balanced and the cross-slate starter sign is not persistent.
  6. Do not infer that simulation is harmless merely because final winner accuracy recovered; its intermediate and cross-slate inertness remains a diagnostic issue.

6. Data and contract defects

Critical findings

  1. Unexplained probability publication deltas
  2. CHW@STL: calibrated/governed 0.623, published 0.598363, delta −2.4637 pp.
  3. COL@DET: calibrated/governed 0.6071, published 0.541169, delta −6.5931 pp.
  4. LAA@WAS: calibrated/governed 0.6177, published 0.575673, delta −4.2027 pp.
  5. The contract explicitly says not to call these governor bypasses without tracing pick-side math. The correct finding is an unexplained transformation, not yet a proven bypass.
  6. Required action: block promotion until each transformation is recorded and reconciled.
  1. Missing integrity revision audit
  2. Manifest status is missing.
  3. This is a source/contract defect, not a proven prediction defect.

Error findings

Warning findings

Informational findings

Model defects versus presentation/artifact defects

Prediction-model/process risks:

Presentation/artifact/contract defects:

Complete pick-side probability lineage

The lineage was audited from raw model → calibrated → governor → score coherence/recency → published.

A bypass should be called only for those three pending mathematical trace reconciliation. Other large deltas have recorded transformations.


7. Cross-slate persistence

The cross-slate evidence covers 11 slates for most trends and 12 slates for the separate bias analysis. A single slate is noise, but escalated findings are explicitly established failures.

Finding streaks

FindingConsecutive-slate countPresent now?Interpretation
high_raw_probability_cluster0NoOccurred in 2 of 11 slates but is not current; no immediate lever move
pipeline_winner_instability0NoOccurred in 3 of 11; not current and not escalated
score_margin_compression0NoOccurred in 2 of 11; not current as a registered finding, although current margin data is concerning
simulation_inert_on_slate11YesEstablished persistent failure, not single-slate noise
single_slate_calibration_instability1YesCurrent slate contributes to an incidence of 5/11, but its consecutive streak is only one; do not call the calibration curve stable
weak_run_model_signal11YesEstablished persistent failure, not single-slate noise

Escalated findings

simulation_inert_on_slate

weak_run_model_signal

Metric trends

Cross-slate bias holds


8. Adjustments for today

Ranked by persistence, scope, expected metric, affected games, and regression risk.

1. Simulation: code/diagnostic repair, not a parameter promotion

2. Run model: feature-contract and isolated-training repair

3. Single strongest current-slate driver: bounded confidence moderation

4. Score variance: optional secondary shadow experiment

Abstentions


9. Bottom line

Known

Uncertain

Safest next action

The safest immediate action is to block promotion and run a shadow audit of the complete probability lineage for CHW@STL, COL@DET, and LAA@WAS, while separately repairing the simulation’s independent win-distribution path. This addresses the only critical contract failure first and targets the strongest persistent process defect without making an unvalidated production parameter change.