Exclude farm_income from export-mass parity: unpinned free dimension (#441)#442
Merged
Conversation
Build M sparse attempt 12 (6584dfa; first run under the #437 batched report) failed exactly one gate group: farm_income exported $23.45B against the live-default reference's $62.39B (-62.4%, beyond +/-50%). Full adjudication (populace#441), the #433 doctrine: - Nothing pins the column: the v8 Ledger feed carries zero farm facts and the compiled 2024 registry zero farm specs, so the reference's $62.39B is an incidental artifact of the incumbent solve (the estate_income class). - The pool carries 353 one-signed nonzero persons ($10.24B at base weights, byte-identical pre/post-#435 - distinct from the farm_operations_income signed leaf), 109 of them in the frozen rmloss100+keogh-swap selection ($4.10B). The band floor ($31.19B) would demand a 7.6x stretch of those 109 records toward the incidental value. - Unpinned exports wander exactly as populace#432 describes: Build J -25.6% in-band, attempt 11 -43.2% in-band, attempt 12 -62.4% out, all on an identical pool. The exclusion lifts when SOI Table 1.4 farm net income (Schedule F) is identified as a Ledger target (populace#441 remedy 2). Register entry only - the parity gate's behavior for non-excluded columns is unchanged (the #433 pattern). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #441
Why
Build M sparse attempt 12 (
populace-us-2024-buildm-sparse-rmloss100-6584dfa-20260716T105513Z, the first run under the #437 batched terminal report) failed exactly one gate group:Adjudication (reference-wrong, the #433 doctrine — full detail in #441)
farm_incomemassgrep source_measure_id.*farm→ none), zero farm specs in the compiled 2024 registry. The reference level is an incidental artifact of the incumbent solve — theestate_incomeclass.farm_income(one-signed, PUF-era concept) is notfarm_operations_income(the QBI base −31%/−40% vs targets and JCT; add per-component repeal-revenue benchmarks (amount residuals can't see yield gaps) #298/Pin signed sparse QRF outputs' net mass to the donor instrument (farm sign flip; #432) #435 signed Schedule F leaf) — Pin signed sparse QRF outputs' net mass to the donor instrument (farm sign flip; #432) #435 didn't touch it.What
Register entry in
US_EXPORT_INPUT_MASS_REVIEWED_EXCLUSIONS+ doctrine-comment line, citing #441. The exclusion lifts when SOI Table 1.4 farm net income (Schedule F) is identified as a Ledger target (#441 remedy 2). Data-to-the-gate only, like #433 — no behavior change for non-excluded columns; builder test suite passes.🤖 Generated with Claude Code