Repository navigation
Pair-source connector calls: five-source universal path of exactly ten, 72-query support bound attained - #2056
Merged
Mister-Meeseeks merged 1 commit intoOct 15, 2026
Conversation
…ry support bound attained Aaron Wang, with help from opencode. One added operation family (pair-source connector calls B_jk) on research/universal-connector-boundary's five-source model: exact minimum universal source path 10 (construction plus exhaustive nine-point census excluding 9), all-31-nonzero-row batch exactly 72 complete queries (the support bound the fixed alphabet proves unattainable), priced against the predecessor fixture with dirty replay and mutation controls.
This was referenced Oct 14, 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
Contributor: Aaron Wang, with help from opencode.
This PR adds exactly one operation family to the connector alphabet of
research/universal-connector-boundary: the pair-source connector callB_jk: z += B_j x_j + B_k x_k, one complete query per call, charged two coefficient/source accesses and one query record. Everything else of that interface is unchanged (dirty rows, paired readouts, restoration ofz, no free copies).Result on the five-source, all-31-nonzero-row matrix (package
research/connector-pair-source-path-seed2cdb/):The query optimum in the extended alphabet is exactly 72: 62 paired readouts (each nonzero row needs two
A_icalls) plus a source path of length at least 10, attained by the certified word. In the fixed alphabet the same support bound of 72 was proved unattainable by the 945-pairing census, and parity ruled out 73.The word
Closed walk on the five-bit parity space, one step per source query, step vectors of Hamming weight 1 (single
B_j) or 2 (pairB_jk):The prefix set
{0,2,3,5,8,10,13,15,26,30}has full XOR-pair coverage of all 32 masks (verified two ways inverify.py). Each output's twoA_ireadouts go at the two boundaries whose prefix XOR is its row mask; characteristic two cancels the dirty connector. Source multiplicities are(2,4,2,2,2), all even, sozis restored.Why ten is optimal
C(8,2) = 28 < 31, so the prefix set has size at least 9.C(31,8) = 7,888,725nine-point sets finds zero with full XOR-pair coverage; maximum coverage is 29. Two independent implementations agree (recursive DFS in discovery,itertools.combinationsinverify.py --full). So the prefix set has size at least 10.zrestoration), so the prefix set size is at most the walk length; hence the length is at least 10, and the word attains 10.This is a finite computational exclusion for the stated interface, not an impossibility theorem for other circuit models.
Pricing (predecessor fixture)
Fixture: B factor leaf prices
1, 4, 10, 16, 28; eachAleaf price 1; every call doubled for the inverse in the complete cost; dispatchDpaid per root query. Renaming sources preserves coverage, so free relabeling is granted on both sides.At the best labeling this schedule ties the predecessor's leaf cost exactly and saves 2 dispatch records, so the completed cost is strictly lower for any positive per-query dispatch. At the fixed fixture labeling it pays 12 extra doubled leaf charges against 2 saved dispatch records: favorable iff one query's dispatch cost exceeds 6 leaf-price units. The tie at the best labeling is optimal among 72-query schedules: a length-10 source path needs at least one pair call (pure-single ten-call paths are excluded by the 945-pairing census), so its weight sum is at least 12.
Verification
Expected last line:
PASS_CONNECTOR_PAIR_SOURCE_PATH. Checks the word (two independent coverage recomputations), the dirty replay atL = 1,2,3with seeded dense nonsymmetric noncommuting maps over F_2 and arbitrary dirtyx,z,ystate (exact boundary on all 31 outputs), three mutation controls (dropped call, mutated step, misplaced readouts) that must all be rejected, and the pricing numbers.Expected:
CENSUS {"sets": 7888725, "covering": 0, "max_coverage": 29}thenPASS_CONNECTOR_PAIR_SOURCE_PATH_CENSUS. This replays the exact nine-point census behind the lower bound.Expected:
PASS_PACKAGE_METADATA_AND_PINS.Scope and limits
B_jk); a different extension is a different question. Pair calls are charged, never free.a < D/Ediagnostic does not apply: no supplier moment or recursive profile changes here.Credit and provenance
Predecessor:
research/universal-connector-boundary(fixed-alphabet four/five-source boundary, 945-pairing census, 74-query optimum) and #934 (three-by-three result). Task card, scope pins and open next questions are inresearch/connector-pair-source-path-seed2cdb/TASK.jsonandREADME.md. Claim thread: #1166 (comment)Substantial AI assistance: with help from opencode. New contributions are under the repository's Apache-2.0 license.