Repository navigation
research: exclude 15-call five-b UT4 splits across dirty workspaces - #2828
Merged
Mister-Meeseeks merged 1 commit intoOct 16, 2026
Conversation
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
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.
Summary
Resolves the explicit 15-call five-$b$ weighted-tariff handoff formulated by Gareth Davidson ($\operatorname{diag}([z], [uz], I_{\text{rest}})$ in $\mathbb{F}_2[\mathrm{UT}_4(\mathbb{F}_2)]$ across arbitrary finite restored dirty workspaces ($r \ge 2$ ):
@bitplane) in PR #2314 (research/ut4-mixed-weighted-boundary) and PR #2343 (research/register-pairing-compression, Discussion #2019 comment) for(6,5,4)and(4,5,6)to Two Roles (Lemma 1): Because(5,5,5)(Lemma 2): All common-orientation excess profiles compress to two roles. For the remaining two opposite-orientation three-role modes (Case I:Case II: $(0, 1, 1, 0)$), in5,664compatible(5,5,5)profile pairs;AC,ACB,BACreceives only the rank-one cross-role contraction.9,721,47,521, and174,670profiles;55,566,907,200, and15,471,918realizations).(4,5,4)(5,536words) and PR Prove a sharp weighted region for the mixed UT4 target #2314(5,5,4)/(4,5,5)(211,968/209,920words) byte-for-byte, and exhausts(6,5,4)(3,376profile pairs,6,049,824words),(5,5,5)(5,664profile pairs,8,655,168words), and(4,5,6)(3,280profile pairs,5,874,848words) — 20,579,840 new 15-call words, 0 survivors.(5,5,5)censuses: Across all5,664active profile pairs, both Case I and Case II leave17,864dirty profile pairs passing(4,6,4)word is globally optimal on the expanded coneScope & Attribution
scripts/choose_research_task.py(seed = 09aa8c1ab0ddd939f9b2d42697e50a37,task_id = bit-new-register-model,priority_revision = 5); tracked in Discussion #2019 comment 18961496.@bitplane, PR Research: sharp mixed UT4 root tariffs with arbitrary dirty workspace #2027, PR Prove a sharp weighted region for the mixed UT4 target #2314, PR Research: body-dependent BIT stock cutoff and fixed-point counterexample #2343), Nick Petalas (@petalas, PR Research: prove the mixed UT4 z/uz endpoint needs fourteen calls #2175), ToikY (PR Research: UT4 central-target tariff bound with arbitrary dirty workspace #1662, PR Research: UT4 two-target unit count is independent of dirty workspace #1680), CinnaDavis /1337isnot1337(PR Scoped negative theorem: three coordinate swaps need nine calls with arbitrary dirty workspace #1541), and Aaron Wang (@navinor, PR Research: no 14-call two-target UT4 word on two roles; with CrocSwap/integer-mult-bounds#1680, at least 15 calls for every r (no new kappa) #1690).Verification
python3.12 -I -B scripts/research_package.py --package research/ut4-fifteen-call-five-b python3 -B -m unittest discover -s tests -p 'test_research_*.py'Both
verify.py(PASS_UT4_FIFTEEN_CALL_FIVE_B, receipt9b7ad621553bb1517c52128298e5ea66f3841f51cebed67dc9839d0b6ffb65bf) andcontrols.py(PASS_UT4_FIFTEEN_CALL_CONTROLS) complete in ~8 seconds total.