PolicyEngine / PolicyEngine/policyengine-claude
Update agent docs away from split state/district H5 datasets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 32
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
PolicyEngine/populace#237 removed release generation for one-file-per-state and one-file-per-district artifacts. The replacement path is the single certified Populace national H5 plus the standard region/scoping machinery in policyengine.py, not direct hf://policyengine/policyengine-us-data/states/... or districts/... files.
GitHub code search still finds split-H5 references in this repo:
skills/tools-and-apis/policyengine-microsimulation-skill/SKILL.mdskills/analysis/policyengine-district-analysis-skill/SKILL.mdskills/domain-knowledge/policyengine-healthcare-skill/SKILL.md
Migration checklist:
- Stop constructing or documenting
policyengine-us-data/states/*.h5andpolicyengine-us-data/districts/*.h5dataset URIs. - Use the certified Populace default dataset through policyengine.py, with region filters/scoping for state and congressional-district analyses.
- Add or update a regression test so future state/CD runs do not depend on split regional H5 files.
- Keep historical/generated output unchanged unless it is actively used by the app or docs.
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
Read the three named SKILL.md files and the standard region/scoping machinery in policyengine.py, then search the repository for split state and district H5 URIs. Update the documented paths to use the certified Populace default dataset, add or update regression coverage for state and congressional-district runs, and verify that no active docs or app paths depend on split regional H5 files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100