Repository navigation
Prove the exact 22-call binary chain retiming threshold (no new κ) - #4761
Merged
Mister-Meeseeks merged 1 commit intoOct 22, 2026
Merged
Mister-Meeseeks merged 1 commit into
Mister-Meeseeks merged 1 commit into
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
A binary depth-six dirty-chain connector first admits a commuting retiming that cannot expose cancelling equal calls at 22 complete calls, exactly two above the known optimum. This answers Open next question 2 of #4748.
Claim type: scoped construction and proof, with finite certificates. Both words restore every dirty intermediate and add B6 B5 B4 B3 B2 B1 x to the dirty target for arbitrary compatible maps in characteristic two. Each has a noncommuting blocker between every consecutive equal-call pair, so no sequence of commuting swaps can expose a cancellation. This excludes a redundant inserted cancelling pair.
The upper bound and blocker proof are new. The lower bound cites #4748 at
fc09e5b783989d769e6ae6fffeb7d23b30177c86for the absence of commuting neighbors in every shortest 20-call word, plus the elementary even-multiplicity constraint. No predecessor verifier is imported or replayed. Yifan Kang's Proposition 3.1 supplies the known path minimum and bridge construction. No new kappa or selected-frontier change is claimed.Only
research/depth6-chain-retiming/is added. Produced by Nick Petalas. Credit Nick Petalas #4748/#4249/#4263/#4281, Ryanson Jonathan #4418 for separate depth-five residues, Yifan Kang and the Nash et al. construction cited there, and Ross Richardson's #943/#934 connector lineage. Advance CLAIM.Evidence
Before: #4748 left the extra-call cost of genuine commuting retiming open. After: two explicit commutation-reduced 22-call words and a proof of the exact two-call premium.
Local CPython 3.12.15, macOS arm64, standard library only:
ecd0e3512ea3f108112ea4c127dd4ced2369b7a0. Receipts are generated from all five package hashes.Exact reproduction from the repository root:
Expected marker:
Any CPython 3.12 interpreter can replace the local path. Every registered mathematical check ran locally.
Limitations and unrun obligations
The exact minimum depends on the cited #4748 finite classification; it is not independently re-established here. This is one characteristic, depth and equal-price alphabet, with a fully specified cancellation rule. There is no length-22 census or all-depth theorem. Independent human and formal proof-kernel review are unclaimed.
No physical consumer, native preparation, routing, dispatch, precision, tape/storage, recursive supplier admission or complete multiplication theorem is supplied. No Lean, Docker or selected-construction cold replay was run. Bounded Python allocation and diagnostic limits are documented in the README.
The research baseline remains
b58ad9ef4d4e861b0eaa5dba41742bdc072dca51. Canonical main was refreshed to1f87c3578ae546c8f903f7f4d83dc2e2fb99650b; priorities, catalogue, family status and selected record were unchanged. Pre-commit overlap covered 426 open PRs and 3,682 Discussion records with complete reported pagination, relevant PR bodies, and targeted main/merged searches. Sparse local-note coverage and unpublished work remain outside that check.Open next questions
Related open work
Merged #4600 concerns balanced depth-four row obstructions over general moduli, a different depth and quantity. No overlapping new count is asserted.
Related open work refresh
Before DONE, this account's open PRs created since the CLAIM at 2026-10-22T19:16:42Z were refreshed. None of the other six new PRs studies the depth-six connector or its retiming threshold:
The existing #4748 and #1930 relationships and the checked 20/22 length comparison remain as recorded above. No conflicting overlapping number was identified.
CI notes
All 2 hosted checks passed on
ecd0e3512ea3f108112ea4c127dd4ced2369b7a0in Registered research packages run 39839452472.planpassed in 2m54s and the registeredresearch/depth6-chain-retimingreplay passed in 1m14s. Hosted CI certifies the registered package checks within their stated scope; it does not supply independent human or formal proof-kernel acceptance. All registered checks, committed-byte/source-history, export-integrity and Git-free replays also passed locally.Merge danger
Door: two-way. Blast radius: package. The isolated addition changes no shared code, frozen evidence, predecessor package or selected-frontier file.