populace-build: TRACE TRO emission for dataset builds - #16
Merged
Conversation
Emit Transparent Research Objects (w3id.org/trace/trov/0.1) for populace builds: composition pins output artifacts, restricted survey inputs, and content-hashed build-config/gate/stage payloads by sha256; restricted inputs are flagged pop:accessRestricted at their canonical access location. tro_from_release_manifest converts the existing release manifest mechanically; the shipped populace-us-2024-9f1260b-20260611 TRO is generated from it and published alongside the release on the Hub. Hash algorithms replicate policyengine.provenance.trace exactly (documented) so both ecosystems' fingerprints interoperate. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jun 13, 2026
MaxGhenis
marked this pull request as ready for review
June 14, 2026 16:21
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.
Fixes #15
Adds
populace.build.trace: TRACE Transparent Research Object (TRO) emission for populace dataset builds, conforming to the TROv vocabulary (https://w3id.org/trace/trov/0.1#).What a build TRO binds
pop:accessRestricted. A re-runner cannot fetch the bytes, but anyone with access can confirm the same checksummed input was used.Honest gate claims
pop:gatesPassedis derived only from recorded verdicts (explicitpassedbools,*_gaps == 0counters) and omitted when the manifest records evidence without pass criteria — the TRO never claims more than the build recorded.Interoperability
Canonical-JSON encoding and the composition fingerprint replicate
policyengine.provenance.tracebyte-for-byte (documented on each function); the module itself is stdlib-only and decoupled.Shipped artifact
packages/populace-data/build/us/populace_us_2024.trace.tro.jsonldis generated from the existing release manifest (deterministic — emitted twice and diffed) and published at https://huggingface.co/datasets/policyengine/populace-us/resolve/main/releases/populace-us-2024-9f1260b-20260611/populace_us_2024.trace.tro.jsonld (fetched back and byte-identical). Composition fingerprint:64c1db587b49f1000c49b55c3ee6e4aa35030626a057258573053407aae62df3.Usage
34 tests; ruff clean.
🤖 Generated with Claude Code