Repository navigation
Research construction: optimal dyadic-run BIT query batches (no new kappa) - #953
Merged
Mister-Meeseeks merged 2 commits intoOct 13, 2026
Conversation
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.
Completing each PR840 centered BIT shear separately repeats the target's ADDRESS-layout restoration. For a shared target and unchanged source, this contribution batches dyadic indices into consecutive runs: r indices in c runs use 2r+c ordinary recursive children instead of 3r, with no additional full private row. Seed 55 selects
{0,1,2,4,5}: 15 → 12 children, 90 → 72 affine events, ten XOR scans unchanged.Status: recursive-interface research construction; no new kappa. The written proof establishes the exact query minimum only in the uniform target-query/source-XOR alphabet with signed dyadic powers, including arbitrary off-support excursions. Concrete controls show why nondyadic queries and fixed-modulus cancellation lie outside that theorem. The coefficient-aware work and storage recurrence pays every native affine event, full child, source scan, layout return, preparation and tape obligation. This is not a selected supplier, a general circuit lower bound or a measured runtime improvement.
Review entrypoint: research/dyadic-query-runs/README.md. Only that new directory is added, including the proof, literal certificate, deterministic evidence, source pins, local sprint claim and validation record.
Expected:
PASS_DYADIC_QUERY_RUNS cases=63 seed=55 children=15->12 affines=90->72 XOR=10andPASS_DYADIC_QUERY_RUNS_PACKAGE relocation=1 regeneration=2 corruptions=8.Validation:
make verifyin an untouched base archive completed six historical groups, then was deliberately stopped during entrance banks after the mandatorygen4-bank-verifygate separately failed for missing SymPy. No full-suite, selected-supplier cold replay, hosted-CI or formal multiplication-proof pass is claimed.Exact development base:
47481c89fd30a43f8f882eb4b391e89c29273fd0. Direct predecessor: Wentao Li / PR840,da2cd0dd2229e08b61b174a8835a2c2bb99d2230; credit also Karl Appel / PR521, commdata2338 / PR677, and the original OpenAI tape framework. Their original proofs, notices and licenses are preserved with source pins. The selected PR890 certificate is unchanged and remains complex-bound; this local BIT construction supplies no new exponent.The refreshed full queue covered 700 open PRs through #947; the immediate pre-submission check reached #950. PR840 covers one pair; this adds batching across an arbitrary finite dyadic index set and a restricted exact optimum. PR934/943/944 use different multi-source dirty-connector contracts. No pinned coordination issue exists, so the claim and result are local. Main advanced to
007664306fff84fbb1c9a1b4053b69f439764034without changing the selected record. No duplicate of this scoped result was identified.Prepared by Ross Richardson (@RossRichardson) with substantial OpenAI Codex assistance, under Apache-2.0. No independent human review or literature-priority claim. All-size compilation, realization, physical frames/owners, whole-row hosting, tape/precision and analytic transfer remain obligations. Nothing is merged and the selected frontier is not edited.