Luna deep analysis — slate 20260905

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

1. Evidence receipt and gaps

Sources received

All seven source_manifest entries were reviewed:

  1. Prediction review — loaded; 376,581 bytes; official outcomes and scoring errors.
  2. Forensic deep audit — loaded; 241,224 bytes; probability, provenance, starter, and decision contracts.
  3. Continuous learning — loaded; 2,499,160 bytes; stage quality, calibration, probability lineage, score distribution, and starter comparisons.
  4. Detailed report — loaded; 355,886 bytes; full game and simulation rendering.
  5. Ultra-detailed player audit — loaded; 30,881,727 bytes; player-level prediction trace.
  6. Structural audit — loaded; 1,848,251 bytes; invariant findings.
  7. Integrity revision audit — missing; path /app/output/reports/audit_report_20260905_integrity_revision.html; intended to provide post-remediation proof for immutable revision artifacts.

Slate coverage

The evidence reports:

The 15 reviewed games were:

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, WAS@LAD.

Gaps and contradictions


2. Executive diagnosis

Overall result

The slate achieved:

A correct winner does not imply a good prediction. For example:

Winner accuracy

Winner performance was weak:

Calibration quality

Calibration was mixed rather than uniformly defective:

Score accuracy

Score prediction is the clearest persistent model weakness:

Starter accuracy

Starter projections were a mixed contributor:

Artifact integrity

Structural artifact integrity was strong for the loaded game artifacts:

Causal issue register reconciliation

Critical: unexplained probability publication delta

The evidence confirms the deltas:

High: intermediate winner instability

High: weak run-model signal

Medium: high raw probability cluster

Informational: complete slate audit coverage

Informational: simulation inert on slate


3. Every game

The listed probability is the published probability of the selected side. The confidence edge is the absolute published-side edge from 50%; the raw signed home-minus-away edge is also shown where useful.

ARI@HOU — correct winner, wrong score

ATL@PHI — miss

BOS@BAL — correct winner, wrong score

CHC@MIA — correct winner and strong score

DET@CLE — miss

LAA@PIT — miss

MIL@CIN — miss

MIN@CHW — correct winner, wrong score

NYY@SD — correct winner, wrong score

OAK@SEA — miss

SF@NYM — miss

STL@COL — miss

TB@TEX — correct winner, wrong score

TOR@KC — correct winner, wrong score

WAS@LAD — correct winner, wrong score


4. Miss reconstruction

Earliest wrong-direction stage for each loss

ATL@PHI

DET@CLE

LAA@PIT

MIL@CIN

OAK@SEA

SF@NYM

STL@COL

Loss taxonomy

Across the seven losses:

A published home-away confidence edge of 0.12 is moderate, not a near coin flip. The system’s confidence labels correctly distinguish toss-up, lean, moderate, and strong; a 0.11–0.12 edge should not be treated as negligible.

Pipeline-stage audit across all stages

StageWinner accuracyHitsTeam-run MAEMargin MAEAssessment
historical_ml53.33%81.87293.0583Baseline
variance_applied33.33%51.83333.0000Winner-direction regression
enhanced_prediction53.33%81.96673.2667Recovered winners, worsened run metrics
embedded_savant_run_environment53.33%82.00003.3333Further run-model regression
fundamental_edge_target_review53.33%82.00003.3333No winner recovery
capped_target53.33%82.00003.3333No change
simulation_result53.33%82.00003.3333No change
published_final53.33%82.00003.3333No change

Transitions


5. Cross-game counterfactuals

Lever tension: widen run distributions

Lever: score.variance_multiplier / score.variance_floor.

Helps

Hurts

Net evidence

Lever tension: pitcher form weights / prior games

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

Helps

Hurts

Net evidence

Lever tension: recent/season run-mean weighting

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

Helps

Hurts

Net evidence

Tempting one-game fixes that should not be made


6. Data and contract defects

Critical findings

  1. Unexplained probability publication delta
  2. ATL@PHI: +3.2979 pp.
  3. LAA@PIT: -2.3371 pp.
  4. WAS@LAD: -4.8469 pp.
  5. Required action: block promotion until each transformation is recorded and reconciled.
  1. Missing integrity revision audit
  2. The manifest explicitly marks the integrity revision audit as missing.
  3. This is a source-receipt gap, even though the loaded structural audits passed.

Error findings

Warning findings

Informational findings

Prediction-model defects versus artifact bugs

Prediction-model/process defects

Presentation/artifact/contract defects

Coverage reconciliation

The coverage matrix says the slate is fully covered:

Therefore, the slate is coverage-complete but not contract-clean. Full coverage does not permit calling the slate clean because three probability-lineage defects remain.

Complete pick-side probability lineage

The expected path is:

raw model → calibrated → governor → score coherence/recency → published.

Material examples:

The evidence supports calling a material undocumented transformation, not asserting a governor bypass without further math tracing.


7. Cross-slate persistence

The trend window contains nine slates: 2026-08-28 through 2026-09-05, with eight prior slates loaded.

Finding streaks

Escalated findings

Simulation inertness

The self-assessment identifies a likely root cause: the simulation uses draws selected while searching for a target-realizing play-by-play, exits early with roughly two draws, and then treats those selected draws as a probability distribution. That makes the win-rate estimate vacuous.

Weak run-model signal

The self-assessment recommends adding, where legitimately available:

then retraining under a new model schema version and comparing same-fingerprint holdout R².

Metric trends

The top-confidence pick has had intermittent misses but no current consecutive-loss streak.


8. Adjustments for today

Recommendations are ranked by persistence, scope, expected metric effect, and regression risk.

1. Fix and independently validate the simulation path — highest evidence strength

2. Run the persistent run-model feature/target backtest — high evidence strength

3. Shadow a small confidence-cap reduction for the current high-raw cluster — lower evidence strength

No direct starter-weight change is recommended today: the pitcher lever is 5–5 in cross-game tension, and the evidence does not support a net direction.


9. Bottom line

Known

Uncertain

Single safest next action

Run the operator-level simulation diagnostic and contract reconciliation before promoting another slate: independently verify that the simulation executes with an unsteered probability batch, and trace every calibrated-to-published probability transformation for ATL@PHI, LAA@PIT, and WAS@LAD. This is safer than tuning scores or confidence because it addresses an established code/process failure and the registered critical publication defects without weakening the proven strong call in CHC@MIA.