Skip to content

Add reported-benefit Social Security PIA ratio lever - #10484

Merged
MaxGhenis merged 86 commits into
mainfrom
ss-pia-ratio-lever-c
Oct 30, 2026
Merged

MaxGhenis merged 86 commits into
mainfrom
ss-pia-ratio-lever-c

Conversation

@MaxGhenis

@MaxGhenis MaxGhenis commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Both prerequisite PRs, #10400 and #10401, have merged into main. Main is merged into this branch.

Round-1 review fixes

Review head: fea0d26ef98a6771e946f621e8edd2bff11a046c. The only production behavior change in this round is proxy classification for assumed retirement claiming ages.

  • Claiming proxies: all four sensitivities now flag resolved records even with exact birth dates; supplied-age and entitlement-date rules are unchanged. Six added resolver cases cover the sensitivities and both observed-source controls. Born 1956-06-15, FRA is 796 months: the adjustments are 1 - 36/180 - 16/240 = 11/15, 1 - 16/180 = 41/45, 1, and 1 + 44/150 = 97/75. The review example keeps E=2018 and adjustment 41/45, with proxy=true and unmodeled=false.
  • Named reporting: a two-retiree household checks named proxies [true, true], proxy count [2], positive sensitivity AIMEs and exclusion from the documented identified-only filter. There is no separate identified-only AIME output; consumers must filter proxy, unmodeled, missing-claim-age and pre-1983 records and report sensitivities separately.
  • Current-law ingress: three new differential cases compare public situations, later public set_input, and YAML through Core's SimulationBuilder against main's constant-one hooks. They carry 2024 public inputs into 2026, checking SSI directly plus the four components, their sum, taxes, household net income and every reached baseline cached output. A fourth case checks multiple household members and weighting counts once. A shared read-only neutral reference avoids repeated cloning.
  • Composition: one native-SSA-subtree test recovers AIME 5,000 using baseline COLA 1.028 and ratio 2295.5/2156.8, then checks that joint COLA, PIA ratio, across-the-board and payable factors each apply once. Reform COLAs and cached reformed benefits cannot enter inference. No country clone is built by this test.
  • Test isolation: both reformed Core fixtures construct private Reform wrappers and preserve PE-US's input carry-forward setting on those wrappers and the neutral reference. Core applies reform= in place to an explicitly supplied system; the first local run exposed a selector leaking into two following existing cases (8 passed, 2 failed). A private-wrapper retry exposed Core's generic carry-forward default (9 passed, 1 failed). The final complete rerun passes all ten unchanged-assertion cases with private parameters and the country input contract preserved.
  • Base: branch start was exactly 22bcfb497c4235cd0498adf38a09d873a33919e7. Main remains c55b806541c4b8a2fe1530a2468bf231befe5f22; no new merge or resolved hunks. Nothing under .github/ changed.

Round-1 validation

Full CI is green at fea0d26ef98a6771e946f621e8edd2bff11a046c. The final-head run 40796218956 completed successfully. Verified at 02:00:31Z on October 29: 34 checks passed, one documentation-deployment check skipped, no failures or pending jobs. All 11 Baseline jobs, all nine Contrib jobs, all six Rest Python shards and their aggregate, Quick Feedback, and Microsimulation passed. Monitoring took about 74 minutes after the final push, within the 100-minute limit, with checks polled no faster than every five minutes.

The changed files pass 25 cases in CI and locally: retirement resolution 14 (6 added), Core ingress/reporting 10 (5 added), composition 1 (new). Historical results below belong to preceding heads. Added simulation tests share one neutral reference and add one sensitivity reform; both reformed tests now own private parameter copies.

The original seven focused files plus the new composition file pass 184 cases at this head, up from 172 before the round-1 additions. Final JUnit artifacts confirm 47 ratio-service, 5 parameter-path, 14 retirement-record, 33 survivor-record, 12 worker-basis, 62 routing/code-health, 10 Core-ingress and 1 composition passes, with no failures, errors or skips in this focused set.

Changed file under policyengine_us/tests/ Final-head CI result
unit/test_ss_population_retirement.py 14 passed; summed JUnit case time 0.013s; Rest Python shard 3
core/test_ss_pia_ratio_inputs.py 10 passed in 46.98s pytest / 94.34s process; Rest Python shard 2
unit/test_ss_population_composition.py 1 passed; JUnit case time 0.020s (rounded setup/call 0.01s each); Rest Python shard 3

The two unit-file timings include their case setup/teardown and exclude the containing process's shared country import. Per-file process wall/RSS are unavailable for those files. Their containing remaining group passed 3,204 tests with 11 skips, with 1,603.15s process wall and 7,928,704 KiB peak RSS; those resource figures describe the entire group, not these two files.

All 33 original PIA-ratio YAML cases passed twice in Quick Feedback at this final head; both executions used coverage commands. First/second file times were: retirement factor 8 passed, 80.82/78.70s; claiming 5 passed, 77.22/77.65s; eligibility 10 passed, 71.83/71.13s; disability 4 passed, 46.74/46.03s; dependents 4 passed, 46.66/45.91s; survivors 2 passed, 32.80/32.54s. This retains the original S.770 case and all pre-existing assertions.

Changed file under policyengine_us/tests/ Local pytest result Full process including import
unit/test_ss_population_retirement.py 14 passed in 6.85s 255.61s
core/test_ss_pia_ratio_inputs.py 10 passed in 286.62s 926.84s
unit/test_ss_population_composition.py 1 passed in 7.15s; fixture 1.33s, call 0.62s 270.11s

At this final head, Rest Python shard 2 passes the complete Core file: 10 passed in 46.98s, 94.34s process wall, 3,132,092 KiB peak RSS (2.99 GiB), exit 0. Before this round, its five cases took 35.915s in CI, with 68.47s process wall and 2,359,476 KiB peak RSS. The measured growth is 11.066s pytest / 25.87s full process, within the approximate one-minute added-time budget; peak RSS rises by 772,616 KiB (0.74 GiB). The five added cases total 16.787s of JUnit time including their setup/teardown; the shared reference setup is charged to the first existing case. The earlier intermediate head's two isolation failures are superseded by this complete final-head pass.

