Repository navigation
Research: actual Turyn profiles have asymmetric block rank 9d (no new kappa) - #1037
Draft
yonghaozheng64-commits wants to merge 1 commit into
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.
For every characteristic-two field and every positive integer block size d, each complete canonical 7,680-port Turyn profile has minimum asymmetric block-fitting rank exactly 9d, with diagonal blocks I_d and zero blocks on actual active edges.
This contribution consistently lifts PR598's per-profile parity-clique restrictions to twenty actual ports in each profile, then independently verifies the upper fit on every complete profile. DominikScholz / PR598, incorporated head 615ca6f, deserves credit for the general parity-projector argument, the predecessor geometry, and the nine-dimensional upper map. The new part is the consistent actual-port lift and independent full-profile reconstruction. PR898 accelerates a historical affine Leech-minor audit; it supplies neither this lift nor the asymmetric-block result, and none of its code is reused. The exact comparison and pinned primary sources are in research/turyn-profile-parity-lift/COMPARISON.md.
Scope: this is a per-profile result. It does not establish unrestricted global rank 27, exclude arbitrary global 25-dimensional fittings, improve kappa, supply a multiplication supplier, or constitute a formal verification of the full multiplication theorem. The ordinary degree-three polynomial-calculus appendix independently corroborates the different earlier 24-port symmetric obstruction over all characteristic-two fields; its 57-variable-edge core is inclusion-minimal with fixed anchors, not globally edge-minimum.
Draft integration limitation: the original validation base is 91a2094. Its preserved baseline deliberately pins the historical PR799 selected record. This branch applies the identical 44 added files on main 2921874, whose selected record is different. The baseline checker on this branch fails with "Source pin mismatch: certificates/selected-result.json". Context adaptation is outstanding; this PR is not presented as merge-ready. No selected record, source pin, frozen baseline, upstream source, or unrelated file has been overwritten or relaxed. Integration needs an immutable historical checkpoint/adapter, review of changed dependency pins, and a focused rerun.
Validation evidence:
To reproduce the original-base validation, apply this PR's two-directory diff to the exact original base (rather than rewriting newer main's selected record), then run Python 3.10+ with its standard library only:
Only research/turyn-profile-cnf/ (15 files) and research/turyn-profile-parity-lift/ (29 files) are added. The archive, fetched context, publication logs, and other project files are excluded. Substantial AI assistance was used for the research, implementation, verification, and preparation of this submission. Predecessor attribution and Apache-2.0 notices are retained.