Deep slate report —

Generated 2026-09-29T05:07:38.605107-04:00 · schema deep_slate_diagnosis_v3 · fuses prediction review + forensic deep audit + official starter lines, with a Luna post-mortem.

Process, end to end

1. Settle review
complete
0 games vs official finals
2. Forensic deep audit
incomplete
per-game probability + pitcher impact
3. Deep diagnosis
built
0 losses attributed to a root cause
4. Luna post-mortem
received
9/8 sections; 0/0 games; 2/2 causes; 3/3 sources
5. Adjustment
skipped_open_rollback_monitor
6. Gating
shadow, manual + gated
production champion unchanged

Slate summary

Games
0
Hits
0
Misses
0
Winner accuracy
0%
Mean Brier (losses)
n/a
Mean total-run bias (losses)
n/a

Source coverage receipt

Which reports actually fed the diagnosis. A source shown as missing was not silently assumed.

SourceStatusEvidence suppliedPathBytes
prediction reviewloadedofficial outcomes and scoring errors/app/output/reports/prediction_review_20260928.json4003
forensic deep auditloadedprobability, provenance, starter and decision contracts/app/output/reports/PREDICTION_SYSTEM_DEEP_AUDIT_20260928.json15888
continuous learningloadedpipeline-stage quality, calibration, probability lineage, score distribution, and official starter comparisons/app/output/learning/continuous_learning_daily_20260928.json6809
detailed reportmissingfull game and simulation rendering/app/output/reports/detailed_20260928.htmln/a
ultra detailed player auditmissingplayer-level prediction trace/app/output/reports/20260928_ultra_detailed_player_audit.htmln/a
structural auditmissingall invariant findings/app/output/reports/audit_report_20260928.htmln/a
integrity revision auditmissingpost-Luna remediation proof for immutable revision artifacts/app/output/reports/audit_report_20260928_integrity_revision.htmln/a

High-level causal issue register

