Align UK UC claim, child and period definitions

Cerrado
  • ¿Algo no está bien?
#882 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
data-engineering

Línea de trabajo

Comience con packages/microcosm-build/src/microcosm/build/uk/uk_population_targets.json y el feed family-by-payment-indicator de Chronicle fijado. No se nombra ninguna ruta de prueba ni ningún punto de entrada de implementación, así que siga los criterios de aceptación a través del código de generación de objetivos y calibración de Microcosm, y después verifique los estados de reclamación separados, los períodos de origen, los joints compatibles, la procedencia y los informes de sensibilidad.

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

Descripción

This consolidates the remaining UC consumer-contract questions from #736 and #738, following the benefit-unit corrections in #727 and #813. It supports the UC investigation alongside #879 and #701; SPI generation remains tracked in #840. The evidence below is limited to public repository code and published aggregate source tables.

Reproducible discrepancies

  • Paid versus all claims. The current contract at eb7ca8a5 counts universal_credit > 0 against all-claim headline/composition rows. The pinned family × payment-indicator source has 90 cells: five family categories × Yes/No × April–December 2025. Summing the five family cells within each month, then averaging the nine months, gives 6,316,227.78 paid and 542,059.89 nil-payment claims. DWP explicitly retains some open claims with no payment. These quantities cannot be treated interchangeably. (Payment indicator definition)
  • The required joint is unavailable. The pinned feed contains family × payment indicator, family × child entitlement and child count × child entitlement. It does not contain payment indicator × child entitlement, or payment indicator × child count. Therefore pairwise margins cannot identify the paid/child-entitled composition joint. Child Entitlement Yes also does not turn the reported child-count axis into a count of qualifying children. Chronicle #233 and #234 closed the earlier ingestion requests; the remaining consumer alignment is still necessary.
  • Monthly cash and annual model payments differ in timing. The unresolved bridge is to DWP's monthly payment amount, which includes third-party payments and one-off advances in their issue month. Dividing an annual model award by 12 does not establish that equivalence, especially for rare upper-band cells. (DWP amount definition)
  • Observation periods need an explicit comparison contract. The public April–December 2025 series has nine monthly observations; the TCL methodology covers open claims during April and a 6 April 2017 birth cutoff. It includes exceptions and distinguishes its dependent/qualifying-child definition from the broader verified under-20 children reported on Stat-Xplore. A source April snapshot, a nine-month average and an annual model state need separate labels and a documented comparison.

Acceptance criteria and ownership

  • Microcosm: declare and test each target's claim state, benefit-unit/child definition, geography, amount basis and source/model observation periods. Preserve separate all-claim, paid and nil-claim diagnostics; do not blindly rebind all-claim targets to paid margins.
  • Microcosm: enforce the declared source-month set and record the actual averaging denominator. Retain April snapshot dates separately from annual assignment.
  • Microcosm: establish the age/cohort anchor across the source year, model year and source observation date; preserve its provenance and test year transitions. If exact birth dates or open-claim state are unavailable, record the approximation and its sensitivity.
  • Microcosm, with PolicyEngine-UK where model inputs are required: test TCL claimant roles, own qualifying children, exceptions and element denial separately, including nil-payment claims, 18–19-year-olds, multiple benefit units in one dwelling and the birth-date boundary. Claimant PIP and disabled-child elements must refer to the relevant claim's members.
  • Microcosm: support only identifiable joints. Do not construct a joint from marginal products or rename reported children as qualifying children. Chronicle owns any additional publisher cross export.
  • Microcosm: reconcile the headline and family cells using a common-vintage published total, unknown-family cells and disclosure tolerances. Chronicle #247/PR #250 owns the published-total/history feed update; the consumer comparison remains a Microcosm responsibility.
  • Microcosm: audit joint support by reported-child count, own qualifying-child count, birth cohort, family roles and claim/payment state. Trace missing or thin cells through source stages before choosing generation changes; retain original-source lineage in diagnostics.
  • Microcosm: compare repairs at a fixed optimizer budget and report target-specific original-source support, source contribution and leave-one-source-out sensitivity alongside global concentration and convergence. Do not alter target values or exclusions solely to improve fit.
Lenguaje dominante
Python
Estrellas
0
Forks
6
Merge medio
2 d 5 h
PR fusionados (30 d)
150

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/microcosm

Todos los issues de PolicyEngine/microcosm

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.