Config Reference
Each market/KPI folder must define a config.yml.
Example
Required Top-Level Keys
market_codekpiownerweek_startartifact_namemodelmappinginputsdecompvalidation
Field Notes
market_code
- short market identifier, for example
CN,IT,UK
kpi
- KPI folder name and logical build target
owner
- named analyst or market owner
week_start
1for Monday7for Sunday
artifact_name
- human-readable artefact stem used by build logic
model.source
- where the model object comes from
- current scaffold assumes an external RDS-style source, but this can evolve
model.path
- explicit path to the model artefact used by the market
model.object_path
- object name or object-path identifier within the artefact
model.api_model_policy
- expected consistency rule for predict/decomp
model.update_strategy
- how model updates are handled, for example explicit replacement or inherited
mapping
- where the mapping table comes from
inputs.raw_data
- explicit market input artefact used by transform
inputs.fixed_forecast
- fixed forecast input if applicable
decomp.*
- market-specific decomp regex or configuration
validation.*
- switches describing required validation behaviour
Current Limitation
The current repo validates config shape and week-start values. It does not yet validate a full schema of allowed values for every nested field.