make format and Ruff pass. env -u UV_FROZEN uv lock --check passes without relocking (150 packages, 9ms). Local Python uses the required 4 GiB / 1,800-second cap, thread caps of four, passive OpenMP waiting and a load1 gate at 100. Mutants use 2 GiB / 900 seconds.

The evidence patch claiming-sensitivity-proxy-removed.patch removes this round's fix. It is caught by all four cases of unit/test_ss_population_retirement.py::test_imputed_claiming_scenario_is_flagged_with_exact_birth, each failing at the proxy assertion. The normal-import run completed with 4 failed / 10 deselected in 1.57s, full process 56.66s, exit 1, under the required 2 GiB / 900-second cap (starting load1 42.86). Production source was restored and verified unchanged against Git. The named-output integration test is an additional intended detector. The four review mutants remain assigned to the hub; no local detection result is claimed for them.

Reported-benefit PIA ratios

Implements design v3 C1–C3, A1/A5.2, P2, ADDENDA item 2, and amendments M2/M4/M8/M9. The four reported-benefit components now use the shared PIA service to apply new_PIA(inferred_AIME, E; t) / baseline_PIA(inferred_AIME, E). Inference starts from the unreformed annual reported benefit, removes the claiming/composite-share adjustment and unreformed COLAs, and uses the baseline inverse's lower endpoint. The forward baseline and reform calculations read the same FormulaPath as the household calculator; applicability uses its existing cohort/recompute mode.

  • Adds social_security_retirement_claim_age_months, a pure annual Person input without a formula or uprating. The explicit claiming selector offers supplied_claim_age (default), entitlement_dates, age_62, age_65, fra, and age_70; missing or unusable supplied ages have no fallback.
  • Resolves supplied worker eligibility/computation years and links before proxies, rebuilding an absent retirement basis as E = t - age_t + 62 within each scoring year's cross-section. Disability uses adjustment one and supplied onset/entitlement information before its labelled pre_reform or current_year sensitivity.
  • Preserves neutral current law, zero amounts and calculated-source bypass. Rejects negative/nonfinite reported benefits, invalid identified ratios and nonpositive divisors. The reported route composes the PIA ratio with the existing joint COLA, across-the-board and payable factors once.
  • Keeps the custom C2 15% first-bend-point fixture distinct from S.770's 18% preset. S.770 reported-survivor inference shares the household calculation's ordinary computation/death basis and interpretation switch.

Named outputs and supported coverage

For X in retirement, disability, survivors and dependents, these annual Person variables expose the inference. Monetary values are monthly dollars at the eligibility-year basis; the source benefit is annual.

Variable after social_security_X Meaning and limits
_inferred_aime Baseline inverse point estimate; the lower endpoint for an exact dime-rounded eligibility PIA. An optional annual measurement bound expands the interval without moving this point.
_inferred_aime_lower_bound, _inferred_aime_upper_bound Inclusive lower and exclusive upper conditional AIME bounds. These are not a complete survey-error interval.
_pia_ratio_eligibility_year Underlying worker eligibility/computation year E.
_pia_ratio_claiming_adjustment Imputed worker adjustment a. Zero marks unavailable claiming data on a positive retirement record. On an auxiliary composite-ratio route it is one by decomposition convention; the entire a * s is supplied in the worker-benefit ratio.
_pia_ratio_own_record_retired_worker Modeling classification for an unmixed own-record retired-worker amount; it does not establish insured status or administrative entitlement.
_pia_ratio_missing_claim_age, _pia_ratio_pre_1983, _pia_ratio_unmodeled, _pia_ratio_proxy, _pia_ratio_measurement_uncertainty Coverage, approximation and measurement indicators.

Zero AIME diagnostics mean no inference and must be read with the flags. For an identified-only own-record AIME distribution, exclude proxy, unmodeled, missing-claim-age and pre-1983 records and inspect measurement uncertainty. Every resolved age_62, age_65, fra or age_70 sensitivity is a proxy even with an exact birth date. Supported proxy AIME outputs remain available for separately reported sensitivities. Each coverage indicator has a Household _count variable. Weight those household counts once when members share that weight; distinct Person weights require weighting the Person indicator directly. Unmodeled amounts should likewise be reported with their Person weights.

Unsupported positive records keep factor one and expose flags: missing/unusable retirement claiming data, mixed retirement components, pre-1983 benchmarks, links without a supported worker basis, and auxiliaries without an identified worker/composite ratio. Recipient age alone never supplies an auxiliary worker PIA. S.770 survivors additionally require the shared ordinary-survivor/death basis; missing identification is neutral and flagged, while contradictory supplied information is rejected. No auxiliary age proxy is enabled. Identified, proxy and unmodeled results need separate population reporting.

Approximations and departures from the idealized design

  • Core's parameter schema requires named selectors as singleton lists, such as [age_65], rather than bare scalar strings.
  • Annual survey inversion assumes a full-year gross benefit and fully credited delayed-retirement credits. Partial-year awards, deferred same-year credits, withheld checks, binding family caps, dual entitlement and survey error can prevent unique inversion; the detailed monthly household ledger remains the appropriate route for identified histories.
  • Exact dime-rounded eligibility PIA has interval [inverse(z), inverse(z + 0.10)). Paid annual/survey amounts only identify this interval conditionally. annual_rounding_bound can propagate an explicit annual measurement-resolution interval through all baseline divisors. Core stores named AIME values as float32 ceilings, so represented endpoints can differ by one float32 step; the pure service retains exact rational endpoints for boundary work.
  • Pre-1983 initial-PIA rounding and unsupported positive records receive the explicit neutral/flagged treatment above rather than a fabricated inverse. Disability missing-onset years and incomplete birth dates remain labelled assumptions. No package values or administrative percentiles are encoded. M8's supplied progressive-indexing paths are independent of this adapter.

The claiming scenario changes the inference materially: C2's adjustment 0.70 recovers AIME $5,000 and a $1,165.248 unrounded annual gain; assuming one infers $2,978 and a $1,664.64 gain, about 43% larger.

Historical invariants and validation before round 1