Deterministic findings across data integrity, model validation, calibration, score distribution, pipeline stages, simulation, and coverage. Critical is reserved for broken evidence or an unexplained contract violation; high marks material model/process risk. Each row pairs the action to take (Do this) with the wrong conclusion to avoid (Don't conclude).

SeverityDomainFinding and evidenceAffectedAction & guardrail
CRITICALcoverageNot every settled game received structural QA
0/0 games structurally audited
slate-wide
Do thisDo not call the slate clean; run per-game QA on every canonical artifact first.
Don't concludeA clean subset of games cannot certify the games that were never audited.
INFOsimulationSimulation produced no winner-direction intervention on this slate
flip candidates 0; published flips 0
slate-wide
Do thisMeasure the simulation's contribution across rolling slates, separating score realization from winner flipping.
Don't concludeZero winner flips is not a defect and does not mean the simulation did no score-reconciliation work.

Cross-slate trends (persistent-pattern memory)

Window: 20260918, 20260919, 20260920, 20260921, 20260922, 20260923, 20260924, 20260925, 20260926, 20260927, (10 prior slates loaded). Highest-confidence pick loss streak: 0 slate(s). Actionable pattern detected.

Escalated persistent patterns

A finding that has repeated at or beyond the escalation streak is no longer single-slate noise. It carries its target registered lever and an action-oriented guardrail.

FindingPersistenceTarget lever(s)DirectionGuardrail
simulation_inert_on_slate11 consecutive · 11 in windowsimulation.allow_scoreconfirm the simulation module is running, not silently no-opingsimulation_inert_on_slate has persisted 11 consecutive slates; this is no longer single-slate noise. Treat it as an actionable pattern and raise the code/diagnostic action named; do not force a parameter move.

Finding streaks across the window

FindingConsecutive slatesIncidencePresent nowFix type
high_raw_probability_cluster02/11noparam
pipeline_winner_instability06/11nocode/diagnostic
score_margin_compression02/11noparam
simulation_inert_on_slate1111/11yescode/diagnostic
single_slate_calibration_instability06/11noparam
weak_run_model_signal010/11nocode/diagnostic

Metric direction across the window

MetricDirectionSeries (old → new)
winner_accuracyimproving[0.6667, 0.7333, 0.6, 0.3333, 0.4, 0.5, 0.6667, 0.6471, 0.5385, 0.6429, None]
weighted_calibration_errorimproving[0.1247, 0.3458, 0.3184, 0.2028, 0.1881, 0.1108, 0.1701, 0.1302, 0.1524, 0.1031, None]
margin_biasimproving[-2.0, -0.667, -1.533, -2.667, -1.867, -1.188, -1.083, -1.706, -3.0, -1.571, None]
team_run_error_on_lossesimproving[5.2, 6.5, 6.5, 3.0, 6.222, 5.75, 3.5, 5.333, 6.167, 4.8, None]

Pipeline stage regression

Every stored stage is scored against the same official finals. A later recovery remains visible; it does not erase an unstable intermediate flip.

Pitcher versus batter: patterns across the whole slate

Not computed for this slate. no game carried a matchup breakdown. The per-player feed (data/all_players_stats.csv) is refreshed on its own schedule and regularly lands after official finals, so a slate reviewed promptly can be published before its player box exists.

Once the feed carries the slate, rebuild it offline with python -m services.forensics_backfill. The nightly cycle runs the same sweep at the start of every run, so this repairs itself on the next cycle.

Trained winner blend: does it reach the published number?

no game artifacts supplied

Repeated bias across slates, and the lever that moves it

A bias on one slate is noise. The same sign across slates, large relative to how much it moves between them, is a model defect. Only the ones that pass both tests are turned into a named parameter change; the rest are held deliberately.

starter ERA error (actual minus projected)

Mean 0.44 over 12 slates (sign shared by 0.58 of them, z = 0.69).

starters were hit harder than projected: the run model under-credits opposing offenses.

Hold: no change: this bias is not separable from slate-to-slate noise yet

7 of 12 slates share the sign, mean 0.44 +/- 0.64 standard error: not separable from noise

lineup runs actual minus projected

Mean -0.24 over 12 slates (sign shared by 0.67 of them, z = -1.46).

lineups scored below projection: the run environment is set too high.

Hold: no change: this bias is not separable from slate-to-slate noise yet

8 of 12 slates share the sign, mean -0.25 +/- 0.17 standard error: not separable from noise

SlateGamesWinner accMean starter ERA errorMean lineup runs vs projSides broke on pitchingSides broke on offense
20260927140.643-4.850.1713
20260926130.5380.550.6934
20260925170.6471.130.50810
20260924120.6671.68-0.67411
20260923160.500-0.49-0.91411
20260922150.400-0.32-0.97311
2026092130.333-1.08-0.50
20260920150.600-0.89-1.00210
20260919150.7331.36-0.1087
20260918150.6673.950.3065
2026091790.4442.16-0.2223
20260916150.6672.09-0.2345

Per-game evidence coverage

Expected games
0
Artifacts loaded
0
Structural audits
0
Deep-audit games
0
Learning rows
0
Starter comparisons
0

Every game, in depth (0)

Cross-game lever tension

Each candidate fix, and exactly which games it would help versus hurt. A lever that repairs one game and breaks two is visible here before it is proposed.

score.variance_multiplier / score.variance_floor (widen run distributions)

Targets: brier_score, calibration_error · 0 helped vs 0 hurt
Would help
  • none
Would hurt / risk
  • none

player.pitcher.v4 form weights / player.pitcher_prior_games

Targets: starter_er_mae, starter_outs_mae · 0 helped vs 0 hurt
Would help
  • none
Would hurt / risk
  • none

recent.* / season.* run-mean weighting

Targets: team_run_mae, total_run_mae, accuracy · 0 helped vs 0 hurt
Would help
  • none
Would hurt / risk
  • none

Day over day: did it improve or worsen

Compared against packet 20260927. Last recorded change: v4.30.0 (2026-09-08) Hitter shrinkage is derived from the between-hitter spread rather than fitted to slate error, so an established extreme profile is no longer flattened toward the league.

MetricPriorCurrentΔResult
brier_score0.24620.2462+0flat
accuracy0.57260.5726+0flat
team_run_mae2.56842.5684+0flat
total_run_mae3.80343.8034+0flat
calibration_error0.08620.0862+0flat
starter_er_mae1.79651.7965+0flat
starter_outs_mae4.04424.0442+0flat

The adjustment the system made in response

Status: skipped open rollback monitor.

Luna deep post-mortem (full)

1. Evidence receipt and gaps

Source manifest

All eight manifest entries were reviewed as untrusted evidence metadata:

SourceStatusEvidence
Prediction reviewLoaded4,003 bytes; intended to contain official outcomes and scoring errors
Forensic deep auditLoaded15,888 bytes; intended to contain probability, provenance, starter, and decision contracts
Continuous learningLoaded6,809 bytes; intended to contain stage quality, calibration, lineage, score distribution, and starter comparisons
Detailed reportMissing/app/output/reports/detailed_20260928.html
Ultra-detailed player auditMissing/app/output/reports/20260928_ultra_detailed_player_audit.html
Structural auditMissing/app/output/reports/audit_report_20260928.html
Integrity revision auditMissing/app/output/reports/audit_report_20260928_integrity_revision.html
Game and slate coverage

No games were supplied:

Thus, there is no game-level evidence from which to calculate winner accuracy, Brier score, run error, starter error, or score-path accuracy.

Internal contradictions and gaps
  1. The slate is marked learning-eligible despite no game artifacts.

learning_eligibility.eligible is true with the reason that all artifacts passed structural gates, but the coverage matrix says zero canonical artifacts were loaded and zero games were audited. This is a contract inconsistency.

  1. The slate is effectively empty but carries a normal-looking diagnosis.

self_assessment.headline is "nominal", while needs_operator_action is true, operator_action_count is 1, and the causal register contains a critical coverage failure. “Nominal” should not be used for an unevaluated slate.

  1. The manifest is incomplete for the required forensic scope.

Four reports are missing, including the structural and integrity-revision audits. The available JSON explicitly says that player-level forensics, matchup breakdowns, probability reversions, and game artifacts are unavailable.

  1. The cross-slate window contains a blank date.

window_dates includes "", and the final per_slate top-pick record also has an empty date with result "unknown". This should be treated as a data-quality defect in the trend window.

  1. Current-slate learning metrics are absent.

Calibration has zero settled games; pipeline stages and transitions are empty; margin distribution is empty; high-raw-cluster count is zero; probability lineage is empty. These zeros mean “not measured,” not “no problem.”

---

2. Executive diagnosis

Winner accuracy

No current-slate winner accuracy is measurable:

The cross-slate metric is reported as directionally improving, with mean winner accuracy 0.5729, and the series includes values from 0.3333 to 0.7333. That is historical context only; it does not validate this empty slate.

Calibration quality

No current-slate calibration assessment is possible:

The cross-slate weighted calibration error is listed as 0.1846 and marked “improving,” but no current-slate probabilities exist. A correct or unavailable winner result cannot be treated as calibrated.

Score accuracy

No score or run accuracy is measurable:

The historical margin_bias is marked improving, with mean -1.7282, but it remains a cross-slate trend rather than current-slate evidence.

Starter accuracy

No starter comparisons were supplied:

The cross-slate starter ERA-error finding has mean 0.441, with the same sign on 7 of 12 slates, but it is explicitly marked nonpersistent and held. No parameter change is justified from this slate.

Artifact and contract integrity

Artifact integrity is not clean despite structural_audit_summary showing zero critical, error, info, and warning findings. That summary reflects no completed structural audit, not a successful audit.

The strongest integrity findings are:

Causal issue register reconciliation
incomplete_slate_audit_coverage

This is a genuine evidence/contract failure. Critical is appropriate because the system cannot establish what was predicted or whether the artifacts are internally consistent.

simulation_inert_on_slate

Its current-register severity is only informational, but the cross-slate section escalates it to an established 11-slate pattern requiring operator action.

---

3. Every game

There are no game records to review. Therefore, there are no hits, misses, or correct-winner/wrong-score cases.

The requested game-level fields are all unavailable:

Accordingly, no game should be labeled a hit, miss, correct-winner/wrong-score result, starter failure, offense failure, bullpen failure, or irreducible-variance event.

---

4. Miss reconstruction

Current-slate losses

There are no current-slate losses to reconstruct:

It would be invalid to attribute any loss to bad inputs, weighting, calibration, starter error, offense, bullpen, run environment, or variance.

The explicit guardrail concerning a 0.12 home-away confidence edge is also relevant: if such an edge had appeared in a game artifact, it would be moderate—not a near coin flip. No such current-game edge was provided here.

Earliest wrong-direction stage

No earliest wrong-direction stage can be identified because:

A later recovery cannot erase an intermediate winner-direction regression, but there is no evidence here that any transition occurred.

Pipeline-stage audit across all stages and transitions

The audit result is:

Therefore:

The empty stage table is a measurement failure, not proof that the pipeline behaved correctly.

---

5. Cross-game counterfactuals

All three lever_tension entries have zero observed affected games.

Run-distribution widening

Cross-slate evidence does show a historical score_margin_compression finding twice in an 11-slate window, but it is not present on this slate and is not escalated. A bounded shadow test may be reasonable only after restoring measurement, not as a production move based on this empty slate.

Pitcher form and prior-game weighting

The cross-slate starter ERA signal is explicitly held because it is not separable from noise: mean 0.441, z-score 0.69, same sign on 7/12 slates.

Recent versus season run-mean weighting

Cross-slate lineup run delta is negative on 8/12 slates, with mean -0.245 and z-score -1.46, but the register marks it nonpersistent and recommends holding. It should not be converted into a one-game production adjustment.

Tempting one-game fixes that must not be made

Do not:

  1. Lower confidence caps based on an empty current slate.
  2. Widen score variance based on the historical margin-compression finding alone.
  3. Change pitcher-form weights without starter-level evidence.
  4. Change recent/season run weighting based on the historical negative lineup delta.
  5. Treat zero simulation winner flips as evidence that simulation should force winner changes.
  6. Mark the slate clean because structural-audit counts are zero.
  7. Treat the blank current date as a valid completed daily observation.

---

6. Data and contract defects

Audit findings by severity
Critical
  1. Incomplete slate audit coverage
Error

No findings are reported in structural_audit_summary, but this is not evidence that no errors exist. The structural audit report itself is missing, and zero artifacts were loaded.

Warning

No warnings are reported in the summary. Again, the absence is not probative because the audit was not executed over any current-game artifacts.

Info
  1. Simulation produced no winner-direction intervention
Prediction-model defects versus presentation/artifact defects
Prediction-model or pipeline risks
Presentation and artifact defects
Probability-lineage audit

The required lineage is:

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

The supplied probability_lineage is empty. Therefore:

A material bypass cannot be called because there is no lineage to compare. The correct finding is lineage unavailable, not “bypass confirmed.”

Coverage matrix reconciliation

The coverage matrix is not slate-clean:

The combination of zero expected games and a blank date appears to represent a missing or uninstantiated slate, not a completed slate with zero defects. The eligibility flag should be blocked until that distinction is resolved.

---

7. Cross-slate persistence

Raw structural blocks
Margin distribution

No current-slate margin evidence exists.

Pipeline stage quality

No cross-stage current-slate conclusion is possible.

Calibration monitoring

No current-slate calibration conclusion is possible.

High-raw-probability cluster

No current-slate high-confidence cluster exists in the supplied evidence.

Simulation control

This current-slate non-observation is reinforced by the persistent cross-slate finding below.

Finding streaks
FindingConsecutive-slate countPresent now?Interpretation
high_raw_probability_cluster0NoOccurred on 2 of 11 window slates; not currently present
pipeline_winner_instability0NoOccurred on 6 of 11; not currently present
score_margin_compression0NoOccurred on 2 of 11; not currently present
simulation_inert_on_slate11YesEstablished persistent failure pattern
single_slate_calibration_instability0NoOccurred on 6 of 11; not currently present
weak_run_model_signal0NoOccurred on 10 of 11; not currently present as a streak

The simulation_inert_on_slate finding is escalated and must not be treated as single-slate noise.

Escalated finding
Simulation inertness

The self-assessment gives the proposed implementation direction:

Metric-trend directions

The supplied trend directions are:

These “improving” labels do not overcome the fact that the current slate has no settled games and no measurable current-slate metrics.

Top-confidence-pick loss streak

Therefore, the top-confidence pick does not show a current persistent loss streak in the supplied data. Its historical sequence includes misses but does not establish a consecutive loss streak.

---

8. Adjustments for today

Recommendations are ranked by evidence strength and constrained to registered levers.

1. Persistent pattern: repair and instrument simulation before tuning it
2. Strongest current-slate driver: restore evidence coverage

There is no valid game-level model driver because the slate contains zero games. The strongest current operational driver is therefore the coverage/contract failure.

3. Do not tune held cross-slate parameters today

No bounded production adjustment is justified for:

The relevant findings are either nonpersistent, absent on the current slate, or unmeasurable due to missing games. A shadow experiment can be planned after artifact coverage is restored, but no live move is supported today.

---

9. Bottom line

Known
Uncertain
Single safest next action

Restore and validate the canonical per-game artifact set, then block learning and “nominal” reporting until every expected game passes structural QA and probability-lineage checks. In parallel, open the operator-level simulation diagnostic for the persistent 11-slate inertness finding, but do not promote a parameter change without an independently sampled, measurable simulation output.