Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add protected Housing Benefit family premiums with explicit history input

Abierto
  • ¿Algo no está bien?
#2,222 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@anth-volk ya está trabajando en esto.

Desde el 9/10/2026.

  • #2223 de @anth-volk — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
51
Forks
34
Merge medio
2 d 13 h
PR fusionados (30 d)
177

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PolicyEngine/policyengine-uk

Todos los issues de PolicyEngine/policyengine-uk

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.