Before round 1, full CI was green at 22bcfb497c4235cd0498adf38a09d873a33919e7. Run 40763309982 completed successfully, verified at 21:48:44Z on October 28: 33 checks passed and one documentation-deployment check was skipped. All 11 Baseline jobs, all nine Contrib jobs, all five Rest Python shards and their aggregate, Quick Feedback, and Microsimulation passed. All 33 original PIA-ratio YAML cases now pass, including the formerly failing disability proxy and the retained S.770 case.

First full CI before the corrections

The first full CI run at 27bd7fdb7803513aded985e35faec5d5b5f04d2f ran on the ready PR from 12:38–13:56Z on October 28. All 11 Baseline jobs passed, including ssa-usda (2,028 cases), as did Microsimulation, package/compatibility, PR validation, and five of six Rest Python shards. The remaining 103-file process in Rest Python shard 3 also passed 3,163 cases with 11 skips; that shard failed in the separate household-calculator differential process. Eight contributed jobs passed; the remaining contributed job reported the disability failure and stopped during the final retirement case.

The seven focused Python files passed 172 tests in CI, including all five H5/differential integration cases:

File under policyengine_us/tests/ CI result
unit/test_ss_pia_ratio.py 47 passed
unit/test_ss_pia_ratio_parameters.py 5 passed
unit/test_ss_population_retirement.py 8 passed
unit/test_ss_population_survivor.py 33 passed
unit/test_ss_worker_basis.py 12 passed
code_health/test_rest_python_groups.py 62 passed
core/test_ss_pia_ratio_inputs.py 5 passed

The PIA-ratio integration checks cover supplied H5 claiming months, the pure-input contract, float32 endpoint round-trips, and lever-off equality for the reported-situation and public H5 routes. The latter restore the original constant-one population hooks within the merged model and compare the requested benefit/downstream outputs and every reached baseline cached output; they do not claim an exhaustive country-system comparison. Existing core/test_social_security_inputs.py also passed in Rest Python shard 6. Microsimulation completed its three processes with 115 passed, 184 passed / 4 skipped, and 82 passed.

TOB is covered by passing CI. In Rest Python shard 5, job 122820893300, both baseline/gov/ssa/revenue/test_tob_revenue.py cases passed: generated split invariants (75.65s call) and preservation of supplied inputs and cached current-law tax in either calculation order (78.78s call). Their containing policy process finished with 982 passed in 630.95s. This supplies the clean result missing from the earlier local run capped at 1,800 seconds.

The first full run passed all four dependent PIA-ratio YAML cases and the first 22 retirement cases. Disability had three passes and the proxy-year failure described below. The final S.770 retirement case did not finish, so that run supplies no full-file retirement pass; the interrupted log supplies no survivor PIA-ratio file result.

Main merge and three CI fixes

  • Main merge: merge commit ff6d5e35fada97570c3f2f55453a12359d06f6aa brings in upstream main at bf108e931a, including Add S.770 section 8 investment and active income tax options #10402's narrower household-calculator reference exclusions. The merge was clean: no conflicts or resolved hunks.
  • Household-calculator reference: WithoutHouseholdCalculator removed parameter nodes that the reported-benefit population route now reads, raising AttributeError before legacy comparisons could run. Commit ae2d60bbbb retains gov.contrib.ssa.pia and gov.contrib.congress.s770.section_2 in that reference because these formula switches now serve the reported-benefit route too. Calculator-only variables remain removed, and the exclusion list remains a flat tuple of dotted paths. Production parameter access retains its normal schema requirements. The normal differential passed all eight tests. A supplementary reference-only mutant probe adds the numerically neutral 0 * person("ss_calculator_supplied_pia", period) dependency to ss_pia and uses the real reference Reform and Core builder. Its first attempt deferred before Python started (exit 75 at 20:19:00Z, load1 119.23). The retry started at 20:27:22Z with load1 59.82 under the required 2 GiB / 900-second cap, then timed out after 900.2s (full process 902.06s), exit 137, with no collection output or completed assertions. The runner restored the source and verified it against the saved copy and Git. Under the lane I/O rule this mutant is unrun: no detection proof is claimed, and a default-QoS hub rerun is needed.
  • Missing disability onset: the YAML expectation 2025 is correct. DESIGN-v3 A5.2/C1 and the labelled pre_reform sensitivity place an unidentified onset before the substantive PIA reform: the fixture's PIA change begins in 2026, so E = 2026 - 1 = 2025. Adjustment one and an inapplicable cohort reform give ratio one and an unchanged annual benefit of $12,000. Production instead took the parameter gate's historical YAML start (2000), producing E = 1999. Commit bc32567e49 finds the first operative change through the shared formula path, honoring its separate factor, bend-point and indexing gates, and applies the fallback only to positive records with a missing basis. The separate current_year sensitivity remains E = t (2026 in this fixture), and supplied onset/entitlement or worker-basis information retains precedence over either proxy. The new disability unit file passed all 12 cases through normal, unmodified python -m pytest; YAML results are recorded below.
  • Final S.770 retirement case: timed traceback probes of the isolated original case completed 1/1 in 82.59s at the pre-merge head 27bd7fdb78 after country loading (about 19 minutes total), and 1/1 in 100.83s on the merged tree with process exit 0. The merged probe's 30-second snapshots show Core's test_runner.py:447 cloning the baseline through recursive ParameterNode.clone/deepcopy during setup, followed by pytest garbage collection during cleanup. The shared parameters.py and pia.py files are byte-identical to upstream main; a native authored-subtree probe computes the fixture's PIA of 2313.6 in 0.000197s. The original 23-case file has 13 distinct parameter-input combinations retained in Core's cache. Each newly cached combination clones the baseline; a combination with an inline parameter reform adds a second full parameter-tree clone. Earlier CI processes reached 9,605 MB with six combinations and 10,878 MB with seven; the memory guard acts between files. Accumulated cache pressure is the inferred explanation for the file-level stall; RSS during the stalled final case was not measured. Commit 22bcfb497c splits the 23 unchanged case blocks across three files: the original factor file keeps eight cases / five combinations, claiming keeps five / five, and eligibility keeps ten / four. Every case block matches byte-for-byte, and the S.770 case remains in the original file with its pinned bend points and all assertions. Existing file isolation in both Contrib and Quick Feedback runs each file in a fresh subprocess, releasing its cache afterward. The split changes only YAML fixture organization, with no changes to Core, production PIA calculation, or CI configuration.

