Repository navigation
Show that commuting staged544 moves cannot retarget a rank-1 ADD line - #4128
Merged
Mister-Meeseeks merged 2 commits intoOct 20, 2026
Merged
Mister-Meeseeks merged 2 commits into
Mister-Meeseeks merged 2 commits into
Conversation
On both pinned PR3734 providers every rank-1 ADD keeps a witness line under apply_move, so the crossed-line pattern left by CrocSwap#3964 does not occur. That pattern's scalar program is unchanged and its histogram delta is zero, so this does not change kappa. Co-authored-by: unpaidmoon <unpaidmoon@users.noreply.github.com>
…on as the added piece. PR CrocSwap#4122 already prices a swap-and-restore identity at histogram delta zero and does not search the pinned providers. This package's new claim is that commuting apply_move cannot retarget those rank-1 lines. Co-authored-by: unpaidmoon <unpaidmoon@users.noreply.github.com>
This was referenced Oct 20, 2026
Draft
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
Finite obstruction plus one scalar identity. No new κ. Selected conditional κ stays
0.001672660197076918.On both pinned PR #3734 providers, every rank-1 ADD frame has a witness operand whose line is created by an entrance, a warp map, or an earlier rank-1 ADD that does not commute with it. Those witnesses are invariant under
apply_move: non-map frames must contain their incoming state, and a warp cannot be relocated or crossed. After any finite sequence of commuting ADD moves, the frame still contains the original line. The crossed-line pattern left open by PR #3964 therefore does not occur on these words.The same pattern, written as two scalar ADDs, keeps its opcodes, operands, and coefficients. Each of the two helpers contributes two rank-1 climbs before and after, so the child-histogram delta is zero. Either one-edit intermediate is illegal. An unchanged histogram is not a paid-profile gain.
Counts on each provider: 735 rank-1 ADDs, entrance 653, map 70, dependence 12. The twelve dependence pairs are adjacent read-after-write ADDs in section A.
This is not a supplier admission, not a noncommuting-rewrite theorem, and not a multiplication theorem. Frames that properly contain the old line, cleanup, native phases, owners, and all-size transfer are not repriced.
Task and overlap
bb4bccbf42844d2801487450727c2f63e10d1d0f(canonicalCrocSwap/integer-mult-boundsmain). Priority revision 6.scalar-to-moment, scope refined. The card asks whether one scalar simplification changes a paid histogram. The object is the moved-ADD question released by PR Close stationary simultaneous-frame loophole on staged544 #3964, on the two pinned providers and theapply_movecontract, not a new R439 word.8a8bfb8d36cf5c9f7681b9e7f5d7876a4ba0f5a0, proves the stationary case and leaves the moved-ADD question open. Its synthetic crossed-line control is not a provider occurrence.apply_move. The two-ADD bill in this package recomputes the Close stationary simultaneous-frame loophole on staged544 #3964 synthetic control; it is not a second claim on the Price one moved-ADD crossed-frame pair at histogram delta zero. #4122 invoice.b52f2efaff416cd1f464463e125e7ba4146c9c72. Fork PR: Show that commuting staged544 moves cannot retarget a rank-1 ADD line. unpaidmoon/integer-mult-bounds#18.Validation
Python 3.12, standard library, from the repository root:
The direct verifier also passes under
python3.12 -O -B. Observed marker:research_package.pyreportsPASS_REGISTERED_RESEARCH_PACKAGE ... outcome=negative-result.check_research_commit.pyreports byte equality at the publication commit and source-history ancestry ofbb4bccbf42844d2801487450727c2f63e10d1d0f.Provider and tracer SHA-256 values are checked inside
verify.py. The gzip words andvendor/retiming.pyare unmodified copies from PR #3964. That commit is not an ancestor of this base, soSOURCES.jsonpins only the catalogue and the selected record.The checker tests the witness partition and the window hypotheses. The invariance statement is a proof about every
apply_movesequence, not an enumeration of those sequences. No Lean, Docker, or selected cold replay was run.Credit
The providers are dataisfire's PR #3734 words as vendored by Chris R / Clear1nsight in PR #3964. The stationary theorem, the crossed-line control, and
retiming.pycome from that PR and its credited PR #3886 / PR #3942 lineage. PR #4122 is the parallel abstract invoice. The witness partition and the invariance argument are new.Prepared by unpaidmoon with substantial Cursor Grok assistance. No independent human or formal-kernel review is claimed. Apache-2.0.
Open next questions
0<a<1? The twelve read-after-write pairs are the place to start. This obstruction stops atcrosses, so that rewrite is a different identity. No such correction is specified here.Workflow feedback (optional)
Handoff-before-picker selection kept this off the randomized catalogue. A parallel session invoiced the abstract identity while this one was still on the provider trace; citing that PR in the package is what kept the two claims apart.