<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reference — DSAMbayes Backtest Documentation</title>
    <link>/reference/index.html</link>
    <description>Reference material for the current data contract, CLI surface, metrics, and result artifacts.</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="/reference/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Data Contract</title>
      <link>/reference/data-contract/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/reference/data-contract/index.html</guid>
      <description>The backtest harness needs enough information to replay the same model surface consistently across folds and across repos.&#xA;Minimum Required Inputs For a runnable pilot manifest, the repo needs:&#xA;a weekly source table a date column a KPI / response column the locked model formula priors boundaries repo targets and repo paths fit settings and seed policy If recommendation stability is in scope, the repo also needs:</description>
    </item>
    <item>
      <title>Results And Artifacts</title>
      <link>/reference/results-and-artifacts/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/reference/results-and-artifacts/index.html</guid>
      <description>Backtest outputs are written under run-scoped result trees so filtered reruns do not overwrite earlier summaries.&#xA;Result Tree Shape Typical layout:&#xA;results.../ &lt;dataset_id&gt;/ &lt;comparison_label&gt;/ run_id=.../ experiment_manifest.yaml fold_manifest.csv summary/ run_status.csv holdout_scores.csv holdout_summary.csv parameter_stability_summary.csv recommendation_stability_summary.csv repo_target=&lt;repo&gt;/ fold_id=01/ run_manifest.yaml run_status.json fit_payload.rds prediction_payload.rds holdout_scores.csv recommendations.csv stability/ parameter_drift.csv parameter_drift_summary.csv recommendation_drift.csv recommendation_drift_summary.csv Most Important Summary Files summary/run_status.csv Fold-by-fold execution state.</description>
    </item>
    <item>
      <title>CLI Reference</title>
      <link>/reference/cli/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/reference/cli/index.html</guid>
      <description>The main entrypoint is:&#xA;Rscript scripts/dsambayes-backtest.R &lt;command&gt; [options] validate Validate a pilot manifest and print the planned run scope.&#xA;Rscript scripts/dsambayes-backtest.R validate \ --manifest .planning/research/pilot_manifest.yaml plan Build the run matrix for the active manifest.&#xA;Rscript scripts/dsambayes-backtest.R plan \ --manifest .planning/research/pilot_manifest.yaml run Execute a batch or write a dry-run result tree.</description>
    </item>
    <item>
      <title>Metrics Reference</title>
      <link>/reference/metrics/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/reference/metrics/index.html</guid>
      <description>Forward Holdout Metrics RMSE Root mean squared error on the observed KPI scale.&#xA;WMAPE Weighted mean absolute percentage error on the observed KPI scale.&#xA;Mean error Signed bias on the observed KPI scale.&#xA;SMAPE Secondary holdout metric on the observed KPI scale.&#xA;Holdout ELPD / log score Secondary probabilistic diagnostics when compatible posterior outputs are available.</description>
    </item>
  </channel>
</rss>