Local validation after the fixes

Local validation head: 22bcfb497c4235cd0498adf38a09d873a33919e7. These local results are separate from the passing jobs and failed cases in the historical CI run above; CI at the corrected head is recorded below.

Required file, one process per file Result at the corrected tree
unit/test_ss_calculator_differential.py 8 passed; pytest 1084.91s; full process 1763.81s; exit 0
policy/contrib/ssa/benefit_levers/social_security_disability_pia_ratio_factor.yaml 4 collected, 2 pass markers; killed at 4 GiB RSS after 1465.9s (full process 1469.23s); exit 137 at 19:02:02Z; remaining 2 unrun; no full-file pass
policy/contrib/ssa/benefit_levers/social_security_retirement_pia_ratio_factor.yaml (8 cases) 8 collected, 3 pass markers; killed at 4 GiB RSS after 830.9s (full process 833.37s); exit 137 at 19:15:56Z; remaining 5 unrun; no full-file pass
policy/contrib/ssa/benefit_levers/social_security_retirement_pia_ratio_factor_claiming.yaml (5 cases) 5 collected near the time limit; no completed assertions; timed out after 1800.4s (full process 1801.83s); exit 137 at 19:45:58Z; all 5 unrun
policy/contrib/ssa/benefit_levers/social_security_retirement_pia_ratio_factor_eligibility.yaml (10 cases) 10 cases defined; no collection output or completed assertions; timed out after 1800.6s (full process 1805.37s); exit 137 at 20:17:39Z; all 10 unrun
unit/test_ss_population_disability.py 12 passed; pytest 7.84s; full process 390.74s; exit 0

The disability YAML pass markers cover the supplied-onset case and the formerly failing missing-onset pre_reform case. The current_year and supplied-eligibility precedence cases did not complete, so neither has a result from this run.

Both Python files above used normal, unmodified python -m pytest. The differential process completed at 18:37:33Z with six NumPy warnings from an unchanged unemployment formula and no assertion failures.

env -u UV_FROZEN uv lock --check passed without relocking (150 packages resolved in 55ms). make format left 7,648 files unchanged and Ruff reported all checks passed.

Local Python processes use the required 4 GiB / 1,800-second cap (mutants: 2 GiB / 900 seconds), thread caps of four, passive OpenMP waiting, and country imports start only at load1 at most 100. Any process capped during import or collection is reported as unrun rather than credited with a result. No microsimulation runs locally.

CI at the corrected head

The corrected head was pushed as a fast-forward, and its entire full CI run completed successfully. The final 21:48:44Z snapshot has 33 passed, 1 skipped, with no failures or pending jobs. Baseline ssa-usda passed 2,028 cases. The Contrib other-shard-1 job passed every required YAML file and all its remaining tests.

At this corrected head, the seven focused files listed above again passed all 172 tests. The new disability unit file added 12 passes, and the household-calculator differential passed 8/8 independently. Completed-job logs provide these targeted results:

File under policyengine_us/tests/ Corrected-head CI result
unit/test_ss_calculator_differential.py 8 passed in 122.06s; Rest Python shard 3
unit/test_ss_population_disability.py 12 passed in 0.20s in Quick Feedback; also 12 passed in Rest Python shard 2
core/test_ss_pia_ratio_inputs.py 5 passed in 35.91s; Rest Python shard 4
policy/baseline/gov/ssa/revenue/test_tob_revenue.py 2 passed; calls 103.96s and 107.86s; Rest Python shard 5; containing policy process 982 passed in 791.80s
policy/contrib/ssa/benefit_levers/social_security_disability_pia_ratio_factor.yaml 4 passed in 48.46s in Contrib; peak RSS 5,145 MB
policy/contrib/ssa/benefit_levers/social_security_retirement_pia_ratio_factor.yaml 8 passed in 84.08s in Contrib, including the retained S.770 case; peak RSS 8,224 MB
policy/contrib/ssa/benefit_levers/social_security_retirement_pia_ratio_factor_claiming.yaml 5 passed in 79.85s in Contrib; peak RSS 7,579 MB
policy/contrib/ssa/benefit_levers/social_security_retirement_pia_ratio_factor_eligibility.yaml 10 passed in 66.42s in Contrib; peak RSS 7,035 MB
policy/contrib/ssa/benefit_levers/social_security_dependents_pia_ratio_factor.yaml 4 passed in 48.88s in Contrib
policy/contrib/ssa/benefit_levers/social_security_survivors_pia_ratio_factor.yaml 2 passed in 30.41s in Contrib

The four required YAML files also passed twice in Quick Feedback, with first-run times of 41.93s, 71.47s, 69.18s, and 66.27s respectively. In Contrib, every individual case in the original retirement file took at most 16.49s, bounding the S.770 case at 16.49s or less. The duration rows omit case names, so its individual timing is not separately identified. All nine SSA batches exited 0; the original retirement file's complete process took 131.9s including setup and cleanup.

Interaction with #10486

At the checked heads, the static overlap check found no file changed by both branches, and a trial merge was clean. They interact in the public component formulas and tools/social_security_benefit_levers.py: #10486 preserves the reported-route joint_cola_factor * pia_ratio_factor and bypasses these population factors for calculated sources. C imports only the source enum from that shared helper; its inversion uses the unreformed statutory COLA ledger, so E3 withholding never enters the baseline divisor. Their reported-route factors compose multiplicatively. This is a static compatibility check. The round-1 review of #10486 then ran the combination: a trial merge of the two heads was clean; on the reported route the result equals the reported benefit times this PR's PIA ratio (1.022873 in its case) times #10486's joint factor, each factor identical to its single-PR run; and this PR's six lever YAML files pass (33 cases).

Hub microsimulation impact (current head)

A real microsimulation on the default dataset, main at the merge base bf108e931a against this PR's head fea0d26ef9, for 2026. The runs went one at a time under the shared heavy-job lock. Sums are weighted.

