Luna deep analysis — slate 20261002

Coverage receipt: COMPLETE · 9/8 sections; 0/0 games; 2/2 causes; 3/3 sources

1. Evidence receipt and gaps

Source manifest

All manifest entries were checked against the supplied JSON:

SourceStatusPurposeAssessment
/app/output/reports/prediction_review_20261002.jsonLoaded, 4,003 bytesOfficial outcomes and scoring errorsPresent in manifest, but no game records were propagated into this diagnosis
/app/output/reports/PREDICTION_SYSTEM_DEEP_AUDIT_20261002.jsonLoaded, 15,888 bytesProbability, provenance, starter, and decision contractsPresent in manifest, but no per-game audit rows are present here
/app/output/learning/continuous_learning_daily_20261002.jsonLoaded, 6,809 bytesPipeline-stage quality, calibration, probability lineage, score distribution, and starter comparisonsPresent, but all current-slate game-dependent structures are empty
/app/output/reports/detailed_20261002.htmlMissingFull game and simulation renderingGap
/app/output/reports/20261002_ultra_detailed_player_audit.htmlMissingPlayer-level prediction traceGap
/app/output/reports/audit_report_20261002.htmlMissingAll invariant findingsGap
/app/output/reports/audit_report_20261002_integrity_revision.htmlMissingPost-remediation immutable revision proofGap

Games reviewed

Material gaps and contradictions

  1. The slate is not auditable despite the learning eligibility flag. learning_eligibility.eligible is true with the reason "all game artifacts passed critical/error structural gates", but the causal register states "0/0 games structurally audited" and explicitly identifies incomplete_slate_audit_coverage as critical.
  1. The audit summary understates the registered critical issue. structural_audit_summary.critical is 0, while causal_issue_register contains a critical issue: incomplete_slate_audit_coverage. This is an internal reporting inconsistency.
  1. The expected slate size is zero, but the report is framed as a daily slate diagnosis. This may reflect a missing or malformed date/game payload, but the evidence does not establish which.
  1. No probability lineage was supplied. probability_lineage: []; probability_reversions.available: false because no game artifacts were supplied.
  1. No pipeline stages or transitions were supplied. pipeline_stage_quality.stages: [] and transitions: [], with status not_measurable.
  1. No current-slate calibration or score metrics are measurable. Calibration buckets are empty; settled games are zero; weighted absolute calibration error is null.
  1. No player or matchup evidence is available. slate_player_metrics.available: false; matchup patterns are unavailable because no game carried a matchup breakdown.
  1. Missing HTML artifacts prevent independent presentation and revision checks. The detailed, player audit, structural audit, and integrity-revision reports are all missing.

2. Executive diagnosis

Winner accuracy

Current-slate winner accuracy is unknown, not zero and not perfect:

The historical cross-slate series reports a mean winner accuracy of 0.6828 and an improving direction, but that is not evidence of current-slate accuracy.

Calibration quality

Current-slate calibration is not measurable:

The cross-slate metric is nevertheless marked regressing, with mean weighted calibration error 0.2276; the series includes 0.4792 and 0.4832. That is a historical trend, not a current-slate result.

Score accuracy

Current-slate score accuracy is not measurable:

The cross-slate margin_bias trend is marked regressing, with mean -2.2683. This indicates a persistent historical margin-direction concern, but no current game can be assigned that error.

Starter accuracy

Starter accuracy is not measurable:

Artifact integrity

Artifact integrity is the most serious current issue.

The causal register contains:

Critical: incomplete_slate_audit_coverage

This is a critical evidence/contract failure, not a model-quality finding.

Informational: simulation_inert_on_slate

However, cross-slate evidence escalates this issue to an established operational pattern; see Sections 7 and 8.

Overall diagnosis

The current slate cannot support a winner, calibration, score, starter, or player-level diagnosis. The primary known failure is missing or unpropagated evidence coverage, not demonstrated predictive failure on particular games. Separately, the simulation-inert behavior is an established cross-slate code/diagnostic concern.

A correct winner, if one had been reported, would not by itself establish a good prediction. No such current-slate winner result exists here.


3. Every game

There are no game records to enumerate.

Accordingly, the requested per-game fields are unavailable for every game:

There are therefore:

The absence of game rows must not be interpreted as a perfect slate, a failed slate, or a slate with no games. It is an evidence-coverage failure.


4. Miss reconstruction

Per-loss reconstruction

No loss can be reconstructed because games is empty and misses: 0 reflects absence of reviewed misses, not verified predictive success.

It is impossible to identify, for any game, whether the earliest wrong-direction movement came from:

No current-slate primary or secondary loss drivers are recorded: loss_primary_drivers: {}.

