<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Concepts — meridian-tools documentation</title>
    <link>/concepts/index.html</link>
    <description>Background material on architecture, design decisions, and Meridian integration boundaries.</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="/concepts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Architecture</title>
      <link>/concepts/architecture/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/concepts/architecture/index.html</guid>
      <description>`meridian-tools` is a companion package designed for agency teams that use Google Meridian as their client-facing MMM (Marketing Mix Modelling) engine. It provides a stricter, more reproducible workflow around Meridian without forking the upstream library.</description>
    </item>
    <item>
      <title>Design decisions</title>
      <link>/concepts/design-decisions/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/concepts/design-decisions/index.html</guid>
      <description>This document records the key design decisions in `meridian-tools` and the reasoning behind them. It is intended for maintainers and contributors who need to understand why things are built the way they are.</description>
    </item>
    <item>
      <title>Meridian integration</title>
      <link>/concepts/meridian-integration/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/concepts/meridian-integration/index.html</guid>
      <description>This document describes how `meridian-tools` integrates with Google Meridian, the boundaries of that integration, and the risks associated with different coupling levels.</description>
    </item>
  </channel>
</rss>