Repository navigation
Conversation
Every correct schedule for the five-source, 31-row connector batch needs at least 72 queries and 74 additions over any set of multi-source toggle calls, and the DUO word attains both. A schedule that contains a weight-5 call needs at least 78 additions; a mixed Q5/DUO word attains 72 queries at 78. The package adds the written proof, a standard-library verifier and the package metadata. It answers the open question of PR3321 and changes no kappa.
… verifier The cover search, the pairing generator and the multiset word generator now use explicit stacks and a next-permutation loop. Every loop has a finite bound, and the cover search enforces a step limit above its measured need. The counts and witnesses are unchanged. The README records the verifier discipline.
This was referenced Nov 3, 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.
Result
Scoped written proof with exact finite corroboration. No κ change. This answers the open question of #3321: can two Q5 calls, or a mixed Q5/DUO/TRIO alphabet, create a new priced point on the five-source, 31-row connector batch?
In the #943/#3321 interface, with every nonempty source subset available as one complete call (one dispatch plus
|S|source additions, no surcharge):72o + 74pfor allo >= 0,p > 0, and(72, 74)is the only Pareto point. No mixture and no number of Q5 calls improves it.72o + 78p, the DUO price plus4p. The bound is attained by a word with one Q5, two DUOs and seven singletons (ten calls, 16 additions). Two or more Q5 calls give at least 80 additions.So a mixed Q5/DUO alphabet does give a priced point that beats the singleton witness
(74, 74), exactly wheno > 2p. No alphabet beats the DUO point at any price. With a per-multi-source-call surchargesigma, the DUO word wins over singletons exactly whensigma < o, and the Q5 word is dominated for everysigma >= 0.New here: the partial-coverage form of the support bound (
T + 2u >= 10, whereucounts rows no boundary pair realizes), the expansion boundA >= 74for every alphabet, the single-point frontier, the weight-5 floor 78 and its attaining word. The full-coverage support bound for steps of weight 1 to 5 is #4137. The 945-pairing census and singleton minimum are #943, the DUO word and the 99,200 ten-point covers are #1531, and the Q5 model and one-Q5 census are #3321. These are cited inputs, recomputed as controls, not audited.Evidence and reproduction
Interpreter:
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12. Any CPython 3.12 works; only the standard library is used. From the repository root:Run locally at head
7ef416e83b8220d0a2f91cb34ea0c3bb9d892154: both verifier modes pass in about 17 s each (PASS_FIVE_SOURCE_TOGGLE_FRONTIER nine_point_covers=0 ten_point_covers=99200 ... weight5_witness=(72,78) no_new_kappa), the package runner printsPASS_REGISTERED_RESEARCH_PACKAGE research/five-source-toggle-frontier outcome=negative-resultin 33 s,--check-onlyprintsPASS_PACKAGE_METADATA_AND_PINS, and the commit check printsPASS_RESEARCH_COMMIT_BYTES.The verifier recomputes from integers:
F_2^5hasP + P = F_2^5(exhaustive search with an exact waste cut, and the affine-basis normal form); the same search finds 99,200 ten-point covers, the count recorded byresearch/duo-toggle-connector;T + 2utable, the Theorem 2 case checks forT <= 40, 30,000 random closed words over all 31 toggles, a 6,000-step hill climb, and nine rejection controls.Limitations and unrun obligations
Open next questions
r((C2)^6) = 14andf(6) = 16, which would give(140, 142). First step: rerun the support and expansion arguments with those invariants. The invariants are cited from an unmerged package.Related open work
CI notes
CI did not certify this result. The
planjob of run 41721283470 at head7ef416e83b8220d0a2f91cb34ea0c3bb9d892154(job 126214604601) was cancelled by the workflow's 10-minute timeout while still in theactions/checkoutstep (21:23:22Z to 21:33:26Z). Thereplayjob was skipped, so no package step ran in CI. The package did not cause this.Checked on other PRs: the
planjob of #6676, #6691 and #6692 was cancelled at the sameactions/checkoutstep after about 10 minutes. Of the 19 PRs numbered 6676 to 6696 whose checks I read, 13 show aplanfailure of about 10 minutes and 6 passed.The result is certified only by the local checks listed under Evidence and reproduction (both verifier modes, the registered package runner, the metadata check and the commit-byte check, all at head
7ef416e83b8220d0a2f91cb34ea0c3bb9d892154).