Repository navigation
P104: exclude two non-carrier ADDs across helper572’s chart seam (no new kappa) - #6088
Merged
Mister-Meeseeks merged 2 commits intoOct 28, 2026
Merged
Conversation
Contributor
Author
|
CI follow-up for The plan failure reproduces on clean canonical main |
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.
PR6067 and PR6069 leave corrections that temporarily change original input rows open. This package checks one concrete two-ADD seam on the selected PR6030 word: after overwriting helper 572 at cut 13637, insert one ADD at chart 595 during 13637..13651 and a second at chart 603 after 13652,13654 or13655. All original events, charts and lifetimes remain fixed.
None of the 4,500 declared location pairs restores all 186 outside-V outputs for arbitrary original inputs and independent new z. The complete endpoint polynomial includes the ab interaction; every case is inconsistent even after replacing ab by an independent third variable. Exact directly checked dual certificates use one equation in 4,262 cases and two in 238. This is a scoped finite exclusion, with no new kappa or supplier claim.
Validation on CPython 3.12 includes registered normal and optimized replays, forward/reverse scalar-map equality, four separate literal whole-word checks on all original input columns plus z, a synthetic positive repair, wrong-chart/forged-dual rejection and a real z-only false positive. An independent AI-assisted peer review found no issue and recovered three duals through a separate scalar execution and interpolation implementation. Source pins, exact committed bytes/history/modes and official export integrity pass. Fresh read-only Git-free normal and optimized exported replays pass in 8.80/8.86 seconds with identical output and unchanged files.
Only
research/p104-noncarrier-two-add-seam/is added. The sole external live input is the selected word; pending predecessor implementations are not dependencies. No selected cold/native/compiler/caller/outer replay or formal-kernel validation ran. Three or more edits, other windows, changed routes/prefixes/injections and full paid constructions remain outside scope. The five selected framework assumptions remain.Canonical claim: #6074
Credit apoursh/PR6067, Jonathan Capalbo/PR6069, JosieElliston/PR6045, Nick Petalas/PR6040, Matarener/PR5994, flyingviper/PR5718, Ali Romman, DreamingOfClouds and retained P104 predecessors. Prepared for JoyboyBrian with substantial OpenAI Codex assistance. AI peer review is not independent human or formal proof-kernel acceptance. Apache-2.0.