Luna deep analysis — slate 20260906

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

1. Evidence receipt and gaps

Sources received

Six of seven manifest entries were loaded:

  1. Prediction review — /app/output/reports/prediction_review_20260906.json, 377,236 bytes; official outcomes and scoring errors.
  2. Forensic deep audit — /app/output/reports/PREDICTION_SYSTEM_DEEP_AUDIT_20260906.json, 240,848 bytes; probability, provenance, starter, and decision contracts.
  3. Continuous learning — /app/output/learning/continuous_learning_daily_20260906.json, 2,489,405 bytes; pipeline quality, calibration, lineage, score distribution, and starter comparisons.
  4. Detailed report — /app/output/reports/detailed_20260906.html, 349,460 bytes.
  5. Ultra-detailed player audit — /app/output/reports/20260906_ultra_detailed_player_audit.html, 30,202,030 bytes.
  6. Structural audit — /app/output/reports/audit_report_20260906.html, 1,864,642 bytes.
  7. Missing: /app/output/reports/audit_report_20260906_integrity_revision.html, purpose “post-Luna remediation proof for immutable revision artifacts.” Its status is explicitly missing.

Coverage

All 15 expected games were reviewed:

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

Coverage counts are complete for the supplied artifacts:

Gaps and contradictions

2. Executive diagnosis

Winner accuracy

The slate went 9–6, 60.0%, versus a walk-forward baseline of 56.0% and model-validation winner accuracy of 59.6244%. This is a positive result, but only modestly above baseline and not evidence that the score forecasts were reliable.

The winner model was correct in:

ARI@HOU, BOS@BAL, DET@CLE, LAA@PIT, MIN@CHW, OAK@SEA, SF@NYM, STL@COL, and WAS@LAD.

It missed:

ATL@PHI, CHC@MIA, MIL@CIN, NYY@SD, TB@TEX, and TOR@KC.

Calibration quality

Calibration was mixed and materially imperfect:

The published confidence was therefore not uniformly conservative. The lower-confidence bucket was underconfident, but the higher-confidence bucket and high-conviction subset were too aggressive. This supports bounded confidence-cap work, not a blanket conclusion that every probability was overconfident.

Score accuracy

Score accuracy was the principal weakness:

The registered weak_run_model_signal issue is therefore substantiated. The model beat average guessing, but its exact run estimates and tails were weak. The small positive R² must not be interpreted as reliable score prediction.

Starter accuracy

Starter projections were highly variable. Identity matching was successful for all listed starters, but actual earned runs often diverged materially from projection. Examples include:

The lever-tension receipt records the pitcher-weighting lever as helping 10 games and hurting 2. That is useful directional evidence, but not a controlled causal result. Cross-slate evidence does not support changing context.opponent_strength_weight: starter ERA error has the same sign on only 4 of 7 measured slates, with z = 0.65.

Artifact integrity

Artifact integrity was strong for the delivered slate:

The missing integrity-revision audit remains a documentation gap. It does not invalidate the supplied structural passes, but it prevents a fully closed artifact chain.

Causal issue register reconciliation

High: weak_run_model_signal

Info: complete_slate_audit_coverage

Info: probability_publication_delta_explained

Info: simulation_inert_on_slate

3. Every game

Conventions: Published probability is the probability of the published side, while the raw field published_pick_probability is the home probability. “Edge” is home minus away. Team-run error is the absolute team-run error. Total bias is actual total minus predicted total; positive means the model underpredicted total runs.

All player actuals were unavailable because the slate player feed had no rows.

ARI@HOU — correct winner, wrong score

ATL@PHI — wrong winner

BOS@BAL — correct winner, wrong score

CHC@MIA — wrong winner and major score miss

DET@CLE — correct winner, wrong score

LAA@PIT — correct winner, wrong score

MIL@CIN — wrong winner and severe total miss

MIN@CHW — correct winner, wrong score

NYY@SD — wrong winner

OAK@SEA — correct winner, very wrong score

SF@NYM — correct winner, wrong score

STL@COL — correct winner, wrong score

TB@TEX — wrong winner and total miss

TOR@KC — wrong winner and score

WAS@LAD — correct winner, wrong score

4. Miss reconstruction

Earliest wrong-direction evidence for each loss

ATL@PHI

CHC@MIA

MIL@CIN

NYY@SD

TB@TEX

TOR@KC

