Repository navigation
Classify full-column P104 wire entry and exact cleanup queries (no new κ) - #6286
Merged
Mister-Meeseeks merged 1 commit intoOct 31, 2026
Conversation
Prepared for @CubeJerry with OpenAI Codex assistance. Credit Nick Petalas PR6261, Matarener PR6217 and the retained P104 lineage. No new kappa.
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.
At the 11/19/487 wire meeting, prove the forced full-column entry, attain it with two ADDs, and classify the extra query needed to restore the helper. Minimum query support is eight; dyadic cleanup additionally requires a unit coefficient. A concrete collision rules out recovery from the three local observations alone. This completes local obligations left open by #6261's qualified response projection; it is not a counterexample to that claim.
Base: 2485805.
#6261 source: 1866c2f. Exact input hashes: SOURCES.json.
Reproduce (Python 3.12, stdlib):
Expected:
PASS_REGISTERED_RESEARCH_PACKAGE.Executed: all 209 input columns; 15 query fixtures; exhaustive F3/F5 quotient cases 2673/70625 and correlated-Y F3 cases 24057; 97 rejection controls; normal/-O, source/history/mode/export and read-only Git-free checks. Wrong Y column, missing query, nonunit dyadic cleanup and actual source corruption reject. Fixed exhaustive domains; no random seed or unsearched region within them.
No new κ. This is a local interface, not a complete supplier. Correlated preparation, pure-query production, outgoing restoration, native implementation and a favorable complete invoice remain open; all five framework assumptions remain.
By @CubeJerry with substantial OpenAI Codex assistance: worker B, independent boundary reviewer, worker C and lead review. Credit Nick Petalas (#6261), Matarener (#6217), DreamingOfClouds (#6170) and retained lineage. No human or proof-kernel acceptance claimed.
Proof, exact pins, controls and limitations: https://github.com/CubeJerry/integer-mult-bounds/tree/2f2cf0b227bc54ce0b95d165b5f90ec82d7c4686/research/p104-correlated-entry-completion
Complete remote Git tree matches the tested contribution.