Repository navigation
Charge cubic radix setup in source-directory production - #2590
Merged
Merged
Conversation
This was referenced Oct 19, 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.
PR2569's unchanged source-directory producer reconstructs the radix exponent for each of its m² high-field coordinates. That makes the CH cardinality setup cubic in w, rather than the stated
O_q(w log(C+1)+w²). This source-pinned audit gives the exact division write bill and corrects the setup bound. It also proves that complete directory production remainsTheta_q(D)in its actual serialized output extent, including this setup and local cleanup.For L-bit words, every retained unsigned division writes exactly
3L²+8L+4+(3L+2) popcount(quotient). Thehigh_powercall performs exactly m²w divisions and m²wL full-width shift iterations, even when the dividend has leading zeros. Its sharp setup order isTheta_q(w³+(w−1) bitlength(C)); making the fresh C copy givesTheta_q(w³+w bitlength(C)). At w=1 the unchangedhigh_powerperforms no multiplication and need not read C.The complete
Context/produce/Context.closeinterval performs((2m²+1)w+1)divisions. Its output hasD=CH(h+1)(B+2+m²(L+1))cells, withH=q^(m²(w−1)). The proof absorbs the corrected cubic setup into D directly. The separate payload statementD=O_q(V)still needs PR2569's h/w/R premises; this audit does not refute its final volume-based asymptotics.Validation: native CPython 3.12.7 registered optimized primary and all four export/integrity groups pass; native CPython 3.14.5 optimized primary passes. Sixteen setup cases cover w through 32, a 129-bit C and m=64/w=1. Eleven complete directory cases check exact serialized order, repeated/empty physical prefixes, ownership, cleanup and meters. Four semantic controls and typed receipt/source corruption tests accompany the written all-size argument.
Independent AI review found no material issue in the stated scope. The reviewer separately derived the division formula and cubic absorption, checked 166 direct-source divisions at L=2..11, authenticated all 11 retained source/proof files, and passed the registered replay plus all four export groups.
Scope: fixed q>=3, fixed 1<=m<=64 and finite compiled request catalogue, canonical cardinality tapes, and the retained fixed-alphabet Tape/Word meters. Input fixture/vocabulary compilation and returned directory/Count disposal lie outside the measured interval. Python controller/allocation costs, a literal fixed-tape compiler, numerical reserve constants, full selected packet/route execution, recursive hosting and supplier/exponent admission remain open. The producer and selected record are unchanged.
Source pins: PR2569
0b116cb34f27a4b064f0d8dd65549ea5705cf9c0; credited primitive/division audit PR2566bfe8317a38f03a5693470e873b29101f3f7a55e4. Every retained source has SHA256 and Git-blob authentication before execution. Direct base is current canonical main0fdd7d82de03e43c9e5a1000dfbcd380d1b687d2, priority revision 4. Thebit-helper-contractpicker refinement and bounded overlap coverage are recorded in TASK.json. Canonical advance claim: #2569 (comment).Credit Jose Manuel and the retained source lineage, and ywz65's prior cost audits. Prepared for ywz65 with substantial OpenAI Codex assistance. No human or formal-kernel verification is claimed. Open next questions concern sharing the encoded exponent traversal with a complete bill, and pricing the full caller's directory reserve.