Review Outputs

Config runs write a compact artefact set intended for analyst review.

First files to open

File Review question
analysis_report.md What is the run status, readiness, and headline result?
run_status.json Is reportable true? Why did the run complete, warn, block, or fail?
readiness.csv How many comparable rows were eligible, and are they enough?
diagnostics.csv Did sampler diagnostics pass configured thresholds?
prior_diagnostics.csv Do priors imply warnings or implausible prior-predictive ranges?
effect_preparation.csv Which rows were included, transformed, excluded, or scenario-based?
ppc.csv Are individual studies out of line with in-sample posterior predictive checks?

Status meanings

run_status.json may report:

  • completed
  • completed_with_warnings
  • blocked
  • failed

A completed run is not automatically reportable. Treat reportable: false as a hard prompt for analyst review before any downstream presentation.

Common reasons a run is not reportable

  • Readiness is directional or not_recommended.
  • Sampler diagnostics failed or were downgraded to warnings.
  • The tracker contains blocking duplicate rows.
  • Prior diagnostics or sensitivity indicate material prior dependence.
  • One or more rows rely on scenario uncertainty.