Output 2026 change 2026 records changed (weighted)
social_security +0 0 (0)
social_security_retirement +0 0 (0)
social_security_disability +0 0 (0)
social_security_survivors +0 0 (0)
social_security_dependents +0 0 (0)
taxable_social_security +0 0 (0)
ssi +0 0 (0)
state_income_tax +0 0 (0)
income_tax +0 0 (0)
household_net_income +0 0 (0)
household_benefits +0 0 (0)

Comparison files are in fixes/10484-impact/ on the hub host.

impact: none under current law (contributed reform). The hub's microsimulation at fea0d26ef9 against main bf108e931a changes no 2026 output (section above).

axiom: n/a: contributed reform, not enacted law

# Conflicts:
#	policyengine_us/tests/code_health/test_rest_python_groups.py
MaxGhenis and others added 9 commits October 27, 2026 05:29
#10400 was squash-merged as 9969420, so Git's merge base is the
pre-#10400 commit d453360 and every file #10400 added and this branch
then changed shows as an add/add conflict. Each was resolved against
#10400's head a6dcc92:

- The four social_security_*_pia_ratio_factor.py variables, Makefile and
  tests/code_health/test_rest_python_groups.py: main's copy equals
  #10400's head, so this branch's filled version (built on that head) is
  kept.
- tests/core/_social_security_state_backend.py: this branch's copy equals
  #10400's head and main changed it afterwards (#10504, Core 3.33.13
  names), so main's version is kept.
- changelog.d/ss-benefit-levers.added.md: main's release compiled and
  removed it; removed here too.

A merge-tree run with a6dcc92 as the base gives the same tree apart
from the version files (CHANGELOG.md, pyproject.toml, uv.lock), which
this merge takes from main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MaxGhenis
MaxGhenis marked this pull request as ready for review October 28, 2026 12:38
@MaxGhenis
MaxGhenis merged commit 78cdba8 into main Oct 30, 2026
35 checks passed
@MaxGhenis

Copy link
Copy Markdown
Contributor Author

US + core hub merge audit, us#10484 at fea0d26ef98a6771e946f621e8edd2bff11a046c (squash): add the reported-benefit Social Security PIA ratio lever, a contributed reform that is off by default.

  • Reviews: GPT-6.1 Sol, two rounds.
    • Round 1 at 22bcfb497c requested changes (~/reviews/us-hub/reviews-gen/us-10484/review-r1.md). Its one P2: the age_62, age_65, fra and age_70 claiming scenarios left records with an exact birth date unflagged as proxies. Its coverage note asked for three more current-law routes.
    • A hub build fixed both (aa5d225ed8 to fea0d26ef9).
    • Round 2 APPROVE at fea0d26ef9 with no findings (Subfleet job 20261029-010717-hub-us10484-r2-g; review-r2.md beside round 1). It reran the round 1 probe (E 2018, a 41/45, proxy true), hand-checked the four claiming adjustments, confirmed the new route tests compare against main's constant-one hooks rather than the head against itself, and confirmed the composition test fails when a reformed COLA enters the divisor. The three changed test files pass locally: 14, 10 and 1.
  • Mutants: the hub ran round 1's four mutants and the build's fix-removal mutant at default QoS on this head, one process each under 2 GB and 900 s (~/reviews/us-hub/reviews-gen/hub-mutants-1029/RESULT.md). Five were killed by real assertions or the intended VariableNotFoundError. The core-file variant of the COLA-divisor mutant hit the 2 GB cap during import; the unit-file variant kills the same mutation. All seven clean test files pass.
  • Gates checked live at merge:
    • gh pr checks exits 0;
    • the latest Pull request run at the head (40796218956) concluded success;
    • MERGEABLE;
    • not a draft;
    • no reviewer's latest review requests changes;
    • head pinned.
  • Overlap with main: CI ran on base bf108e931a. Main is now 903a5b88d5, 83 commits later: LIHEAP, Medicaid ABD and MSP, CHIP pregnancy, tax-credit fixes, and Add contributed owners draw SECA reform #10483's owners-draw reform in gov/contrib/ssa/owners_draw. None touches this PR's areas, and the merge-tree is clean.
    • Whatever in main reads social_security is unaffected by default: this PR changes that variable only when its lever is on; with every lever off each factor is exactly 1, which rounds 1 and 2 tested on four routes, and the microsimulation below confirms it.
    • The hub merged the head into 903a5b88d5 (tree 36ac1d5392) and ran the shared registries this PR edits: test_rest_python_groups.py (62 passed), the shrink-only guard (10 passed) and test_source_conflicts.py (103 passed).
  • Impact: none. The hub's full-file microsimulation, main at the merge base bf108e931a against fea0d26ef9 for 2026, changes no output: social_security and its four components, taxable_social_security, ssi, state_income_tax, income_tax, household_net_income and household_benefits all move by $0 on 0 records (~/reviews/us-hub/fixes/10484-impact/compare.2026.json). The body's impact: line says so. The run went on the guest heavy slot the triple-lock reservation granted.
  • Axiom: n/a. A contributed reform, not enacted law.

@MaxGhenis
MaxGhenis deleted the ss-pia-ratio-lever-c branch October 30, 2026 04:33
MaxGhenis pushed a commit that referenced this pull request Nov 5, 2026
Assertions are unchanged; only inputs are restated.

- nm premium assistance integration Scenarios 5, 6 and 11: the MIH gate
  reads Marketplace enrollment (is_aca_coverage_family_member), and on
  current main these unsupplied households compute as Medicaid-eligible
  with other qualifying coverage, so they no longer enroll. Supply
  is_aca_marketplace_enrollee alongside pays_aca_premium, as the earlier
  merge did for the legacy MIH fixtures.
- claimable-filer PTC invariants: since #10484 a reported Social
  Security component must be nonnegative, so the seeded dependent with
  -30,000 of survivors benefits raised. Supply the signed amount as the
  social_security total instead, as aca_magi.yaml does, keeping the
  signed-income coverage.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LwQq6FNAxaBM1PuY7CjDL5
