Skip to content

Show that commuting staged544 moves cannot retarget a rank-1 ADD line - #4128

Merged
Mister-Meeseeks merged 2 commits into
CrocSwap:mainfrom
unpaidmoon:cursor/staged544-moved-add-pair-00a3
Oct 20, 2026
Merged

Mister-Meeseeks merged 2 commits into
CrocSwap:mainfrom
unpaidmoon:cursor/staged544-moved-add-pair-00a3

Conversation

@unpaidmoon

@unpaidmoon unpaidmoon commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

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

Validation

Python 3.12, standard library, from the repository root:

python3.12 -B research/staged544-moved-add-pair/verify.py
python3.12 -B scripts/research_package.py --package research/staged544-moved-add-pair
python3.12 -B scripts/check_research_commit.py --package research/staged544-moved-add-pair --check-source-history

The direct verifier also passes under python3.12 -O -B. Observed marker:

PASS_MOVED_ADD_PAIR providers=2 rank1=735 entrance=653 map=70 dependence=12 disjoint_line_moves=0 toy_helper_bill=4xrank1 toy_delta=0 no_new_kappa

research_package.py reports PASS_REGISTERED_RESEARCH_PACKAGE ... outcome=negative-result. check_research_commit.py reports byte equality at the publication commit and source-history ancestry of bb4bccbf42844d2801487450727c2f63e10d1d0f.

Provider and tracer SHA-256 values are checked inside verify.py. The gzip words and vendor/retiming.py are unmodified copies from PR #3964. That commit is not an ancestor of this base, so SOURCES.json pins 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_move sequence, 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.py come 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

  1. Can one explicit noncommuting transposition, with a scalar correction, put a rank-1 ADD on a disjoint line and strictly lower the histogram for every real 0<a<1? The twelve read-after-write pairs are the place to start. This obstruction stops at crosses, so that rewrite is a different identity. No such correction is specified here.
  2. Does a commuting move whose new frame properly contains the old line improve the histogram? Containing frames are outside this theorem. PR Certify neutral fixed-frame two-edit obstruction at displacement two #3970 already prices fixed-frame displacement two; a containing-frame census needs its own domain.

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.

cursoragent and others added 2 commits October 20, 2026 02:38
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>
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.

3 participants