PolicyEngine / PolicyEngine/microcosm
Require certification and publication tooling to descend from the deny-list merge
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 94
Description
PR #857 adds a sealed deny-list for the candidate-26 pool enforced in loaders, receipts, selection manifests, and the publisher's release contract. Merged code cannot constrain a stale checkout: a builder or publisher run from a tree predating the merge still admits the pool through the gate-failed opt-in. Follow-up: make certification and publication refuse to run from a tree that does not descend from the deny-list merge commit (record the merge SHA once #857 lands), and log the check in the release receipt. Refs #856, #857.
🤖 Generated with Claude Code
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 reviewing PR #857 and the certification and publication flows it affects, including release receipt generation. Trace how the current gate-failed opt-in is admitted from a stale checkout. Done means both flows reject trees that do not descend from the recorded deny-list merge and the release receipt logs the ancestry check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, security, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100