Emit a TRACE Transparent Research Object (TRO) for every populace dataset build, so the microdata-construction provenance is certifiable in the emerging TRACE standard (w3id.org/trace).
This is the prime TRACE use case identified with the AEA Data Editor: the build consumes restricted inputs (IRS PUF, Fed SCF, Census SIPP) that third parties cannot re-access, so a checksummed provenance certificate — inputs, pinned code, gates, outputs — provides credibility that re-running cannot.
Scope:
- trov-vocabulary JSON-LD emission in populace-build (stdlib-only, decoupled from policyengine.py but hash-compatible with its TROs)
- converter from the existing release_manifest.json shape
- TRO for the shipped populace-us-2024-9f1260b-20260611 release, published alongside the release on the Hub
Emit a TRACE Transparent Research Object (TRO) for every populace dataset build, so the microdata-construction provenance is certifiable in the emerging TRACE standard (w3id.org/trace).
This is the prime TRACE use case identified with the AEA Data Editor: the build consumes restricted inputs (IRS PUF, Fed SCF, Census SIPP) that third parties cannot re-access, so a checksummed provenance certificate — inputs, pinned code, gates, outputs — provides credibility that re-running cannot.
Scope: