Repository navigation
Prove exact nearest-even shear history from binary code weight - #5912
Merged
Mister-Meeseeks merged 1 commit intoOct 27, 2026
Merged
Mister-Meeseeks merged 1 commit into
Mister-Meeseeks merged 1 commit into
Conversation
This was referenced Oct 27, 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 mathematical proof with exact finite corroboration. For a fixed rational matrix A, retained integer source x and whole-sum nearest-even output z=R(y+A*x), the minimum fixed history is exactly tau(A) bits:
Every nonempty fixed-source fiber has exactly 2^t(x) preimages. An explicit bit encoder/decoder attains the lower bound. The unaugmented map is a bijection exactly when every reduced entry denominator is odd. Rank one can require arbitrarily many bits; two 3-by-2 rank-two matrices need exactly two and three bits respectively.
This contribution was produced by Nick Petalas. Credit Ali Romman #5838 for the actual-rounder correlation question and ywz65 #2555 for the prior scalar whole-sum tie collision and increment-rounding boundary. Their scientific verifiers were not replayed as the contribution. Exact question-source head/blob/SHA256 and historical provenance are in SOURCES.json. Classical rounding, binary codes, Bezout and the pigeonhole principle retain their credit.
Evidence
Before, #2555 identifies a scalar collision and #5838 distinguishes adversarial completed defects from physical rounding correlations. After, the written proof classifies every rational shear's exact history requirement and supplies a matching reconstruction, including signed data.
Local CPython 3.12.15 normal and isolated optimized warning-strict commands pass in 2.108s and 2.003s, each below its 120-second timeout:
Registered replay and metadata/pins pass. Committed bytes, modes and source-history preflight pass at 8c6aa0f. Official committed export/integrity and a read-only Git-free optimized replay with empty PATH pass; all six exported files, including the export manifest, retain their bytes. Receipts are generated on stdout and bind all five package files.
From the repository root:
Any CPython 3.12 executable can replace the local interpreter path. No third-party dependency is required. Expected markers are PASS_NEAREST_EVEN_SHEAR_HISTORY, PASS_REGISTERED_RESEARCH_PACKAGE and PASS_RESEARCH_COMMIT_BYTES.
Advance CLAIM. Canonical main was refreshed before submission and remains de5ec2e, priority revision 8. The joint-query-controller card is explicitly changed to this local arithmetic/cleanup side result.
Limitations
The theorem assumes arbitrary independent integer-grid destinations, retained source, fixed rational coefficients and whole-sum nearest-even rounding without overflow or saturation. Its universal scope rests on the written proof; enumeration corroborates bounded domains. The encoding is an information result, with no physical history lifetime, instruction count or zero-return workspace bound.
Physical/native child construction, history uncomputation, full P104 words, compiler/tapes, selected cold replay, outer arithmetic, Lean and a complete multiplication theorem are unrun and unclaimed. No kappa or selected-frontier change is made. The five selected framework assumptions remain. Independent human and formal proof-kernel review are unclaimed.
Open next questions
Can one actual completed P104 child retain and uncompute its required tie history within the complete physical bill? First freeze that child's rounding sites, entrance lattice and returned outputs, derive its fibers, then price a history lifecycle. A completed physical child and restoration machine remain missing.
Related open work
The final related-work refresh inspected all nine other account PRs opened since the CLAIM. Two also concern rational shear arithmetic, under different interfaces:
No matching history quantity or numerical disagreement was found. No extra mathematical computations were run to validate the other submissions.
CI notes
At exact head
8c6aa0f49bce1a96b15d636d6854ae5f158b2091, run 40506300760 has plan failed; replay skipped. The only failed step is Onboarding helper tests. All ten failure/error entries are in unchangedtests/test_research_current_assignment.py, endingFAILED (failures=8, errors=2, skipped=22).The two errors are
KeyError: 'follow_up_steps'andKeyError: 'catalog_first_step'. The eight assertion failures comprise0 != 16, five missing-reference/helper cases reportingValueError not raised, and two sparse-omission list mismatches. These are the shared mainde5ec2e7aonboarding failures. All ten failure/error headers, their exception/assertion messages and the final summary match PR #5915's plan log, which was read directly.Hosted replay has not certified this package; only the local scientific and publication checks above have run. Maintainers will address the shared test failure. No package, shared implementation or test file was changed in response.
Merge Danger
Door: two-way
Blast Radius: research
Five new files in one opt-in package. No shared checker, predecessor source or selected record changes.