Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add protected Housing Benefit family premiums with explicit history input

Aperta
#2,222 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@anth-volk ci sta già lavorando.

Dal 9/10/2026.

  • #2223 di @anth-volk — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
python
Ambito
backend

Direzione di ricerca

The work touches policyengine_uk/variables/gov/dwp/housing_benefit/housing_benefit_applicable_amount.py and a new premiums/family package of YAML and Python files, but the issue is a dense legal-design plan with pre-assessed categories and jurisdiction-specific closure dates. Pull request #2223 is already open against it, so the work is claimed. Done would mean the approved plan's files exist with test cases, which requires the maintainers' design context.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Approved plan C3 adds the protected Housing Benefit family premium, with ordinary and historical lone-parent amounts, jurisdiction-specific new-claim closure dates, one pre-assessed category and one derived formula. Eight files and one categorical input; no claim-history input matrix. Benefit and pension rates 2025 to 2026 (Housing Benefit: personal allowances, capital, non-dependant deductions and earnings disregards); Benefit and pension rates 2026 to 2027 (Housing Benefit: personal allowances, non-dependant deductions and disregards; cross-checked against the enacted 2026 Order); Housing Benefit family premium amounts (Paragraph 3: ordinary and historically protected lone-parent rates and conditions); Family premium closure and transitional protection (Regulations 1, 2 and 4: closure 1 May 2016 and saved existing families); NI family-premium abolition and transition (Regulations 1, 3 and 5; 5 September 2016 closure, 4 September protected awards)

Audited model surface

  • Audited release: policyengine-uk 2.106.1
  • Audit unit: variable:housing_benefit_applicable_amount
  • Last model modification: 2024-07-15
  • Explicitly reviewed units:
    • variable:housing_benefit_applicable_amount — last model modification: 2024-07-15
  • Audit date: 2026-10-09
  • Periods reviewed: 2015 to 2026 rate history; GB 1 May 2016 and NI 5 September 2016 closure
  • Jurisdictions: Great Britain and Northern Ireland

Findings and implementation parts

1. The applicable amount omits the family premium for protected awards and the distinct historical lone-parent amount.

Sources: Benefit and pension rates 2025 to 2026 (Housing Benefit: personal allowances, capital, non-dependant deductions and earnings disregards); Benefit and pension rates 2026 to 2027 (Housing Benefit: personal allowances, non-dependant deductions and disregards; cross-checked against the enacted 2026 Order); Housing Benefit family premium amounts (Paragraph 3: ordinary and historically protected lone-parent rates and conditions); Family premium closure and transitional protection (Regulations 1, 2 and 4: closure 1 May 2016 and saved existing families); NI family-premium abolition and transition (Regulations 1, 3 and 5; 5 September 2016 closure, 4 September protected awards)

Uncertainties and exclusions

No verified dataset mapping for continuous award protection. From each jurisdiction's closure year, absent/NONE input omits protected premiums and may understate awards. The category must reflect all continuity and loss-of-protection conditions; the model does not reconstruct them. Annual input does not recover changes within the year. New-claim end dates are legal metadata, not a future freshness guarantee.

Lingua principale
Python
Stelle
51
Fork
34
Merge medio
2g 13h
PR unite (30g)
177

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PolicyEngine/policyengine-uk

Tutte le issue di PolicyEngine/policyengine-uk

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.