PolicyEngine / PolicyEngine/define-uk-model
Validation gate before DEFINE-UK results are presented beyond replication
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
DEFINE-UK currently runs the unlicensed upstream model at a pinned commit. Before its results are surfaced as more than a replication:
- Define acceptance criteria vs the pinned upstream run (tolerances, which outputs).
- Wire a CI invariants gate mirroring the other model repos (obr-macroeconomic-model, boe-var-model).
- Resolve or document the upstream licensing position.
🤖 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 comparing the DEFINE-UK scaffold with the invariants and CI setup in obr-macroeconomic-model and boe-var-model. Define the accepted outputs and tolerances for the pinned upstream replication, add the corresponding CI gate, and document the upstream licensing position. Done means the criteria, automated checks, and licensing status are explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, documentation, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100