PolicyEngine / PolicyEngine/policyengine.py
Adopt Microcosm naming (populace-data → microcosm-data, legacy-aware certification)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 9
- Avg merge
- 15h 51m
- Merged PRs (30d)
- 9
Description
Populace was renamed to Microcosm on 2026-08-07 (PolicyEngine/microcosm; dists microcosm-frame/-fit/-calibrate/-data/-build once microcosm#638 lands). policyengine.py references the populace-data package and Populace naming in certification/bundle machinery.
- Certified release manifests record
data_package.name = "populace-data"— any name check must stay legacy-aware until the next certified release (mirror of the contract change in microcosm#638). - HF repo ids and artifact pins are unchanged; do not touch pinned URIs.
- Prose/docs → Microcosm; git-source deps → the renamed packages at their post-#638 SHAs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in policyengine.py, especially the certification and bundle machinery that references populace-data and Populace. Trace how release manifests and git-source dependencies are handled, preserving legacy populace-data names in certified manifests and leaving pinned URIs unchanged. Done means prose uses Microcosm and dependencies use the renamed packages at their post-#638 SHAs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100