Repository navigation
Record the reflected P112 frame's transported weight-16 equality. - #7017
Open
unpaidmoon wants to merge 1 commit into
Open
unpaidmoon wants to merge 1 commit into
unpaidmoon wants to merge 1 commit into
Conversation
One simple reflection of the CrocSwap#7007 puncture rebuilds a different 112-line frame. A half-split of that kernel matches the transported supports. Selected kappa is unchanged. Co-authored-by: unpaidmoon <unpaidmoon@users.noreply.github.com>
This was referenced Nov 10, 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.
Change and mathematical scope
On the 112 lines left by one simple reflection of the pinned P112 puncture, one half-split returns exactly the transported images of the seven weight-16 supports recorded in #7007. The reflected frame is a different orthogonal 8-frame. The code is again 36-dimensional, the least positive weight is 16, and those seven words are the whole weight-at-most-16 set.
This is an exhaustive finite census of one reflected code, and a set comparison. It is not a timing claim, not a consumer installation, and no new κ is claimed. The selected value stays
781451/250000000.The reflection is the first pair, in the pinned E8 simple-system order and then the punctured-line order, that moves a line. Simple root
α = (1, -1, -1, -1, -1, -1, -1, 1)sends punctured line(2, -2, 0, 0, 0, 0, 0, 0)to(1, -1, 1, 1, 1, 1, 1, -1). The same reflection fixes four punctured lines and moves four. The rebuilt complement, in increasing line index, has SHA256a2ac7049d9eef1cff8af1eec35b084e6d261efad5311625e5356cceafe260da7.The transported supports, in the recorded order, are
Their SHA256, of
json.dumpsof that sorted list, is9ce7e5edc72ee3104d62cb068146b73840e9a3c42c4132403dece70c8146cccb.The seven untransported integers fail a frame parity of this new code. The half-split visits all
2^36kernel words. Its weight distribution equals the distribution recorded for the unreflected frame. That is a comparison of enumerators from two different bases, not a replay of the unreflected census.Task and overlap
Base commit:
17469fff78c22941280f04d39dc5a1faee09c840on canonical CrocSwap main.Task card
replay-runtime, priority revision 8. Scope status: refined. The card asks for a measured speedup that keeps coverage. The revision-8 verification row says a published faster replay is not equivalent coverage until checked. Open #7007 recorded the unreflected P112 equality and left this reflection as its first open question. This package answers that question for one pair. It does not rerun the unreflected census, the D6 equality of #6959, or the E6 equality of #6948, and it does not run the intersection-counter comparison.scripts/find_overlap.py --refreshon 2026-11-10 read 317 open pull requests (fetched2026-11-10T08:51:47Z, pagination complete) and 10180 local notes at this base, with a complete local inventory. The only match was #7007, which poses the question and does not build the reflected frame. The discussion refresh returned HTTP 504 and left no usable discussion snapshot. A search for the recorded support hash found that same pull request and no second item.Validation
Python 3.12, gcc, and the standard library. The registered command measured about 73 seconds here, including a 70-second half-split on 4 cores.
check_research_commit.py --check-modespassed at11af08b8ff57dc26492501b4efaffdb34d298a00.--check-source-historywas not run: this checkout is shallow.The registered replay printed
Not run: a second split, the unreflected half-split,
low_weight_words,research/e7-intersection-counters/engine.py, the E6 and D6 censuses, any other simple root's frame, Lean, Docker, andscripts/research_selected_baseline.pyas a scientific replay. The selected record is provenance only.This census does not cover every simple reflection, and it is not an unrestricted nonexistence result.
Credit
The 120-line order and the unreflected puncture are the model in
research/p112-rank6-frame-coverage, from the PR1226/PR1323 listing used by Cinna Davis. The simple system is the one inresearch/p112-a3-six-flat/geometry.py, from Nick Petalas's PR3161/PR3162 lineage. The seven supports, their hash, and the unreflected weight distribution are recorded in open #7007. The doubling half-split follows that package's scanner and reads the reflected basis. The question is open question 1 of #7007.Prepared by unpaidmoon with substantial Cursor Grok assistance. Apache-2.0. No independent human review and no formal-kernel acceptance are claimed.
Open next questions
low_weight_wordson this reflected 36-generator basis return the same seven transported supports? This is the bit-lane iterator on the reflected basis, compared with hash9ce7e5edc72ee3104d62cb068146b73840e9a3c42c4132403dece70c8146cccb. It is separate from the intersection-counter comparison on the unreflected basis and hashff8861dab18040c03d403a860773218df7c120d03770d701afb61b78c941e3d3.Workflow feedback (optional)
One half-split of this 36-dimensional length-112 code fits in the 600-second command limit. The bit-lane scan that #7007 measured at about 494 seconds does not fit beside it, which is why that comparison stays a separate question. A link to the feedback discussion is enough: #1200