DTrim99 added a commit that referenced this pull request Nov 13, 2026
… credit family, and apply each state premium program's rule (#10041)

* Make head_is_dependent_elsewhere consumers independent of the head label

The federal standard deduction and 17 state formulas read only whether the
tax-unit head is claimed elsewhere, so a joint return where one spouse can be
claimed was taxed differently depending on which spouse was labelled head.
Each formula now applies its jurisdiction's rule for that case (either spouse,
single filers only, per spouse, or only when every filer is claimed), using
two new label-independent helpers. Adds swap-pair YAML cases and a Hypothesis
property test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Keep tax units without a filer eligible where only claimed filers are barred

The New Mexico, Maine and Hawaii renters gates counted filers who are not
claimed elsewhere, so a tax unit with neither a head nor a spouse (252 in
the default dataset) looked like one whose every filer was claimed. A new
helper, every_filer_is_dependent_elsewhere, requires a claimed filer and no
unclaimed one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Address review: Hawaii worksheet earnings, NM same-filer age, childless EITC

- Hawaii's dependent standard deduction uses earned income net of the
  deductible part of self-employment tax, as the N-11 worksheet does.
- New Mexico's medical care credit needs a filer who is both 65 or older
  and not a dependent when a filer is a dependent elsewhere (NMSA 7-2-18.13).
- The federal EITC without a qualifying child requires that no filer can be
  claimed as a dependent (IRC 32(c)(1)(A)(ii)(III), Publication 596), so
  Missouri's working family credit no longer reaches such a couple.
- Hawaii's food/excise credit keeps minor children receiving public support
  (HRS 235-55.85(c)) on a joint return where one spouse can be claimed.
- Comments label the readings the law does not settle, and the property
  test covers the EITC and the food/excise exemption amount.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Allow a cent of rounding in the Hawaii self-employed joint pair

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Address review round 2: worksheet earnings, minors' own status, input meaning

- The federal and Oregon dependent worksheets use earned income net of the
  deductible part of self-employment tax, as Hawaii's now does.
- Hawaii's food/excise minor-child count excludes children who can be
  claimed by another taxpayer and the filers themselves (Form N-311 line 3).
- claimed_as_dependent_on_another_return documents what it stands for: a
  §151 deduction for the person is allowable to another taxpayer, so a
  person whose would-be claimer files only for a refund is not one
  (Publications 501 and 596); rules on actually being claimed read it too.
- Hawaii's renters comment labels the mixed joint reading as an inference;
  the Hawaii dependent threshold cites HRS 235-2.4(a)(3) on its page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Merge the Hawaii deductions references after syncing main

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Apply the federal rules for a filer who can be claimed as a dependent

A filer who can be claimed on another return is treated as having no
dependents (IRC 152(b)(1); on a joint return either spouse counts) and has no
personal exemption (IRC 151(d)(2)); one who is claimed gets no education
credits (25A(g)(3)), student loan interest deduction (221(c)) or recovery
rebate (6428(d)(2), 6428A(d)(2), 6428B(c)(2)). The model read none of these.
Now the child tax credit and credit for other dependents, the under-13 child
and dependent care qualifying person, exemptions_count and its RI, DE, OH, OR,
WI, HI and NM readers, the recovery rebates, the education credits and the
student loan interest deduction apply them symmetrically for joint returns.
Georgia keeps its own counts; the HI, WI and Treasury exemption reforms
follow the corrected count.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Keep a filer who can be claimed elsewhere out of the premium tax credit family

IRC 36B(c)(1)(D) excludes anyone another taxpayer can claim from being an
applicable taxpayer, and 26 CFR 1.36B-1(d)(2) leaves such a spouse out of a
joint return's family. Add is_aca_tax_family_member and aca_tax_family_size,
measure household income against the poverty line for that family (aca_fpg,
aca_magi_fraction), gate is_aca_ptc_eligible and the below-FPL immigration
exception on it, and price the credit on the coverage family's benchmark
(aca_ptc_slcsp, which equals slcsp whenever every enrollee is in the family).
The NY/VT family-tier logic becomes shared functions so the benchmark can
apply it to the coverage family. The three ACA reforms that override
is_aca_ptc_eligible keep the gate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Apply each state premium program's own rule to an enrollee outside the tax family

Massachusetts, Connecticut, Colorado, Maryland, California, New Mexico and
Vermont require each enrollee to be eligible for the federal credit, so the
gate flows through is_aca_ptc_eligible and their wraps use the coverage
family's benchmark. New Mexico's Middle Income Household component and New
Jersey Health Plan Savings require every federal criterion except income, so
they now read the tax family too. Washington's Cascade Care Savings pays its
non-federally-subsidized amount (Group 2) to a QHP-eligible enrollee without
a federal subsidy, so a claimable enrollee moves from Group 1 to Group 2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Test the premium tax credit invariants for claimable filers

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Cite 36B(c)(1)(D) and 1.36B-2(b)(3) for what each says

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Address the federal claimable-filer review

- Child and dependent care: childcare expenses do not count on a return with a
  claimable filer unless a child under 13 still qualifies (IRC 21(b)(2)(A)(ii)).
- Tuition and fees deduction: not allowed to a filer who can be claimed (IRC
  222(c)(3)), so the education credit bar no longer makes such a filer eligible.
- Recovery rebates: the Armed Forces exception waives the identification rule
  only, not the exclusion of a spouse who is another taxpayer's dependent.
- Georgia: the contributed refundable credit and SB 520 reforms count the same
  children as ga_ctc_potential through a new ga_ctc_eligible_child.
- Education credits and student loan interest read the claimed input directly,
  since IRC 25A(g)(3) and 221(c) turn on an actual claim.
- One reference per source document; quote IRC 24(h)(4)(A) exactly.
- Tests: mixed-recipient care, tuition deduction, military rebates, Georgia
  refund cap, and the swapped New Mexico rebate case; the property test now
  covers the state readers of the exemption count.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Separate dependency facts and fix Hawaii qualified-person counts

* Clarify claimability outside the current tax unit

* Read the split dependency inputs from #10024

#10024 now separates three facts: is claimed, can be claimed, and the would-be
claimant's filing exception.

- IRC 152(b)(1) gates (child tax credit, credit for other dependents, under-13
  care child and its expenses, dependents in exemptions_count, ARPA dependents,
  Ohio dependents, the Hawaii and Wisconsin reforms) read
  head_or_spouse_is_dependent_elsewhere_without_filing_exception, so a filer
  within the Publication 501 exception keeps their dependents.
- Own exemptions, recovery rebates and the tuition deduction read claimability.
- Education credits and student loan interest keep reading the claimed input.
- Tests: the filing exception and a filer who can be claimed but is not.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Follow the corrected exemption count in three Hawaii credits

#10024's food/excise credit, Act 115 rebate and renters credit took claimable
filers off exemptions_count themselves. exemptions_count now leaves them out
(and, outside the filing exception, the return's dependents), so those credits
read it as it is; the filing-exception cases were one exemption short.

The renters credit also leaves out a dependent who can be claimed by another
taxpayer (Schedule X counts only people who cannot be), as the food/excise
credit already did.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Address the second federal claimable-filer review

- Education credits: a dependent student is not eligible on a return whose
  filer can be claimed outside the filing exception (IRC 25A(f)(1)(A)(iii),
  152(b)(1)); the filer's own eligibility still turns on an actual claim.
- Recovery rebates: no credit when every filer is a dependent of another
  taxpayer (IRC 6428B(a)); the CARES and CAA child prerequisite is a spouse
  with a valid SSN, whether or not that spouse is an eligible individual.
- Child and dependent care: cdcc_qualifying_childcare_expenses holds the
  expense rule, and the single-parent work requirement reform and California's
  expenses read it.
- References: Georgia HB 136 page 3; one entry per recovery rebate statute;
  quote IRC 24(h)(4)(A) exactly in the test comment.
- Tests: dependent students, the two rebate cases, the reform and California
  expenses, and the Hawaii, Wisconsin and Treasury reforms with a claimable
  filer under both labellings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Address the third federal claimable-filer review

- Education credits: is_barred_from_education_credits_by_dependency holds the
  claimed-filer and dependent-student rules; both eligibility formulas and the
  reconciliation SSN reform's Lifetime Learning Credit read it, so the reform
  no longer turns a barred student's tuition into that credit.
- Child and dependent care: childcare counts when any child under 18 is still a
  qualifying individual, so an incapacitated child aged 13 to 17 keeps it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Give the spouse without an SSN a card type in the recovery rebate test

Setting meets_eitc_identification_requirements on one person made it an input
for every person, so the other spouse lost their SSN too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Address review r1: claimability, household income, premium cap, CSR, role-less units

- is_aca_tax_family_member reads claimable_as_dependent_on_another_return
  (#10024's split input: 36B(c)(1)(D) and 1.36B-1(d)(2) turn on being
  claimable, and Form 1040 line 12a, which Form 8962 line 1 keys on, has no
  refund-only carve-out). The return keeps its dependents when the would-be
  claimant meets the refund-only filing exception (Pub 501, Dependent
  Taxpayer Test), a return with no applicable taxpayer has no family, and a
  tax unit with neither a head nor a spouse uses each member's own
  claimability (a lone claimable minor no longer gets the credit).
- aca_magi leaves out the tax-exempt interest and Social Security of the
  return's dependents who are outside the tax family (26 CFR 1.36B-1(e)(1)).
- used_aca_ptc is capped at the coverage family's share of the selected plan
  premium (new aca_ptc_coverage_family_premium; 26 CFR 1.36B-3(d)(1)(i),
  (h)(1)), not the whole policy's premium.
- marketplace_csr_eligible applies 45 CFR 155.305(g)(3): the model prices one
  policy per tax unit, and a policy that also covers an enrollee without
  credit eligibility gets no cost-sharing reductions.
- aca_fpg documents that it sizes the family for the tax year; the NJHPS
  exclusion is labelled an interpretation; one reference per source in
  is_aca_coverage_family_member.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Test the review r1 fixes and tighten the invariant test

YAML: refund-only exception (family keeps the child), single claimable filer
with the exception (no family), claimable but not claimed, lone claimable
and unclaimed 17-year-old filers, household income without an out-of-family
child's tax-exempt interest, the coverage-family premium cap (silver and
bronze), CSR under the family-policy rule, Colorado's binding residual
($420), and the tax year's family size against a supplied prior-year size.
Test inputs now use claimable_as_dependent_on_another_return.

Property test: Hypothesis runs every year 2021-2026 and draws claimable-but-
unclaimed spouses and the filing exception; the credit's monotonicity
exemption is limited to crossing the 100% floor or dependents' income leaving
household income; the benchmark check compares enrolled people, not counts;
new identities for household income, the premium cap and CSR.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Address review r2: role-less filers, coverage-family pricing and allocation, MAGI floor

- A tax unit with neither a head nor a spouse is filed by its oldest member.
  When that member can be claimed elsewhere, nobody is in the tax family.
  Before, a claimable 17-year-old filing with an infant got $12,000.
- The coverage family is priced on its own. Its children are ranked for the
  three-oldest-children rule (45 CFR 147.102(c)(1)), and its family tier is
  built from its own members.
- A shared premium is allocated by each family's benchmark (26 CFR
  1.36B-3(h)(1)). The denominator is the coverage family's benchmark plus the
  benchmark of the enrollees outside it, not the whole policy's tier. An empty
  coverage family gets no share of the premium.
- Out-of-family dependents' tax-exempt interest and Social Security are
  removed before the single zero floor. A negative benefit no longer cuts
  household income.
- is_aca_marketplace_enrollee (enrolled) is split from pays_aca_premium
  (charged an age-rated premium). The family-tier child tests no longer
  depend on payment.
- Tests: YAML for each case under both head/spouse labellings. The property
  test now gives dependents tax-exempt interest and Social Security. It checks
  aca_magi against an expectation built from the inputs, and it exempts only
  that removal from monotonicity. Monotonicity runs under Hypothesis in every
  year 2021-2026. The "unchanged" identities apply only to returns with a
  head or spouse.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Correct PTC test fixtures after merging main

* Supply consistent premium and enrollment test inputs

* Set Marketplace enrollment in New Mexico MIH test fixtures

* Check CSR conditions for every Marketplace enrollee

* Preserve ACA MAGI inputs and infer minor joint filers

* Preserve supplied ACA prices and rank covered children

* Allocate shared ACA premiums by coverage month

* Count enrolled nonpayers in Washington Cascade Care Savings

* Complete partially inferred joint ACA filers

* Preserve supplied child predicates for nonpaying enrollees

* Divide California's premium subsidy by the tax family's poverty line

After the merge, aca_magi_fraction divides by aca_fpg (the prior-year
guideline for the section 36B tax family, Form 8962 line 4), while the
California band test and rate lookup still divided by tax_unit_fpg for
the prior year, which takes the whole tax unit's size. For a couple
with one claimable spouse that put $15,650 and $21,150 in one formula.
Program Design (d)(10) gives family size its section 36B meaning, so
both California reads now use aca_fpg.

Tests that supplied the denominator as tax_unit_fpg for the prior year
now supply aca_fpg for the test's own period, with the same amounts and
unchanged expected outputs: 19 pins in ca_premium_subsidy.yaml, 17 in
ca_premium_subsidy_applicable_percentage.yaml, 20 in
ca_premium_subsidy_eligible.yaml, 7 in integration.yaml, and the two
unit test files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LwQq6FNAxaBM1PuY7CjDL5

* Add witnesses that California uses the tax family's poverty line

A couple with one claimable spouse has a tax family of one and a tax
unit of two, so the two poverty lines put it in different places. Five
YAML cases pin where it lands over the one-person line: 2026 at $20,000
(eligible, rate 0, subsidy 420), $25,000 under both labellings (rate
3.622%, subsidy 250.45), $27,000 (not eligible), and 2027 at $35,000
(219.3%, not eligible). Each was hand-computed first; each lands
differently over the tax unit's two-person line.

The 2027 case holds is_medicaid_ineligible_due_to_work_requirement
false, as the other coverage flags are held, so Marketplace enrollment
turns on income alone.

A property test draws incomes for the same couple in 2026 and 2027,
lets the model compute aca_fpg, and checks eligibility and the rate
against the Design bands and interpolation over the transcribed
one-person guideline in exact arithmetic.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LwQq6FNAxaBM1PuY7CjDL5

* Name the four 18-and-17 joint-filer ACA cases by their household

The names recorded which review round added them; they now say who
files, who is claimable and whether roles are inferred or explicit.
Assertions are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LwQq6FNAxaBM1PuY7CjDL5

* Keep two PR fixtures valid on current main

Assertions are unchanged; only inputs are restated.

- nm premium assistance integration Scenarios 5, 6 and 11: the MIH gate
  reads Marketplace enrollment (is_aca_coverage_family_member), and on
  current main these unsupplied households compute as Medicaid-eligible
  with other qualifying coverage, so they no longer enroll. Supply
  is_aca_marketplace_enrollee alongside pays_aca_premium, as the earlier
  merge did for the legacy MIH fixtures.
- claimable-filer PTC invariants: since #10484 a reported Social
  Security component must be nonnegative, so the seeded dependent with
  -30,000 of survivors benefits raised. Supply the signed amount as the
  social_security total instead, as aca_magi.yaml does, keeping the
  signed-income coverage.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LwQq6FNAxaBM1PuY7CjDL5

* Name the ACA test cases for their households

Drop the review-round labels from twelve case names in the ACA and
Washington Cascade Care YAML. The assertions don't change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Correct the comments and names that #10041's last review flagged

The California 2027 case holds the work-requirement flag false because it
supplies aca_magi without income, so the comment now says that. The eligible
property file's docstring splits two sentences it had joined, and the invariant
file's helpers now describe their cases.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Apply the tax-family rules in the ACA minimum premium reform

The reform came from main (#10681) in the last merge and still read the
whole tax unit's benchmark (slcsp) and selected premium. It now reads the
coverage family's benchmark (aca_ptc_slcsp) and its share of the premium
(aca_ptc_coverage_family_premium), as the baseline credit does, so an
enrollee who can be claimed on another return stays out of the credit.

The reform's tests state enrollment (is_aca_marketplace_enrollee), as this
branch's used_aca_ptc tests do, and a new case covers a claimable spouse:
$5,016.40, the baseline credit, where the reform gave $11,016.40.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Count supplied premiums and payers as enrollment, per Pavel's review

A supplied pays_aca_premium of true marks an enrollee, since everyone who
pays an age-rated premium is one. A supplied premium for a tax unit in which
the model finds no enrollee, with enrollment not supplied, is the tax
family's, as before enrollment was modeled. This restores #10773's four
household tests unchanged. The minimum premium reform gets a case in which
the cap binds, so the coverage family's premium is pinned.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Pin the supplied-premium rule and count monthly premiums, per Pavel's review

A supplied monthly premium now counts as a supplied premium. New cases pin
each condition of the rule (enrollment supplied, an enrollee found, a tax
family present), the monthly input, and the minimum premium reform's
used_aca_ptc cap. The changelog names the two supplied-input rules.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Close the round-1 review items on #10041

Address the round-1 items that Pavel's 2026-11-13 review carried forward.

- New cases pin the even-split fallback for a supplied annual premium, the
  CSR test of a premium payer's supplied PTC eligibility, and is_aca_filer's
  fallback when every member is a supplied dependent.
- aca_ptc_coverage_family_premium returns early when no tax unit has an
  enrollee outside its tax family; the result is unchanged.
- slcsp_age_curve_amount_person_uncapped uses has_input_for_period, and
  is_aca_tax_family_member reads is_dependent_elsewhere_without_filing_exception.
- California references reach PDF page 3 for (d)(7)(B), (d)(10) and (d)(11).
- The Colorado source-conflict candidate gets its URLs, quotes and code paths,
  and a new candidate records the Exchange "tax filer" reading.
- Case names drop review-round prefixes, is_aca_tax_family_member.yaml drops
  its YAML anchors, and the NM and tax-family-size wording is fixed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: David Trimmer <david@policyengine.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant