<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>forecast-mmmapi-markets Documentation</title>
    <link>/index.html</link>
    <description>This documentation explains how forecast-mmmapi-markets is intended to work as the governed market-implementation layer for forecasting/MMM API artefacts.&#xA;Core Pages Quickstart Getting Started Repo Model Market Folder Contract Validation and Build Config Reference Roles and Ownership Validation Contract Build and Release Market README Template Glossary Troubleshooting Example CN Store Visits Standards Model Consistency Purpose This repo exists to stop market implementations drifting into unreviewed local copies on SharePoint or analyst machines. It should be the source of truth for market/KPI logic once a market has been migrated.</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting Started</title>
      <link>/getting-started/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/getting-started/index.html</guid>
      <description>Start here to understand the repo model, the workflow, and the first command path for a migrated market.</description>
    </item>
    <item>
      <title>Market Contract</title>
      <link>/market-contract/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/market-contract/index.html</guid>
      <description>Define the market folder structure, configuration contract, and the minimum documentation each market implementation must carry.</description>
    </item>
    <item>
      <title>Governance</title>
      <link>/governance/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/governance/index.html</guid>
      <description>Clarify ownership boundaries, decision rights, and the review path for market changes.</description>
    </item>
    <item>
      <title>Validation and Release</title>
      <link>/validation-and-release/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/validation-and-release/index.html</guid>
      <description>Capture what validation is enforced, how builds are produced, and how common failures should be diagnosed.</description>
    </item>
    <item>
      <title>Standards</title>
      <link>/standards/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/standards/index.html</guid>
      <description>Document modelling and implementation standards that every market integration must satisfy.</description>
    </item>
    <item>
      <title>Examples</title>
      <link>/examples/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/examples/index.html</guid>
      <description>Worked examples that show how the repo structure is applied to real market cases.</description>
    </item>
    <item>
      <title>Appendices</title>
      <link>/appendices/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/appendices/index.html</guid>
      <description>Reference material that supports the operating model and shared language used across the repo.</description>
    </item>
  </channel>
</rss>