Donor Artefact Schemas
donor_eval_results.csv
Each row is a treated-candidate donor pair. Maintained columns include treatment
and donor IDs; composite, fit, correlation, and seasonality scores; design-stage
recommendation weight and role; rank; quality labels; warnings; metric failure
reasons; correlation and its p-value; RMSE, percentage RMSE, MAPE, DTW; and
metrics_complete.
Score normalisation and ranking occur within each treated geography. Cross- treatment score values are therefore not a common absolute scale.
donor_pool_quality.json
The shared JSON persistence contract
applies: nested non-finite metrics become null, supported values are complete,
and unsupported payloads fail explicitly. The JSON file is atomically replaced;
the CSV and JSON pair is not a transaction.
Schema 1.0 records run configuration, an overall summary, and
by_treatment summaries. Summary fields include recommendation counts, quality
distribution, warning and metric-failure counts, weight role, maximum weight,
dominant donor count, effective donor count, score and correlation summaries,
strength score, and quality_assessment.
run_config.adaptive_scoring records scope, treatment_date,
n_observations, outcome_mean, outcome_std (sample standard deviation),
coefficient_of_variation, metric_weights, rmse_thresholds, and
dtw_thresholds. The scope is all_geographies_pre_treatment; each observed row
contributes equally to these statistics. The existing weight branch uses
standard deviation divided by mean, with a value of one when the mean is zero.
These adaptive thresholds are recorded settings, not calibrated acceptance
tests; the separate explicit quality-screen thresholds retain their role.
quality_assessment is a deterministic screening label derived from configured
thresholds. It is not a test of exchangeability and does not guarantee good
SparseSC fit.
run_config.dtw_radius is the fixed approximation search radius (1),
dtw_backend identifies the effective FastDTW callable module, and
dtw_local_cost is absolute_difference. Pair-specific standardisation precedes
approximate alignment and distance is divided by finite overlap count. The
radius does not bound calendar lag. These fields are additive in schema 1.0.