Run an Analysis
Use a YAML config when an analysis should be repeatable and reviewable.
For local repository use:
Conservative default gates
Config runs stop on directional and not_recommended readiness by default, and failed
sampler diagnostics are blocking by default.
Override these only for explicit exploratory work. Record the reason in project.notes
or the downstream analysis review.
Paths
data.tracker and outputs.directory are resolved relative to the config file when
they are not absolute paths.
Reportability
Successful execution does not mean the result is reportable. Always review
run_status.reportable and the supporting artefacts before using pooled summaries.