Emit build provenance in v2 compatibility metadata (bundle 4.16.0)#31
Merged
Conversation
The v2 generation path dropped the build provenance that the legacy certification model carried, leaving importers without it. Carry the release manifest's build_id, built-with model version, git sha, and data build fingerprint into the compatibility assertion metadata and regenerate bundle 4.16.0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
MaxGhenis
changed the title
MaxGhenis
force-pushed
the
populace-bundle-build-id
branch
from
fbee4c9 to
c49461e
Compare
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.
The v2 generation path never emitted build provenance into compatibility metadata —
data_build_id,built_with_model_version,built_with_model_git_sha, anddata_build_fingerprintonly existed in the legacy certification model. policyengine.py's bundle importer reads exactly those keys to populatecertified_data_artifact.build_idand thecertificationblock, so v2-generated bundles imported with null build provenance.This carries the release manifest's
buildblock into the metadata (heredata_build_id=populace-us-2024-5da5a95-20260611,built_with_model_version=1.723.0; git sha and fingerprint emitted when present) and regenerates bundle 4.16.0. UK is unchanged (its release manifest predates the build block).Validation:
scripts/validate_bundle.py bundles/4.16.0exit 0; 88 unit tests pass.🤖 Generated with Claude Code