Repository navigation
Prove the UT3(F4) central floor survives nilpotent calls (no new κ) - #4849
Merged
Merged
Conversation
This was referenced Oct 22, 2026
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
Resolve Open next question 1 of Wentao Li's #3788. The six-label UT3(F4) central triple still has exact minimum twelve after admitting every nonzero binary rank-one coupling, including nilpotents, and arbitrary restored dirty workspace.
Claim type: scoped algebraic proof with exact finite corroboration. The same written argument gives the 4d central-target law over every characteristic-two address field. The predecessor's coordinate upper word retains its credit; the new contribution is the enlarged-alphabet lower bound. No predecessor executable was replayed. No new kappa or selected-frontier change.
Package
research/ut3-f4-nilpotent-tariff/was produced by Nick Petalas. Independent human and formal proof-kernel review are unclaimed. Credit Wentao Li #3774/#3788, Cinna Davis #2261, Arham Tahir #1589, Hanson Sun #1607, steph4n-gh #1573, James Reed #3783-#3786 and the retained register-model lineage. Exact source pins and full attribution are in the package.Advance claim.
Evidence
Before, #3788 explicitly excludes non-idempotent couplings and leaves this question open. After, the quotient over the address coefficient field proves at least six X calls and six Y calls without scalar idempotence or a workspace bound.
Local CPython 3.12 checks pass on
cb5230dea14ba310d55d92396c9f0bb28a34bf42:From the repository root:
Expected markers:
PASS_UT3_F4_NILPOTENT_TARIFF minimum=12 nX=6 nY=6,PASS_REGISTERED_RESEARCH_PACKAGE, andPASS_RESEARCH_COMMIT_BYTES. Substitute another CPython 3.12 path outside this environment.Limitations and unrun obligations
The arbitrary-field and arbitrary-workspace statements are written algebraic proofs, with F4 finite corroboration. No proof-kernel formalization, native supplier realization, recursive rank identification, compiler/hosting/precision/tape bill, selected cold replay or outer analytic transfer was run. No complete multiplication theorem is claimed. The formal alphabet's physical price remains unknown. There are no locally unrun registered commands. The selected conditional kappa stays 0.00302015.
Open next questions
Can a physically realizable additional address operation escape the exact axis-alphabet tariff with a favorable complete bill? First pin a literal entry/call/exit contract and charge its frames, preparation, dirty restoration, hosting and precision. A legal physical realization and recursive price remain the blockers.
Related open work
Before DONE, this account's open PRs created since the advance CLAIM were refreshed at 2026-10-22 22:02 UTC. No additional PR in that snapshot studies the same F4 nilpotent central-triple floor. The fixed-factor workspace and S3 rigidity submissions address different quantities or groups; no shared numerical value is compared or recomputed. Canonical main remains
624de9dc66858af0945e5f8a0942488d62280d43, priority revision 7, at the final fetch. Remote overlap and distinctive merged/main searches have the coverage limits recorded in the package.CI notes
Both hosted checks passed on publication head
cb5230dea14ba310d55d92396c9f0bb28a34bf42in run 39861008611: planning in 3m23s and registered package replay in 1m33s. Run metadata confirms that exact head, completed status and success. The package job executes both warning-strict normal and optimized registered commands. These automated checks certify the bounded replay; independent human and formal proof-kernel review remain unclaimed.Merge danger
Door: two-way. Blast radius: package.
Six isolated research files and an opt-in replay manifest. No shared implementation, frozen predecessor, selected source or frontier changes.