<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Standards — forecast-mmmapi-markets Documentation</title>
    <link>/standards/index.html</link>
    <description>Document modelling and implementation standards that every market integration must satisfy.</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="/standards/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Model Consistency</title>
      <link>/standards/model-consistency/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/standards/model-consistency/index.html</guid>
      <description>One of the main failure modes this repo is designed to prevent is inconsistency between:&#xA;transform output model object used for predict model/decomp logic used for contribution outputs Rule For a given market/KPI build, transform, predict, and decomp must refer to the same intended model representation.&#xA;What This Means In Practice If a model is rewritten for forecast/upload purposes, for example by replacing an inline combined term with an explicit single variable, then:</description>
    </item>
  </channel>
</rss>