Skip to content

EPIC: certified populace-us default correctness (gates not fully wired / reference rotted) #28

Description

@MaxGhenis

Tracking epic — certified populace-us default correctness

The certified US default (populace_us_2024.h5, bundle 4.16.2) has correctness issues its gate suite did not catch — some because a gate's reference rotted, some because a defined gate was never wired into the build. All findings below are reproduced (sha-verified certified artifact; build's own check_parity.py recovered from git history; column classification against policyengine-us variable definitions). This epic centralizes the fixes.

Root meta-issue

The acceptance suite (exported_nonzero, formula_owned_export, parity, support, aggregate_vs_admin, per_family_fit) exists in populace.build.gates, but the build pipeline only ran exported_nonzero + parity, against an unpinned eCPS reference, and the runner + reference were deleted from HEAD (fda3838 "Remove retired build and benchmark surfaces"). So "parity 0" was real but non-reproducible and silently rotted, and formula_owned_export never ran at all.

Issues (suggested order)

Decision input

  • #20 — Downstream blocking assessment (CRFB taxation-of-benefits, PolicyBench) — informs how urgently the rebuild ships vs. the current certified default.

PR #21 (pin-parity-reference) already lands the reference-pinned, recorded, reconstructable parity runner (part of PolicyEngine/microcosm-benchmarks#1).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions