ALLPAY2 is counted in two UK income columns; spousal maintenance column (mirror of uk-data)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- data-engineering
Research direction
Start with packages/microcosm-build/src/microcosm/build/uk_runtime/frs_spine.py and compare the corresponding change in PolicyEngine/policyengine-uk-data#627. Check the FRS 2024-25 dictionary entries for ALLPAY2 and the handling of APAMT/APDAMT; done means ALLPAY2 appears in one income list and the runtime includes the matching spousal maintenance column in OUTPUT_COLUMNS if uk-data adds it.
Written by the indexing model from the issue text.
Description
Mirror of PolicyEngine/policyengine-uk-data#627 for the Microcosm UK runtime: packages/microcosm-build/src/microcosm/build/uk_runtime/frs_spine.py (main 41209b38c).
- ALLPAY2 counted twice.
miscellaneous_incomesums("allpay2", "royyr2", "royyr3", "royyr4", "chamtern", "chamttst")andprivate_transfer_incomesums("apamt", "apdamt", "pareamt", "allpay2", "allpay3", "allpay4"). The FRS 2024-25 dictionary labelsALLPAY2"Amount of allowance: organisation", a single amount. Keep it in one list, matching whatever uk-data does. - Spousal maintenance. If uk-data splits
APAMT/APDAMT("Amount received from absent partner", "... paid directly") into aspousal_maintenance_incomecolumn, write the same column here (and add it toOUTPUT_COLUMNS), so policyengine-uk can count it as Pension Credit income under SPC Regs 2002 reg 15(5)(d).
Context: PolicyEngine/policyengine-uk#1954.
🤖 Generated with Claude Code
- Dominant language
- Python
- Stars
- 0
- Forks
- 5
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 148
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from PolicyEngine/microcosm
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/microcosm#1220 ·
Maintainers usually reply within 1 day
-
Update two stale comments about the export-mass reviewed-exclusion registerPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PolicyEngine/microcosm#1108 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
PolicyEngine/microcosm#475 ·
Maintainers usually reply within 1 day
-
US targets label three dimension values two ways: re-pin the Chronicle feed with one label eachPossibly taken @anth-volk claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
PolicyEngine/microcosm#1343 ·
Maintainers usually reply within 1 day
-
Declare each calibration hierarchy label once: diagnostics schema 9 catalogsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 5/5 Over a week Newbie friendliness 32/100
PolicyEngine/microcosm#1341 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/microcosm
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yunaremaia/proto-drift#22 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yunaremaia/memwatch#96 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 91/100
yunaremaia/ci-gate-watch#34 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
yunaremaia/agent-capability-attestation#64 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 86/100
yunaremaia/agent-call-graph#43 ·
Maintainers usually reply within 1 day