The confidence guardrail remains important: a 0.12 home-away confidence edge would be moderate, not a near-coin-flip or near-certainty signal. No such current-slate edge is supplied.

Pipeline-stage quality audit

All required stages and transitions are absent:

Therefore:

The historical self-assessment identifies a specific simulation mechanism: selected draws were reportedly reused for win-probability estimation, with early exit after finding a target-realizing play-by-play. The diagnosis says this can leave away_win_rate based on roughly two selected draws, making the flip/agreement signal vacuous. That is a cross-slate implementation hypothesis supported by the stated 11-slate persistence, not a reconstructed event in a current game.


5. Cross-game counterfactuals

The current lever_tension object contains three entries. None has game assignments because there are no current games.

score.variance_multiplier / score.variance_floor

Historical context is mixed: score_margin_compression occurred in 5 of 11 window slates, but its current streak is zero and it is not currently escalated.

player.pitcher.v4 form weights / player.pitcher_prior_games

The cross-slate starter ERA bias is held, not persistent: 6 of 11 slates share the sign, with z -0.42.

recent.* / season.* run-mean weighting

Tempting fixes that should not be made

  1. Do not lower confidence caps based on this slate. No current probabilities, hits, misses, or Brier outcomes exist.
  1. Do not widen score variance based on a presumed current margin miss. No current predicted or actual margins exist.
  1. Do not retune pitcher-form weights. No starter comparisons exist, and the historical starter bias is explicitly nonpersistent.
  1. Do not alter recent/season run weighting. The lever-tension matrix contains no affected games, and the historical lineup-run bias is held as noise.
  1. Do not infer simulation success or failure from zero published flips alone. The causal register explicitly says zero winner flips is not itself proof of a defect, although the 11-slate persistence warrants code diagnosis.

6. Data and contract defects

Critical findings

incomplete_slate_audit_coverage

Error findings

No findings are listed with severity error.

This does not mean the slate is error-free. It means no error-severity rows were supplied.

Warning findings

No findings are listed with severity warning.

Again, this is not evidence of a clean slate because the canonical audit population is empty.

Informational findings

simulation_inert_on_slate

Coverage matrix reconciliation

The coverage matrix is not clean:

The false value for all_games_structurally_audited is decisive. A zero-denominator audit cannot establish complete coverage.

Probability-lineage audit

The required lineage is:

  1. Raw model probability.
  2. Calibrated probability.
  3. Governor/cap adjustment.
  4. Score-coherence and recency adjustment.
  5. Published probability.

The supplied object contains no lineage rows:

Accordingly, no bypass can be formally declared. A bypass requires a material delta between stages with no recorded transformation; there are no stages to compare. The correct finding is lineage absent, not “lineage bypass proven.”


7. Cross-slate persistence

A single slate is absent here, but the supplied historical blocks provide persistence evidence.

Escalated finding

simulation_inert_on_slate

The registered self-assessment gives the proposed code-level remedy:

Finding streaks

FindingConsecutive slatesPresent nowInterpretation
high_raw_probability_cluster0NoOccurred once in the 11-slate window; not persistent
pipeline_winner_instability0NoIncidence 4/11, but no current streak
score_margin_compression0NoIncidence 5/11, not currently present
simulation_inert_on_slate11YesEstablished persistent failure
single_slate_calibration_instability0NoIncidence 6/11, not currently present
weak_run_model_signal0NoIncidence 9/11, but no registered consecutive streak in this object

The escalation_streak: 3 is also present, but the explicit finding-level persistence for simulation is 11 consecutive slates.

Metric trends

Each registered trend is:

These trends must not be conflated. Improving winner accuracy does not cancel regressing calibration or margin bias.

Top-confidence pick loss streak

Raw structural blocks

The cross-slate simulation persistence is therefore the only established actionable pattern in the supplied evidence.


8. Adjustments for today

Recommendations are ranked by evidence strength and operational safety.

1. Highest priority: repair and verify simulation execution

2. Current-slate evidence coverage restoration

3. Single strongest single-slate driver

No current-slate predictive driver can be established because there are no games, scores, probabilities, or losses. The strongest current-slate driver is therefore evidence absence, not offense, pitching, calibration, or variance.

Do not make a confidence-cap, score-variance, pitcher-weight, or recent/season-weight change from this payload. No registered lever is supported by current-slate observations.


9. Bottom line

Known

Uncertain

Single safest next action

Restore and validate complete per-game artifact coverage before changing model parameters: load the canonical game records, run structural QA for every game, and independently verify that the simulation probability path executes rather than early-exiting. Do not promote any confidence, variance, pitcher, or run-weight adjustment until that evidence exists.