<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Examples — forecast-mmmapi-markets Documentation</title>
    <link>/examples/index.html</link>
    <description>Worked examples that show how the repo structure is applied to real market cases.</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="/examples/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CN Store Visits</title>
      <link>/examples/cn-store-visits/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/examples/cn-store-visits/index.html</guid>
      <description>This is the first worked example and the initial driver for creating this repo.&#xA;Why It Matters The China store visits case exposed several problems that were not just isolated coding mistakes:&#xA;analyst logic was living outside a governed Git workflow local scripts had drifted away from the product-side expectations transform, model, and decomp logic were not clearly aligned date/week conventions introduced market-specific risk Main Lessons One Model Representation If a market updates the variable representation for forecast/upload purposes, then:</description>
    </item>
  </channel>
</rss>