Repository navigation
Bind the QQ16 F0 rounding witness to physical native execution - #3067
Merged
Mister-Meeseeks merged 1 commit intoOct 16, 2026
Merged
Mister-Meeseeks merged 1 commit into
Mister-Meeseeks merged 1 commit into
Conversation
This was referenced Oct 17, 2026
Merged
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.
The concrete QQ16 F0 scalar-rounding failure in #3036 survives the physical native frame and residual adapters under an explicit mixed arithmetic model: scalar ADD components round nearest-even, while completed native operators remain exact. At significand precisions 8, 24, 53 and 113, the literal 26,099-event native word has exactly two rounding sites and five wrong data fields, although all 480 physical helpers return exactly and all eight private fields return zero. The largest Hilbert error equals the original data norm.
This closes #3036's stated physical binding gap for these four finite cases. It does not round native-child interiors, establish an all-input producer guarantee, supply a complete recursive invoice, admit a supplier or change kappa. The original scalar witness is credited to Arham Tahir/#3036; the unchanged exact vector evaluator is retained from Tekalign/#3017. Nick Petalas/#2965 and the Ali Romman/QQ16/native lineage retain their attribution and premises.
Adds only
research/qq16-f0-physical-rounding/: source pins, exact receipt, literal physical execution and integer nearest-even rounding, the written frame/norm argument, and eight behavioral groups. Internal independent mathematical review checked the marked frames, signed continuation responses, zero residual boundaries, frame rounding commutation and scope; it shares the retained primitive evaluator and is not independent human or formal-kernel review.Validation:
Reproduce:
Scientific and submission main:
d8e0f83f00191df62174b641e9fff055c357f641, priority revision 6, refreshed at 2026-10-16 21:34:37 UTC. Pre-submission overlap fully paginated 304 open PRs including drafts, 1,817 Discussion records and 2,440 closed PR bodies; source heads #3036/#3017 are unchanged. Metadata snapshots are non-atomic and exclude arbitrary diffs and unpublished work. Canonical investigation.The next useful task is an actual finite native producer's grid/dirty-range/internal-rounding and complete paid physical contract. Exact-grid arithmetic remains a valid escape. Family decision: narrow and stop. New work by Ross Richardson with substantial OpenAI Codex assistance, including an internal rounded-networks specialist; Apache-2.0, predecessor notices preserved.