PolicyEngine / PolicyEngine/microcosm
Denied-pool identity: version over mandatory relational content, with false-positive tests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 94
Description
The deny-list in microcosm.data.denied_pools (PR #857) identifies the sealed candidate-26 pool by four identities; the packaging-independent one (version 2) is the sorted multiset of household weights plus the count. Sol's final gate round on #857 noted it is not semantic: changing one weight admits otherwise unchanged content, and a legitimately corrected pool that keeps the same weights would be falsely denied. Follow-up: define a versioned identity over mandatory relational content and provenance (households, memberships, and the support/clone structure, not weights alone), with tests for (a) same weights, different payload and (b) changed weights, same support, plus a reproducible derivation receipt for the sealed candidate-26 identity. 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 in microcosm.data.denied_pools and read the context from PRs #856 and #857, especially the final-gate concerns. Define the versioned identity around the named relational content and provenance, then add tests for both payload and weight changes and a reproducible derivation receipt for the sealed candidate-26 identity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100