Public validation inventory

One of the strongest parts of this proposal is that the model can be validated extensively against public sources before any restricted administrative linkage is available. The public record is fragmented, but it is much richer than many policy-model proposals acknowledge. That matters for two reasons.

First, it means the project can set milestone-based validation gates using sources that outside reviewers can inspect themselves. Second, it reduces the risk that the project becomes blocked on restricted-data negotiations before it can produce a credible first model.

This chapter inventories the main public or low-friction sources we can use to validate the model. It is not an exhaustive bibliography. It is the minimum practical source stack for judging whether longitudinal populace is becoming decision-useful.

Many of these sources are already assembled inside populace, PolicyEngine’s microdata stack — the primary-source microdata and the calibration targets (from CBO, IRS, SSA, Census, and others) that it draws on. Naming the sources explicitly here keeps the validation record legible to outside reviewers, who can inspect the underlying public tables and microdata themselves rather than taking the data layer on trust.

Access tiers

The validation stack naturally breaks into four tiers.

The proposal should be explicit that stage gates are built primarily on the first two tiers. The third tier is a bonus, not a prerequisite.

Core source inventory

Source Access tier Best use in this project Main caveat
SSA Annual Statistical Supplement (Social Security Administration, Office of Research, Evaluation, and Statistics 2025b) Open public tables National benchmarks for insured status, benefit type, awards, terminations, dual entitlement, and SSI distributions Aggregate, not person-level
SSA DI Annual Statistical Report (Social Security Administration, Office of Research, Evaluation, and Statistics 2025a) Open public tables Disability incidence, beneficiary composition, awards, application outcomes, and return-to-work patterns Administrative program view, not a full longitudinal panel
SSA SSI Annual Statistical Report (Social Security Administration, Office of Research, Evaluation, and Statistics 2025d) Open public tables SSI caseload, recipient composition, payment levels, and state patterns Aggregate, not household microdata
OASDI Beneficiaries by State and County (Social Security Administration, Office of Research, Evaluation, and Statistics 2025c) Open public tables Geographic validation for beneficiary counts and amounts No full person-level covariates
CPS ASEC (U.S. Census Bureau 2025) Public microdata Cross-sectional income, demographic, and Social Security income benchmarks Retrospective income reporting, limited panel structure
ACS (U.S. Census Bureau 2026) Public microdata and tabulations Population geography, demographic structure, and local benchmarking Limited retirement-program detail relative to SSA files
SIPP (U.S. Census Bureau 2024) Public longitudinal microdata Program participation dynamics, family composition, wealth, and monthly transitions Shorter panel horizon than a lifecycle model
PSID (Panel Study of Income Dynamics 2025) Public longitudinal microdata Long-run earnings, wealth, marriage, fertility, and intergenerational structure Smaller sample, weaker direct program detail
HRS (University of Michigan, Institute for Social Research 2025) Public longitudinal microdata Older-age work, claiming, health, and wealth dynamics Focused on older cohorts
NHATS/NSOC (National Health and Aging Trends Study 2025) Public or application-based microdata Functional status, care receipt, and caregiving for LTC extensions Older-adult focus, not all-age LTSS
MCBS (Centers for Medicare & Medicaid Services 2025a) Public-use and limited data Medicare beneficiaries, utilization, health status, and older-age spending Community/facility split matters for use cases
NVSS mortality tables (Centers for Disease Control and Prevention, National Center for Health Statistics 2025) Open public tables Mortality, life expectancy, and cause-of-death structure Not a direct Social Security mortality table
OACT life tables and Trustees material (Social Security Administration, Office of the Chief Actuary 2025; Board of Trustees, Federal Old-Age and Survivors Insurance and Federal Disability Insurance Trust Funds 2025) Open public tables and reports Projection alignment, mortality assumptions, taxable payroll, and beneficiary totals Designed for official projection use, not open micro-simulation replication
T-MSIS overview and TAF documentation (Centers for Medicare & Medicaid Services 2025c, 2025d) Open documentation plus research files Medicaid enrollment, LTSS utilization, state variation, and later LTC validation Data quality varies by state; research files require more setup
MDS 3.0 technical information (Centers for Medicare & Medicaid Services 2025b) Open technical documentation and files Institutional care benchmarks for nursing-home populations Not a household survey; linking to other populations is nontrivial

Minimum validation set by model block

Population and household structure

The baseline population should be judged first against Census products and then against longitudinal surveys.

Earnings, coverage, and insured status

This is where the proposal needs the most discipline. Public validation does not recover exact administrative earnings histories, but it can still test the outputs that matter for Social Security use.

The proposal should continue to treat public validation of AIME-like and benefit-like outputs as a must-pass requirement even before restricted SSA linkages exist.

Claiming, auxiliary benefits, and beneficiary status

Public SSA tables are stronger here than many teams realize.

Disability and SSI

This is one of the strongest public-validation areas because SSA publishes a surprisingly rich disability record.

Mortality and projection drift

Projection validity should be judged against public official projections, not only against internally generated smooth paths.

LTC and caregiving extension

The LTC extension would also have a substantial public validation stack, even if it is thinner and more fragmented than the Social Security one.

This still does not make LTC easy. It does mean that an LTC extension can be validated more seriously than most high-level proposals imply.

What public sources still cannot solve

This appendix should not be read as claiming that public validation is enough for every question.

  • Public sources will not reproduce exact SSA administrative earnings histories at the person level.
  • Public sources are weaker on precise application processing, adjudication timing, and some program-interaction edge cases.
  • LTC remains harder because the public record is split across household surveys, facility instruments, Medicaid systems, and state manuals.

But those limitations are different from saying the model cannot be validated. The more accurate statement is that the project can produce a substantial public validation record before it reaches the frontier where restricted administrative data would add the most value.