Repository navigation
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.
This source-bound construction supplies a literal rounded alternative at the exposed half-ADD in PR #7660, and proves that this one rounding error reaches native return with gain exactly one, only in public role 210. It affects no other public field or owned erasure. No new kappa or complete caller admission is claimed.
Read the proof, checked result, verifier, candidate source pins and retained runtime inputs. This answers the narrow scalar question in the source review request.
The exact candidate head is
d12b854d4825e9edfa3a3466909e1abf3525e929; its decoded word SHA256 isf0753b6614b2d351723dddc307a39b6ecd748a43008c6fdb9335b01feeec9669. At zero-based clock 100504,ADD 210,457,-1/2follows the chart-218 MOVE. The unchanged PR #6988 compiler and lifecycle service computex-floor(y/2)for every canonical signed field whose rounded outputs fit. The exact local token selects a 669-row table. Both odd signs work; source and context remain unchanged, successful heads return, and both work banks are retired. A late overflow protects the whole public target.The new dependency certificate inspects all 49,504 later events. Only the ADD into role 210 at clock 100527 touches that field; nothing later reads it as a source. Thus the real-component error
Delta*(y mod 2)/2remains isolated and unchanged. Its sharp Euclidean bound for N complex entries isDelta*sqrt(N/2). The 512-entry odd-pair fixture attains that bound. The exact dependency argument is corroborated by separate forward and backward envelope passes.The retained all-size primitive proof specializes to
512(S+1)+64R+7(A_0+A_1)+16Q_cphysical/control units. It charges source reads, staging, copying, head return and retirement. The two work banks retain historical backing. Setup and other fields remain separate charges. This is not an exchange into the old ordinary tariff.Use Python 3.12 and the standard library:
Expected output includes:
Local normal and optimized isolated replay passed. All 1,364 signed scalar pairs at widths 1 through 5 were checked: 1,193 successes and 171 correct range rejections. Further literal checks cover the 512-entry field, dirty reuse after failure and six semantic/source controls. Committed bytes, source ancestry, official export and read-only Git-free replay passed. Hosted CI did not certify this package. The plan job failed in the shared
test_current_ci_section_matches_selected_record: the base guide still names frontier6030, while the selected record requiresmake frontier7000-verify. The log reports 760 tests, one failure and 24 skipped; package replay was skipped. The new package changes no shared CI file. Local replay remains the verification evidence.Limits: this changes the local numerical service to rounded semantics. The fixtures are primitive inputs, not full native-prefix traces, and the fixture invokes the unchanged primitive method rather than the complete recursive Controller. Final signed range remains an explicit input/output contract. The other half-ADD at 100527, all other services, all 17 caller bindings, complete rounded error transport, common physical tariff, native provider, private backing schedule and outer recovery remain open. The five framework assumptions remain
native_all_columns,owned_erasure,compiler,precision_tapeandanalytic_recovery. The full selected replay and complete rounded caller were not run.Base:
e54523517d0f03e58352e647c403a5af3e525a57. @Clear1nsight supplied the exact candidate and review request; the retained source notice records the native lineage and predecessor credit. @CubeJerry supplied the unchanged scalar compiler, lifecycle executor, physical fixtures and general proof. The new work is the current consumer binding, explicit charge specialization and terminal-error theorem. Ali Romman directed it with substantial OpenAI Codex assistance. New work is Apache-2.0; source licenses and notices are retained.