<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Guides — meridian-tools documentation</title>
    <link>/guides/index.html</link>
    <description>Task-oriented workflow documentation for configuration, validation, demos, lifecycle, and troubleshooting.</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="/guides/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Configuration guide</title>
      <link>/guides/configuration/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/guides/configuration/index.html</guid>
      <description>`meridian-tools` is driven by one YAML configuration file. This guide explains every section, its purpose, and its constraints. For a field-level schema reference, see [yaml-schema.md](../reference/yaml-schema).</description>
    </item>
    <item>
      <title>Validation guide</title>
      <link>/guides/validation/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/guides/validation/index.html</guid>
      <description>This guide explains how to choose and configure validation strategies in `meridian-tools`. Validation is the process of evaluating a candidate model specification on held-out data before committing to a final production fit.</description>
    </item>
    <item>
      <title>Model selection guide</title>
      <link>/guides/model-selection/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/guides/model-selection/index.html</guid>
      <description>This guide explains how `meridian-tools` supports Bayesian model selection using Leave-One-Out (LOO) cross-validation and the Watanabe-Akaike Information Criterion (WAIC). It covers when model selection is available, how to interpret the outputs, and how to compare multiple candidate models.</description>
    </item>
    <item>
      <title>Lifecycle management guide</title>
      <link>/guides/lifecycle/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/guides/lifecycle/index.html</guid>
      <description>`meridian-tools` treats completed runs as immutable artefacts. The lifecycle module provides tools to load, compare, and refresh past runs without mutating them. This guide explains each lifecycle operation and when to use it.</description>
    </item>
    <item>
      <title>Meridian Tools workflow guide</title>
      <link>/guides/workflow/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/guides/workflow/index.html</guid>
      <description>This guide shows the supported end-to-end agency workflow for `meridian-tools`. It starts with one YAML config, moves through candidate validation, separates the final full-sample fit from the validation runs, and ends with the artefacts you should hand over or inspect later. The examples in this guide stay inside the implemented package surface. They do not assume notebooks, dashboards, or unpublished helper scripts.</description>
    </item>
    <item>
      <title>Meridian Tools demo guide</title>
      <link>/guides/demos/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/guides/demos/index.html</guid>
      <description>This is the canonical guide to the bundled `meridian-tools` demos. Use it when you want one safe, reproducible, end-to-end example without client data.</description>
    </item>
    <item>
      <title>Troubleshooting</title>
      <link>/guides/troubleshooting/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/guides/troubleshooting/index.html</guid>
      <description>Common issues and solutions when working with `meridian-tools`.</description>
    </item>
  </channel>
</rss>