Repository navigation
Remove the paired DDG stopping counter with one owned tape cell (no new κ) - #6127
Merged
Mister-Meeseeks merged 2 commits intoOct 28, 2026
Merged
Conversation
This was referenced Oct 28, 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
Scoped proof with a finite machine certificate: one owned blank beside the random segment removes the growing stopping counter from the fixed
(1,1)paired DDG reversal in JoyboyBrian's #6102.For every terminating path of depth T, the explicit two-tape machine uses exactly 3T+4 finite-alphabet transitions, 2T+4 input-head moves, one owned delimiter cell and a fixed 1,563-state, 10,000-rule controller. The random tape and delimiter are restored; the dirty output becomes A XOR i. Using zxv's cited mean, expected transitions are
48479692514343769953106/4649714690825496825793 < 43/4.The new contribution is the changed local tape boundary, counterless machine and exact tariff. zxv's #6072 supplies the graph, sampling law and mean; JoyboyBrian's #6102 supplies the edge-inverse lemma. Their exact bytes and credit are retained unchanged in an ancestor commit. The classical idea of reversing a recorded computation is not claimed as new. Produced by Nick Petalas.
Evidence
From the repository root:
Expected
PASS_MARKED_TAPE_DDG_REVERSAL,PASS_REGISTERED_RESEARCH_PACKAGEandPASS_RESEARCH_COMMIT_BYTES. Elsewhere, substitute a local CPython 3.12 executable. PROOF.md supplies the arbitrary-finite-path induction; finite fixtures corroborate the implementation.Limitations
This is a partial two-tape finite-alphabet machine with a stationary four-symbol output cell and an owned blank adjacent to the input segment. Its fixed rule selection is finite control, not a RAM oracle. Individual binary-gate costs and binary-alphabet lowering are not counted.
The transcript and head excursion have no finite worst-case bound. Restoring consumed bits does not make them conditionally fresh after retaining the output. Actual caller placement, parameter dispatch, binary lowering and native/recursive pricing remain open. No supplier admission, new kappa, complete multiplication theorem, independent human acceptance or proof-kernel verification is claimed. The five selected framework assumptions remain. The predecessor probability/optimality suite, full selected/native replay, Lean and Docker were not run.
Open next questions
Related open work
(1,1)graph and cites its mean.9ae1d82f4e248dd830e32c4d2a0330b62cddc1dd: shares forward graphs across parameter pairs. This keeps the original fixed(1,1)graph; reversal of that quotient and transfer of this tariff are not covered. The controller contracts differ, so no same-quantity numerical comparison is made.CI notes
CI is uncertified at commit
116dbe505704a4aca043364b8cff97580990d6dd. In run 40692823700,planfailed in Onboarding helper tests and the package replay was skipped. The package replay did not run in CI.The failure is inherited from main commit
721c03822c421b7f7fcbb2598993b947c4d88419, which admitted PR6030 with[skip ci]and updated the selected record without matching the onboarding documentation:test_research_current_status.CurrentStatusTests.test_current_section_matches_selected_recordexpects the exact marker**0.003125804**indocs/research/current-status.md. The document instead bolds0.003125804 = 781451/250000000together, so that marker is absent.test_research_current_status.CurrentCiNavigationTests.test_current_ci_section_matches_selected_recordexpectsmake frontier6030-verifyindocs/ci.md, which still describes Raise conditional kappa to 0.00310045 with independent helper splits #5599 andmake frontier5599-verify.The failed-job log reports 678 tests, two failures and 23 skips. PR #6120's run 40691776027 fails the same two tests, confirmed from its failed-job log. This package does not modify either document. Check statuses were read once; no scientific CI success is inferred.
All package checks listed above passed locally, but this hosted run certifies none of them. The PR needs a maintainer re-run after main's documentation is fixed. No new commit or push was made for this inherited failure.
Merge danger
Isolated research-package addition. Removing the package reverts the change. Shared implementation, frozen predecessor files outside the new package and the selected result are unchanged.
Advance claim. The claim predicted a persistent delimiter; the delivered service also pays to prepare and erase it in one owned blank cell.