Repository navigation
Prove all-precision dyadic affine feasibility (no new κ) - #5889
Merged
Mister-Meeseeks merged 1 commit intoOct 27, 2026
Merged
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 algebraic proof with exact finite corroboration. Decide whether a supplied rational strict affine parameter region has a dyadic point at any precision, and construct one when it does.
The permanent obstruction is
oddpart(d_i) ∤ (Ub)_i. When none occurs, the exact equality threshold is the largest binary denominator exponent of(Ub)_i/d_i. For each strict row, the construction preserves its margin oncesum_free |(AV)_ij| < 2^(p+1) delta_i. The strict sign is necessary for the stated rounding guarantee. This extends the finite precision cap in Ali Romman's #5794, rather than auditing that search. No new kappa or selected-frontier change.Evidence
infeasible_through_limitleaves all finer grids open. After: the supplied strict affine model has a complete all-precision criterion and a constructive sufficient precision. The equality threshold is exact; the whole-region precision bound is sufficient.8811e913cef13d3d2d7d0941c791d58c9be78e3b. Official five-file export and offline integrity checks pass.From the repository root, CPython 3.12 and the standard library:
Another CPython 3.12 path may replace the absolute path. The standalone output contains
PASS_DYADIC_AFFINE_FEASIBILITYand the registered runner ends withPASS_REGISTERED_RESEARCH_PACKAGE.Limitations
The theorem requires a supplied Smith decomposition and a rational witness strict on all remaining inequalities. It does not extract an affine hull, compute Smith charts, find the witness or minimize the precision of the inequalities. A general closed region needs its forced equalities exposed before this interface applies. The executable helper is bounded to six equality rows/coordinates, 32 inequalities, 64-bit input rational components and 4,096 precision bits; unsupported inputs raise an error. The proof has no dimension or precision cap.
No actual supplier parameter proof, nonlinear feasibility, physical arithmetic/storage invoice, native caller, compiler admission or analytic recovery is supplied. No selected scientific replay, Lean, Docker or proof-kernel check was run. Smith normal form, localization and nearest-grid error bounds are classical; no literature-priority claim is made for those ingredients.
Open next questions
Related open work
Before DONE, this account's open PRs created since the CLAIM at 2026-10-27T11:15:23Z were refreshed. The other new PRs are #5886, #5887, #5888, #5891, #5892, #5893 and #5895. Their bounded NTT storage, signed moments, coframe optimization, two-FULL obstruction, coupled bills, resource migrations and pebble storage quantities do not study dyadic affine feasibility. No common computed number disagrees, and no extra scientific computations were run to check those contributions.
CI notes
At commit
8811e913cef13d3d2d7d0941c791d58c9be78e3b, run 40495794184 failed inplanonly at Onboarding helper tests. All ten failure/error entries are in unchangedtests/test_research_current_assignment.py. The exact final summary isFAILED (failures=8, errors=2, skipped=22).The two errors are
KeyError: 'follow_up_steps'andKeyError: 'catalog_first_step'. The eight assertion failures concern frozen-card counts, missing-helper/reference rejection and sparse-reference receipts. All ten failure/error headers match #5890's failed plan step exactly. This confirms the shared onboarding failure on canonical mainde5ec2e7a6074068452f45b1a191b5c72832df4a. This PR changes only its isolated research package; no shared tests or implementation were changed to address CI.replaywas skipped. Hosted replay has not certified this package; only the local scientific and publication checks listed above have run. No hosted scientific success is claimed.Merge Danger
Door: two-way. Blast radius: isolated. Only
research/dyadic-affine-feasibility/is added.This contribution was produced by Nick Petalas. Credit Ali Romman #5794 at
b67e65c5fcc313f3fcb1e92b199025a63cc1dec7for the bounded dyadic interface and explicit finite-limit distinction. The selected supplier and its credited lineage are historical context only. Independent human and formal proof-kernel review are unclaimed.