feat: tie calibration artefact sets to configs via provenance stamps#18
Merged
koen-vg merged 1 commit intoJul 1, 2026
Merged
Conversation
Calibration artefacts now live in per-config sets under
data/curated/calibration/<source>/, selected by the new
calibration.source config key (a {calibration_source} placeholder in
artefact paths, resolved at config-load time). Each set carries a
provenance.yaml stamp of the structural config it was calibrated
against; every workflow run checks its config against the stamp of the
set it consumes and errors on structural mismatch.
calibration.accept_provenance_mismatch downgrades the error to a
warning for configs where calibration fidelity is irrelevant (test,
tutorials).
tools/calibrate gains --base <config> to calibrate a dedicated set for
a structurally divergent config: the base must declare its own
calibration.source, a fresh set is seeded from the default set, the
chain runs under name=calibration-<source> to keep processing trees
separate, and the set is (re)stamped after each successful run.
tools/calibrate --check also reports provenance drift.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Calibration artefacts now live in per-config sets under data/curated/calibration//, selected by the new calibration.source config key (a {calibration_source} placeholder in artefact paths, resolved at config-load time). Each set carries a provenance.yaml stamp of the structural config it was calibrated against; every workflow run checks its config against the stamp of the set it consumes and errors on structural mismatch. calibration.accept_provenance_mismatch downgrades the error to a warning for configs where calibration fidelity is irrelevant (test, tutorials).
tools/calibrate gains --base to calibrate a dedicated set for a structurally divergent config: the base must declare its own calibration.source, a fresh set is seeded from the default set, the chain runs under name=calibration- to keep processing trees separate, and the set is (re)stamped after each successful run. tools/calibrate --check also reports provenance drift.