Skip to content

Exclude the six-point rank-four length-30 sojourn (no κ) - #7511

Open
petalas wants to merge 1 commit into
CrocSwap:mainfrom
petalas:research/w5-1113b-new-obstruction
Open

petalas wants to merge 1 commit into
CrocSwap:mainfrom
petalas:research/w5-1113b-new-obstruction

Conversation

@petalas

@petalas petalas commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Scoped written proof with exact finite corroboration. A universal closed eight-source binary singleton word of length 30 cannot have a multiplicity-two source whose rank-four sojourn visits exactly six projected states.

- PR #7093 leaves the size-six layer separate, with candidate layer sizes (24,6)
+ the six-point layer needs at least 32 complementary states, hence at least 38 slots

This closes the explicitly separate size-six opening in unpaidmoon #7093 at 94b36d4649b5d29829959409acbc1906ef0b4379. Three translates can cover an elementary binary group only if the other set has at least half the group. Applying that affine-plane coset argument in each of eight fibers gives the new obstruction. An explicit 32+6 cross-layer cover attains this set-cover bound, but fails the same-layer condition and is not a universal word.

The contribution was produced by Nick Petalas. Credit unpaidmoon #7093/#7015/#6943 for the question and sojourn split, RossRichardson #943 for the singleton prefix model, and Mister-Meeseeks #1185, conorholds #3058, petalas #5234 and NicholasStone #5430 for the retained eight-source lineage. The abstract counting method is elementary; no literature-wide priority claim is made. Predecessor scientific executables were cited, not replayed.

Advance CLAIM. The connector-alphabet-change card is explicitly changed to this algebraic side result within the existing alphabet.

Evidence

Before, #7093 leaves the six-point case outside its sixteen-point census. The new self-contained proof excludes it without using that census, the rank-three exclusions or f(7)=24.

Local CPython 3.12.15 warning-strict normal and optimized replay passed all 4,484,480 pairs of 8,008 six-sets and 560 triples in F_2^4. No pair covers the group. A separate literal-set implementation checks all 8,008 normalized cases; their cardinality histogram agrees with the complete census. The explicit cross-layer cover, its failed same-layer condition and four boundary controls pass. Four disposable implementation mutations were rejected.

Every registered command was timed locally at about 0.33 to 0.35 seconds. Metadata/source pins, registered replay, exact six-file committed bytes and source history pass at 68c3c7dd16fe87d86386d7dc61ae566c552925cc. Official export integrity and read-only Git-free normal/optimized execution pass with identical generated package-hash receipts.

From the repository root, using the standard library:

/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -W error -I -B research/rank4-six-point-sojourn/verify.py
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -W error -I -O -B research/rank4-six-point-sojourn/verify.py
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/research_package.py --package research/rank4-six-point-sojourn
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/check_research_commit.py --package research/rank4-six-point-sojourn --check-source-history

Expected marker: PASS_RANK4_SIX_POINT_SOJOURN, with paired_sumsets=4484480, complementary_layer_floor=32 and cross_layer_total_floor=38.

Limitations and unrun obligations

This does not decide the remaining layer sizes, construct or exclude every length-30 word, or improve f(8) or kappa. A cross-layer set cover is not a legal chronological word or a complete difference cover. Physical query prices, routing, restoration, native/stock/precision/caller admission and a complete multiplication theorem remain outside scope. No predecessor scientific replay, Lean, Docker or selected cold replay was run. Independent human and formal proof-kernel review are unclaimed.

Open next questions

Does a universal length-30 word survive the remaining rank-four sizes and higher-rank cases? First search a rank-four layer with 17 complementary points under #7093's existing constraints, excluding size six by this proof. The coupled same-layer cover and legal closed walk remain blockers. This contribution stops at the new exclusion.

Related open work

No extra computation was run to validate or compare these predecessors' numbers. Searches include live open PRs, recent account PR bodies, handoff claims, targeted all-state and merged searches, and canonical-main README terms. The cached overlap helper reports sparse local coverage and no remote snapshot; no match is not a novelty certificate.

CI notes

CI did not certify this package. I read the checks once and inspected run 43442114549, plan job 131942083748 at unchanged head 68c3c7dd16fe87d86386d7dc61ae566c552925cc.

The Onboarding helper tests step ran 760 tests and reports exactly one failure, with 24 skipped: test_research_current_status.CurrentCiNavigationTests.test_current_ci_section_matches_selected_record. Its AssertionError says that 'make frontier7000-verify' was not found in the CI verification document. On canonical main e54523517d0f03e58352e647c403a5af3e525a57, certificates/selected-result.json names make frontier7000-verify, while docs/ci-verification.md still describes #6030. I read those main-file contents directly. This isolated package does not change them.

I independently read the same sole failing test, assertion, 760-test count and 24 skips in run 42905094314 and run 42903313790. The dependent package replay job was skipped because plan failed. The passing local evidence above remains local evidence; hosted CI certified no package claim. The commit is unchanged, and no rerun or retrigger commit was made.

Completion overlap check: this account's open PRs created since the advance CLAIM at 2026-11-13T14:16:12Z were listed and their bodies checked. No additional PR studies this six-point sojourn or the eight-source length-30 object, so no numerical comparison or extra computation was needed. The related-work list above remains current for that check.

Merge Danger

Door: two-way. Blast Radius: isolated. Only the new research package is added; no selected record, shared runtime or frozen predecessor is changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant