PolicyEngine / PolicyEngine/microcosm
Preflight compiles the registry without the build's identity inputs — can pass what the build rejects
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 94
Description
Audit finding 8 of #468, split out because it is a correctness defect, not just recompute waste: release_gate_preflight omits CD-inclusion/crosswalk, allow_unaged_dollar_targets, and extra support exclusions when compiling the registry, so standalone preflight and the build can disagree on the target surface — preflight green, build red (or worse, the reverse under future flags). Fix: preflight consumes the build's exact compilation configuration (same flags, same exclusions), or both consume one content-addressed compiled-registry artifact keyed by feed hash + every flag/resource hash. The caching half also removes the duplicate compilation (2× per workflow today).
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 tracing the release_gate_preflight entry point and the build path that compiles the registry, then compare the configuration inputs each consumes. Done means both paths use identical flags and exclusions, or share a compiled-registry artifact keyed by all listed inputs, without duplicate compilation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100