Repository navigation
Conversation
This was referenced Nov 13, 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
Reduce the supplied literal phase/egress boundary from 36 physical tapes to 20, including two public owners. This scoped constructive proof answers CubeJerry #7425's explicit shared-bank question. The existing component arithmetic and successful retirement are cited premises, not audit deliverables. The new shared graph and composition proof were produced by Nick Petalas.
The fixed graph has 19,960 locations. All sixteen egress private roles share the phase bank after successful retirement. Head return, original DATA ownership and all historical backing remain charged. The exit costs exactly the sum of the original egress and final-phase instruction counts. This improves an inventory upper bound; it claims neither a global tape minimum nor lower total visited space. No new kappa or selected-frontier change.
Only
research/shared-phase-egress-bank/is added, from canonical maine54523517d0f03e58352e647c403a5af3e525a57. Theformal-interface-lemmacard is explicitly changed to this supplied physical-boundary result. Exact pending-source bytes and original notices are retained locally with SHA256/Git-blob pins; replay needs no predecessor verification suite, remote fetch or unmerged Git object. Advance claim.Evidence
PASS_SHARED_PHASE_EGRESS_BANK.From the repository root:
Another machine may substitute its CPython 3.12 path. The verifier prints a generated receipt bound to package and graph hashes.
PROOF.mdgives the unbounded composition argument; finite fixtures corroborate it.Limitations
Both routines require supplied blank private windows covering their combined visits. A larger invocation needs blankness of newly visited cells. This does not merge two arbitrary dirty banks. Rejection/interruption cleanup and rollback are unclaimed; the final phase retains its signed-range condition. The exact C producer, common-grid format conversion, source acquisition, caller allocation and their costs remain additional obligations. Test C production is an explicit outside oracle. No selected cold replay, full supplier, complete multiplier, independent human review or proof-kernel acceptance is claimed.
Open next questions
Bind one actual C producer to the same header, address order, common grid, signed headroom and retired shared bank, and price its format conversion and allocation. Begin with one pinned caller occurrence. Further tape reduction requires changing simultaneous component liveness; this proof supplies no such construction or lower bound.
Related open work
The own-open-PR closeout check inspected the seven other account contributions created since the CLAIM: #7502, #7503, #7504, #7505, #7506, #7507 and #7509. The two related phase results are listed above. The other scopes concern column-plane geometry, canonical rotation routing, exact inverse preparation, cubic repair and interaction-error bounds. No extra mathematical computations were run to compare them.
Credit CubeJerry, aliromman #5375, tekuuu #3127, jmbarrancoml #2287 and #3087/#3091/#3098, JoyboyBrian #5329, 1337isnot1337 and pinterbanget #4325, the upstream stream/layer authors and all unchanged source notices. Lifetime sharing is elementary; the source-specific graph, proof and evidence are the contribution.
CI notes
CI did not certify this package. At unchanged commit
82d677390993e28e12a0203169a69d9d929aa5a2, run 43437279341, plan job 131925534865, failed inOnboarding helper tests. I read the checks once and inspected the actual job log. Exactly one of 760 tests failed, with 24 skipped:test_research_current_status.CurrentCiNavigationTests.test_current_ci_section_matches_selected_record, attests/test_research_current_status.py:58. The AssertionError says that`make frontier7000-verify`was not found in the CI verification document. The package replay job was skipped after planning failed, so no hosted package replay ran.I inspected the base Git objects at
e54523517d0f03e58352e647c403a5af3e525a57:certificates/selected-result.jsonnamesmake frontier7000-verify, whiledocs/ci-verification.mdstill describes #6030 andmake frontier6030-verify. Those files and the test are unchanged by this PR; its diff contains only the sixteen isolated package files.I also read the failed-job logs for rohanarun's run 42905094314, dillona's run 42903313790, and petalas runs 43437283229, 43437288667 and 43437529382. Each reports the same sole failing test and missing-command assertion, 760 tests and 24 skips. Run metadata confirms the named fork owners. This is evidence of the shared repository-level failure and provides no mathematical certification for this package.
The local checks listed above remain the evidence at the unchanged commit. No fix, retrigger commit, push, shared-file edit or job rerun was made in response to the failure. Maintainers own the repair of main.
Merge Danger
Door: two-way. Blast radius: one isolated research package. Shared code, predecessor files and selected records are unchanged.