Skip to content

Triage policyengine-us-data backlog for Populace migration #46

Description

@MaxGhenis

Context

policyengine-us-data is no longer the live build surface for replacement microdata. Populace supersedes it, so open policyengine-us-data issues/PRs should be triaged into Populace work only when the underlying data-quality, target, export, or release-contract concern is still relevant.

This issue records a pass over the live open PolicyEngine/policyengine-us-data issues and PRs on 2026-06-14, after Populace PRs #44 and #45 merged.

Already covered or mostly covered in Populace

Copy into existing Populace issues

New Populace follow-up issues to consider

Move outside the live Populace repo

  • policyengine-us-data #1163 / PR #1164: production eCPS baseline resolver and integrity gate. The lesson is important, but incumbent/eCPS comparison should live in PolicyEngine/populace-benchmarks or another benchmark repo, not in live Populace build code.
  • Any remaining eCPS/local-baseline promotion comparisons should be benchmark-repo work only. Populace release gates can expose diagnostics; they should not depend on a stale incumbent artifact.

Do not migrate directly

Acceptance criteria

  • Existing Populace issues above are updated or linked with the relevant source backlog.
  • Any missing Populace issues from the follow-up section are opened or explicitly rejected.
  • No old policyengine-us-data, Microplex, L0, or eCPS comparison implementation is copied into live Populace without translating it into Populace's spec-driven architecture.
  • Benchmark-only eCPS comparison work is tracked outside live Populace.

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