/reference/index.html Lookup documentation for the CLI, YAML schema, manifest schema, output layout, and related contracts. Hugo en-gb /reference/cli/index.html Mon, 01 Jan 0001 00:00:00 +0000 /reference/cli/index.html `meridian-tools` provides a command-line interface with two subcommands: `run` and `demo`. /reference/yaml-schema/index.html Mon, 01 Jan 0001 00:00:00 +0000 /reference/yaml-schema/index.html This is the complete field-level reference for `meridian-tools` YAML configuration files. For usage guidance, see the [configuration guide](../guides/configuration). /reference/manifest-schema/index.html Mon, 01 Jan 0001 00:00:00 +0000 /reference/manifest-schema/index.html The `run_manifest.json` file is the source of truth for every `meridian-tools` run. It lives at the root of the run directory and records identity, timing, versions, overall status, top-level artefact index, and per-stage records. /reference/output-schema/index.html Mon, 01 Jan 0001 00:00:00 +0000 /reference/output-schema/index.html This page documents the complete run directory layout produced by `meridian-tools`. Every successful pipeline run creates a timestamped directory containing the artefacts described below. /reference/validation-spec-schema/index.html Mon, 01 Jan 0001 00:00:00 +0000 /reference/validation-spec-schema/index.html The `validation_spec.json` artefact is written to `10_validation/` for every validation-aware pipeline run. It records the concrete validation provenance for that specific run, including the holdout strategy, split geometry, and date windows. /reference/api/index.html Mon, 01 Jan 0001 00:00:00 +0000 /reference/api/index.html Public Python APIs exposed by `meridian-tools`.