Repository navigation
Conversation
This was referenced Nov 11, 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
Scoped written proof with exact finite corroboration: the complete once-rounded MOVE of CubeJerry's #6996 admits a smaller sufficient lifted-record allocation. Write g=r*f and k=ceil(g/2).
The new source-interface substitution preserves every exact Gaussian prefix, both serial monomials, the original absolute phase, final nearest-up rounding and true final-overflow contract. It saves s+1 component bits at g=2s and s bits at g=2s+1. At g=8 the saving is five bits per real component. The example h=2, f=1, r=8, 4096 complete records and one complex coefficient reduces the widened coded field from 417792 to 294912 bits. This is an exact record-size calculation, not a physical run or total runtime claim.
The source domain is #6996's retained #6030 raw catalogue. Its placement in the currently selected #7000 caller remains open. Only seven files under
research/sharp-rounded-move-allocation/are added. No frozen provider, selected record or rank invoice changes.The allocation proof and new reference were produced by Nick Petalas. Credit CubeJerry #6996/#6989 for the complete source contract and variable lift/drop codec; Alejandro Zarzuelo Urdiales #45, Jose Manuel / jmbarrancoml #3091 and Nick Petalas #2772/#3089 for the cited sharp Gaussian denominator/row-norm and prefix facts; and the monomial, cutoff, native and tape lineage retained in those sources. The Gaussian facts are cited inputs, not claimed as new or re-audited. Independent human and formal proof-kernel review are unclaimed.
Advance CLAIM. Canonical base and refreshed main:
e54523517d0f03e58352e647c403a5af3e525a57, priority revision 8. The card is explicitly changed to a local precision/storage side result.Evidence
2b882fd2834303655f82d084e25dc551f67e9784. The publication preflight authenticates eleven package/input files and the declared canonical ancestry.Exact reproduction from the repository root:
Other machines may substitute their CPython 3.12 interpreter path. Scientific marker:
PASS_SHARP_ROUNDED_MOVE_ALLOCATION; registered marker:PASS_REGISTERED_RESEARCH_PACKAGE; publication marker:PASS_RESEARCH_COMMIT_BYTES.--emitcomputes the receipt from current file hashes and checks, without writing a checkout artifact.Limitations
This is a sufficient allocation substitution theorem under the retained provider premises. The literal Count/Tape substitution is unimplemented, and no physical whole-MOVE execution is claimed. Finite endpoint checks use two explicit abstract monomial pairs, not actual selected source recipes; they do not replace the proof or inherited contracts. The containing error fibre still includes all 9f native axes.
All fixed roles, protected stages, both serial repetitions, constructor/source/control work, restoration and historical backing remain charged. The complete bill must be recomputed at the smaller physical widths. No paid/productive rank saving, new kappa, supplier admission, actual #7000 caller mapping or complete multiplication theorem follows. All five selected framework assumptions remain. Physical execution, selected cold replay, Lean, Docker, independent human and formal proof-kernel acceptance are unrun or unclaimed.
Open next questions
Related open work
Targeted open searches found no other PR on the retained #6996/#6030 lifted-record allocation. Main README searches included the general tensor/prefix formula and exact width shape; merged searches, recent account contributions, current handoffs and local reservations were checked. Cached coverage included 502 open PRs and 7176 Discussion records with complete reported pagination; sparse local notes, arbitrary diffs and unpublished work remain limitations. No extra scientific computations checked another contributor's result.
The completion refresh read this account's nine other open PRs created since the CLAIM: #7203 through #7208, #7210, #7212 and #7213. Their titles and relevant body text concern distinct feedback, connector, Schur, idle-coalescing, fixed-line crossing, mode-shadow, recovery-cycle and formal-group questions. None targets this lifted-record allocation or computes a conflicting shared quantity. No extra scientific comparison computation was run.
CI notes
CI did not certify this package. At unchanged head
2b882fd2834303655f82d084e25dc551f67e9784, run 43013361819 failed in plan job 130498228533, stepOnboarding helper tests. The package replay job was skipped because planning failed. Automated evidence for this package remains local.I read the checks once and confirmed the job log. Exactly one of 760 tests failed, with 24 skipped:
test_research_current_status.CurrentCiNavigationTests.test_current_ci_section_matches_selected_record. The AssertionError says that`make frontier7000-verify`was not found in the CI verification document. Direct inspection of canonical maine54523517d0f03e58352e647c403a5af3e525a57confirms thatcertificates/selected-result.jsonnamesmake frontier7000-verify, whiledocs/ci-verification.mdstill describes #6030 andmake frontier6030-verify. The selected record, CI document and test are unchanged by this PR. This is a base-repository navigation failure.I also read the failed logs of all six comparison runs below. Each has the same failing test and missing command, the same 760-test total, one failure and 24 skips, in
Onboarding helper tests:No repair, retrigger commit, push or job rerun was made for this repository-level failure. The local registered and exported evidence described above remains unchanged; no hosted scientific pass is claimed.
Merge Danger
Door: two-way. Blast radius: isolated. This adds one research package and its opt-in replay, without changing a shared implementation or the selected frontier.