Repository navigation
Close P104 owned-holder handoffs with public frame separators (no new kappa) - #5579
Merged
Merged
Conversation
This was referenced Oct 25, 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.
This finite obstruction closes the owned-scratch gap explicitly left by PR #5569. All 5,252 owned-holder event cuts, including all 2,832 omitted scalar points, have two public holders with incompatible frame anchors. The same certificate applies to the exact PR #5561 and #5569 words. No new kappa is claimed.
Proof and scope, exact checks, source pins, registered replay. Base: canonical main
5e0052ca0aa3036a3afa8b0438927377c8d97d53, priority revision 7. Contribution head:29d388e9cde819de3b36893e64a7c74c6ed4ac63.The proof permits any binary common frame, any number of extra coframed registers, arbitrary MOVE stops between fixed scalar anchors, and free service of owned holders. Public constraints alone exclude every single-common-frame successor reset in this domain. This directs further work toward changed public anchors or a distributed reset. It does not cover a changed scalar prefix, public basis, scalar order or scalar frame. Canonical claim: Discussion #5576. The active retime and basis scopes remain separate. The submission refresh found the concurrent Discussion #5575 on changing the owned-boundary scalar realization. This fixed-program obstruction was sent there as supporting evidence; it does not close or reserve that changed-program scope.
Registered Python 3.12 normal and optimized replays pass. Sparse rational construction and a separate integer/dyadic pass check all required cuts and scalar exits; bitset and Gaussian frame checks verify every separator. Four controls reject missing coverage, a false separator, a false anchor and a false public-holder role. Both words produce certificate SHA256 dfcace797d5a8f49e2a104fcf8820232f02b0a174f478b24469c9b94a3b55211.
Python 3.12 and the standard library suffice. Committed-byte checks pass. No new native, physical caller, compiler or outer replay is claimed. This is a necessary-condition obstruction, not a global lower bound or independent admission of the predecessor kappa. Full historical ancestry checking was not run in the shallow checkout. Hosted status is unconfirmed at publication.
Source words: GamingPuzzled / Joel Pulikkan, #5569 at af9f091, DreamingOfClouds, #5561, thu-nmrc #5551 and aliromman #5544/#5545. Retain Gareth Davidson, David Arias, Cinna Davis, Cao Yifan, zxv, Jacob Alan Sussman and the productive-helper/native/compiler lineage. Exact remote paths and both content hashes are in INPUTS.json. Source interpreters are not imported.
Open next questions: defeat one public separator with a charged changed-anchor word, or provide a distributed reset with all old-input uses and owned returns paid. Coordinate with the active claims before taking those scopes.
Prepared by Ali Romman with substantial OpenAI Codex assistance; Apache-2.0.