Pipeline-stage quality across all stages

StageWinner accuracyTeam-run MAETotal-run MAEMargin MAEInterpretation
historical_ml8/15 = 53.33%2.67624.64542.4455Baseline
variance_applied8/15 = 53.33%2.66674.80002.2667Margin improved; total error worsened
enhanced_prediction9/15 = 60.00%2.70004.20002.7333Winner accuracy improved, but margin error regressed versus baseline
embedded_savant_run_environment9/152.66674.13332.6667Small score recovery
fundamental_edge_target_review9/152.66674.13332.6667No change
capped_target9/152.66674.13332.6667No change
simulation_result9/152.66674.13332.6667No change
published_final9/152.66674.13332.6667No change

Important transitions:

A later recovery does not erase an intermediate winner-direction regression. In particular, enhanced prediction improved the aggregate hit count but still introduced or preserved wrong-direction states in ATL@PHI, CHC@MIA, NYY@SD, TOR@KC, and WAS@LAD transitions as documented by the transition receipt.

5. Cross-game counterfactuals

Lever: widen run distributions

Lever: score.variance_multiplier / score.variance_floor

Lever: pitcher form weights / prior games

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

Lever: recent/season run-mean weighting

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

Tempting fixes that must not be made

6. Data and contract defects

Critical, error, warning, and info findings

Across the structural audit:

Every per-game audit reported PASS, with zero defects and zero warnings. Thus, there were no supplied structural contract failures that explain the misses.

The major non-structural defects are:

  1. Missing integrity-revision audit artifact — presentation/provenance gap.
  2. Empty player feed — data-coverage gap affecting causal player attribution.
  3. Simulation functional inertness — likely code/process defect, established across 10 slates.
  4. Near-zero run-model signal — model/data/feature-contract defect, established across 10 slates.
  5. Probability-lineage wording inconsistency — artifact/presentation defect for four small deltas.

Model defects versus artifact bugs

Prediction-model/process defects

Presentation/artifact defects

These should not be conflated: clean structural artifacts do not imply a strong predictive model.

Probability-lineage audit

The required layers are raw model → calibrated → governor → score coherence/recency → published.

Examples:

For the eight material movements identified in the causal register, a named transformation is present. No material governor bypass is demonstrated.

However, ARI@HOU, ATL@PHI, LAA@PIT, and OAK@SEA have small publication deltas and text stating that no transformation explains them. Because their unexplained_material_delta flags are false, the likely intended interpretation is that the deltas are below materiality. The lineage contract should record the exact transformation or explicitly mark them as nonmaterial rounding/serialization differences.

7. Cross-slate persistence

The raw structural and trend evidence contains both persistent signals and nonpersistent noise.

Finding streaks

FindingConsecutive-slate countPresent now?Interpretation
high_raw_probability_cluster0No3 incidences in 10 slates, not consecutive
pipeline_winner_instability0No4 incidences in 10 slates, not currently present
score_margin_compression0No3 incidences in 10 slates, not currently present
simulation_inert_on_slate10YesEstablished persistent failure
single_slate_calibration_instability0No5 incidences in 10 slates, but no current streak
weak_run_model_signal10YesEstablished persistent failure

The two ten-slate findings must be treated as established failures, not single-slate noise.

Escalated findings

simulation_inert_on_slate

The self-assessment identifies the likely mechanism: target-realization draws are reused as the win-probability distribution, and the loop exits early after finding a play-by-play realization. A win rate based on approximately two selected draws is not a probability.

weak_run_model_signal

The register marks this as not parameter-actionable despite listing training parameters. That means the listed parameters are candidate experiment controls, not a justified live change.

Metric-trend directions

All requested directions:

Improving trend labels do not erase the persistent run-model and simulation failures.

8. Adjustments for today

Recommendations are ranked by persistence and scope.

1. Simulation code/diagnostic repair — strongest persistent action

2. Run-model feature/target backtest — persistent model failure

3. Bounded confidence/variance shadow experiment — strongest single-slate driver

Changes explicitly not recommended today

9. Bottom line

Known:

Uncertain:

Safest next action: repair and instrument the simulation distribution in shadow mode, using an independent sufficiently large draw batch and a rollback monitor. This addresses the strongest persistent process failure without forcing an unvalidated live parameter change, while preserving the ability to measure whether the simulation actually improves probability calibration, winner accuracy, and run-error metrics on the next slate.