Skip to content

Conditional κ .00310871312 (+5.546e-7 over #5678): exact reorder+re-frame optimum (helpers 473, 733) - #5684

Merged
Mister-Meeseeks merged 4 commits into
CrocSwap:mainfrom
GamingPuzzled:r22e-reframe-5678
Oct 26, 2026
Merged

Mister-Meeseeks merged 4 commits into
CrocSwap:mainfrom
GamingPuzzled:r22e-reframe-5678

Conversation

@GamingPuzzled

Copy link
Copy Markdown
Contributor

Conditional κ .00310871312 (tested .003108713125; exact raw crossing in (0.00310871314031, 0.00310871314032)), +5.546e-7 over #5678 (Ali Romman, .00310815849). Package: research/p104-reframe-r22/, stacked on #5678 head af814f6f3.

Conditional on exactly #5678's assumptions and its P104 line, including free helper endpoints (#5561, audited in #5567). This word changes one helper start.

Change

This is the optimum of the R22 exact reorder+re-frame MIP on #5678's word. The restricted domain and the wide (dim gap ≤ 3) domain give the same optimum.

Per local call: paid H1 −3, H4 +1 (66402 → 66366 paid calls). Helpers H8 −1, H9 +1. Surplus 760 and fields 12958 are unchanged.

Verification

python3 -W error -B research/p104-reframe-r22/verify.py (~4 min, PASS, reproduces RESULT.json exactly):

Supersedes our #5666 (same method, on #5660).

AI disclosure: Claude Opus 5.5 (Anthropic) via Claude Code, directed by Joel Pulikkan (GamingPuzzled). Apache-2.0.

🤖 Generated with Claude Code

aliromman and others added 4 commits October 25, 2026 23:31
Four re-framed ADDs and one helper start (473: 594 -> empty chart 3; 733
reads moved onto chart 772), the R22 MIP optimum on PR5678's P104 word.
Checked on PR5678's own unmodified stack with four declared pricing
literals changed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Clear1nsight

Copy link
Copy Markdown
Contributor

HANDOFF — existing R22 model-domain pointer request, before attempting overlapping work.

Research discussion / PR / artifact: PR #5684, research/p104-reframe-r22/README.md and its stated commutation-poset × subspace-chart optimum.

Exact commit: d0f6fa2555410a1e23fe4191424c2097ab3d5d97, based on PR #5678.

What is established: The README says the restricted and wide dim-gap-at-most-three domains have the same optimum, and identifies the helper 473 entrance/read changes. We have read the committed README and constructor as text; no source replay or new word search was run.

What remains uncertain: The exact permitted helper-start charts and linear extensions in the wide model. In particular, does the boundary-start domain allow raising an initial helper chart above the original start, or only retaining/lowering it? We could not resolve the advertised r22-p104-reframe-optimum branch in the public fork; this is an availability question, not an objection to the result.

Smallest useful next task: Please link an existing immutable commit/path for mip104.py/poset104.py, or the short domain definition. That would let us decide whether a conditional delayed-first-read/unused-prefix trim is already inside the optimum, before any lookup or construction. Actual shared-frame, observer, independence and complete-cost premises remain unproved; no candidate or gain is asserted. No new solver run or search is requested.

Reproduction command and expected runtime: Existing source/domain inspection only; no new execution requested.

Predecessor credit: Joel Pulikkan/GamingPuzzled and Claude assistance for R22; Ali Romman's PR #5678, PR #5599, and all retained native/helper/controller/compiler sources. Prepared for Clear1nsight with substantial OpenAI Codex assistance. No scope reservation, κ improvement or independent acceptance is claimed.

@GamingPuzzled

Copy link
Copy Markdown
Contributor Author

Thanks for checking. Until now the branch was only local; it is now public at an immutable commit:

Helper-start question. Helper endpoints are free (#5561, audited in #5567). Each helper path starts at a virtual source with a zero-cost arc to any chart in its first op's domain. The start is just that first op's chart. Nothing ties it to the original start, so it can be raised as well as kept or lowered. The only limits are the op's bounds (lows <= X <= ups, the join and meet of forced neighbours) and comparability with forced charts. Credit is linked to the chosen start and final dims.

Domains.

  • Restricted: the charts the op's registers already use.
  • Wide dim-gap-3: every subspace between lows and ups when dim ups - dim lows <= 3; otherwise the word's charts within the bounds.
  • In both modes the current chart is always included.

Order.

  • Any linear extension of the run-typed commutation poset: (T,T) and (S,S) runs commute, and owned registers are all-X.
  • Every chart-implied order cycle gets a lazy no-good cut.

Was a delayed-first-read or unused-prefix trim inside the #5684 optimum? It was, as long as the trimmed start chart lies in the first op's domain under that mode, and the reorder it needs commutes in the poset. Starts outside the wide domain (gap > 3 from the bounds), or trims that need non-commuting moves, were not covered.

The block move in #5739 came from the same model, restricted to large-neighbourhood windows (WIN / WINREGS, gap 4). Owned ops are pinned unless OWNED_FREE=1; with it set, the result on #5660 was the same optimum as with them pinned.

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.

4 participants