PolicyEngine / PolicyEngine/policyengine-skills
Add populace-contributor skill: working inside the Populace data stack
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 6
Description
The policyengine-data skill (#61) covers consuming Populace — architecture, certified releases, dataset names, the local-area philosophy. Contributors need the producer side: build plans and stages, release gates (what refuses and why), staging telemetry, the certification path into policyengine.py bundles, and where targets/facts come from (Ledger profiles).
Source of truth is the populace repo's DESIGN.md + build docs; the skill should be pointers + the non-derivable gotchas (checkpoint roots outside the repo, run-once clone guards, reference-pinning rules), not a duplicate of the design charter.
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 by reading the policyengine-data skill in issue #61, then consult the Populace repo's DESIGN.md and build docs. Document pointers to build plans, stages, release gates, staging telemetry, certification into policyengine.py bundles, and Ledger profiles, plus the listed non-derivable gotchas; keep the result from duplicating the design charter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100