/getting-started/index.html Start here to understand the repo model, the workflow, and the first command path for a migrated market. Hugo en-gb /getting-started/quickstart/index.html Mon, 01 Jan 0001 00:00:00 +0000 /getting-started/quickstart/index.html This is the shortest supported path for using the repo. Preconditions Run commands from the repository root. Have R available locally. Install the minimal repo dependency used by validation: install.packages("yaml") Create A New Market/KPI Rscript scripts/scaffold_market.R IT store_visits This creates: /getting-started/getting-started/index.html Mon, 01 Jan 0001 00:00:00 +0000 /getting-started/getting-started/index.html This repo is for market-specific implementations that sit on top of the shared product/package layer in forecast-mmmapi-r. Run all commands from the repository root. Typical Workflow Create or update a market/KPI folder under markets/. Keep market-specific logic in bounded files such as transform.R and decomp.R. Run validation locally. Open a pull request for product/engineering review. Build the upload artefact from the repo version, not from a local copy. Standard Commands Validate all migrated markets: /getting-started/repo-model/index.html Mon, 01 Jan 0001 00:00:00 +0000 /getting-started/repo-model/index.html This repository is intentionally separate from forecast-mmmapi-r. Split Of Responsibility forecast-mmmapi-r reusable package/product code API contract packaging logic shared templates and helpers forecast-mmmapi-markets market/KPI implementations market configuration bounded transform/decomp logic validation entrypoints build manifests and governance Why Split Repos Without this split, the reusable product repo tends to become a hybrid of: