Repository navigation
Conversation
This was referenced Nov 2, 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
Eliminate 11,470 interval exponential evaluations in the complete PR2313 Gaussian recovery replay while preserving every computed interval endpoint and all scientific output. Claim type: scoped implementation-preservation proof, exact work reduction and finite conformance evidence. No runtime improvement or new kappa is established.
The new proof includes the actual finite truncation, per-summand outward rounding and final tail unit. The source-bound adapter changes only expansion setup. It computes 76 rows directly and reflects 60; all 136 rows remain available to the eight completed setup paths. Reflection is classical; the exact interval-preserving substitution and work reduction are the new contribution.
This contribution was produced by Nick Petalas. Credit Mason Hale / PR2313 for the backend, interval arithmetic, numerical/recovery proof and controls; Cinna Davis / PR2298 for its caller question; and the unchanged Harvey–van der Hoeven, Gaussian, CRT, Neumann-rounding and numerical lineage in the retained NOTICE. Predecessor mathematics is cited, not an audit deliverable.
Proof, package, advance CLAIM, scope/timing finding.
Evidence
3376b28a77491fd3d11b0e93724025211c3afd6b. The official committed export and input-coverage/integrity check also pass.Reproduce from the repository root, CPython 3.12.15, standard library only:
Other machines can substitute their CPython 3.12 executable. Expected statuses are
PASS_GAUSSIAN_EXPANSION_REFLECTION,PASS_REGISTERED_RESEARCH_PACKAGEandPASS_RESEARCH_COMMIT_BYTES. All generated verification reports bind the executable sources and manifests; no mathematical receipt is handwritten.Limitations and unrun obligations
This is an isolated coefficient-setup module for the pinned dense reference backend. It supplies no fast sequential backend, physical movement/cleanup tariff, new precision policy, native/caller admission or compiler/stock/outer theorem. All five inherited framework assumptions remain. The selected frontier is unchanged. The universal preservation proof is written, with finite executable corroboration; independent human and formal proof-kernel review are unclaimed.
Selected cold replay, physical native/tape execution, Lean and Docker were unrun and are outside this claim. The export's integrity was checked; an additional exported scientific replay was not run. No required local check was deferred to CI. The initial complete-runtime prediction is narrowed to exact work reduction, as recorded in the finding.
Open next questions
Can an actual fixed-tape Gaussian coefficient producer exploit the reflection with a favorable complete movement and cleanup bill? Start by binding one emitted table and its sequential order, then price the reflected reads, writes, head returns and cleanup. That physical producer and tariff are missing here. Optimization stopped at this first verified work reduction; no follow-up is reserved.
Related open work
The refreshed exact-backend search found no open PR studying PR2313 periodic expansion setup. Nearby Gaussian work has different contracts:
PR6404 gives a determinant/rank obstruction for a linearly truncated Gaussian Schur boundary; this package changes periodic expansion coefficient generation and computes no cross-rim determinant.
PR6405 gives a sharp sign range for linearly truncated real Gaussian kernels; this package makes no sign-range or Schur-fill claim. No additional computations checked either contribution.
PR6412 gives an adjacent-modulus remainder correction tree at a different arithmetic stage; it changes neither this Gaussian expansion matrix nor its setup counts. No common numerical output is compared.
Completion refresh inspected the fourteen other account PRs created since the advance CLAIM. No additional exact-backend overlap or conflicting computed quantity was found. Searches cover retained public evidence and the live claim/PR scope, not unpublished work or arbitrary historical diffs.
CI notes
Both hosted checks passed at exact head
3376b28a77491fd3d11b0e93724025211c3afd6bin run 41529237574:planandreplay (research/gaussian-expansion-reflection). The completed checks were read once; separate run metadata confirms successful completion at this head.Hosted replay certifies the registered normal/optimized conformance and complete retained caller checks, plus package/input validation. The universal preservation argument remains a written proof. All required local checks listed above also pass. No CI failure remains, and no runtime improvement, new kappa, supplier admission, independent human review or formal proof-kernel acceptance is implied.
Related open work was refreshed against this account's open PRs created since the CLAIM. Fourteen other contributions were inspected; no additional PR studies the exact periodic-expansion setup quantity, and no common computed number disagrees. No extra computation checked another contribution.
Merge Danger
Door: two-way; the isolated package can be reverted.
Blast Radius: isolated. Ten new package files; no shared implementation, predecessor source, pinned evidence or selected-frontier file is changed.