Repository navigation
A p = 10 complex supplier: five-stage complex saving 7795/10⁷ (centre-sharing) and 7737/10⁷ (#304 recipe), both kernel-checked in Lean (no new κ; raises the complex cap above 7727) - #327
Conversation
…10^7 centre-sharing, 7737/10^7 CrocSwap#304 recipe; no new kappa) The source-assisted complex word of CrocSwap#184/CrocSwap#194 compiled with CrocSwap#304's frozen recipe at p = 10 (h = 20, 960 ports) on query modules re-annealed at p = 10, priced in Sussman's generic five-stage B2 layout at h = 20 (m = 100, W = 4v + R). Six gcert/1 programs (control, anneal, centre-sharing; parity and mw pairs), each regenerated and checked by verify.py (pair checks, PR CrocSwap#200 admission, PR CrocSwap#184 flow and lift, CrocSwap#194 contract, gx.check1 with the exact scalar identity and gxcore, exact five-stage price). Fixes two latent p != 11 bugs (pairs_mw gauge rank; dropped-gauge births in the record), documented. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The "Verify research artifacts" workflow (make joint-dual-verify) fails on main and on every open pull request since the root Makefile and README changed (AssertionError: Makefile in joint_dual_compose.check_sources). Regenerated with scripts/experiments/pin_joint_dual_sources.py; verify_joint_dual.py and tests/test_joint_reclaim.py pass (16 tests) under Python 3.11. The joint-dual certificates only change in their recorded source-manifest hash. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> (cherry picked from commit a45747d)
|
Thank you @DreamingOfClouds. This contribution is now retained on main in the scoped 100-PR review and contributor credits. Contribution: p10 centre-sharing and annealed complex suppliers. Review and limits: Primitive improvement only. Six complete programs and their exact prices are checked; included historical Lean receipts are distinguished from a new maintainer kernel build. The complete original source, notices and relevant execution evidence are retained through the pinned source archive. The review distinguishes fresh local runs, source-bound historical Linux CI and prior exact-head review; it does not claim 100 fresh full mathematical audits. Closing this historical PR as reconciled. This preserves parallel and cumulative credit without replacing the selected frontier or promoting priced research targets to completed constructions. Reviewed head: |
The complex supplier at cube size p = 10, with no new κ by itself. The source-assisted complex word of #184/#194
is compiled with #304's frozen recipe one cube size down. It has h = 20 and 960 ports, against h = 22 and 1,320 ports
before. The query modules were re-annealed at p = 10.
In each row the next 10⁻⁷ point is rejected, and both claims also hold with the 10⁻¹⁶ fallback. A five-stage
package would consume these fallback-inclusive coarse savings:
Each is certified by two independent rational moment engines.
Both headline programs were also kernel-checked in Lean with Jacob Sussman's unchanged generator, as
wht_main_block_B2Gcc95x(1 − 7795973/10¹⁰) andwht_main_block_B2Gcp37x(1 − 7737183/10¹⁰). Details are below.As far as I know, these are the first h = 20 programs built with his chain.
Why this matters now. The open frontier is the community stacks on the p = 10 bit word (#315 and #325), and
they are approaching the 7727/10⁷ complex cap of #315/#325. A κ package that adopts this supplier raises that cap to
7.796e-4 (+0.89%). This PR does not make that change. #315's package pins its p = 11 complex program in five places,
which a κ package must generalize or re-pin first:
code/complex_labels.py,complex_scalars.pyandcomplex_splice.py(h = 22, v = 1,320, 22 centres);portable_complex.py;math_check.complex_supplier().PROOF.md§5 lists what each pins. The programs are in the star form those checks read.python -m pip install numpy==2.3.5 scipy==1.17.0 python3 -B research/complex-p10/verify.py # about 12 minutes, no networkWhy p = 10 on the complex side too
The five-stage price favours smaller cubes. With a ≈ D/L, the deficit per port D/v = 4 − 15/(p − 2) saturates,
while m = 5h keeps growing. On an ensemble of library-module draws, with one recipe for every size, the complex
word prices as follows. These are measurements on this pipeline, not certificates.
Single draws mislead, because their spread (about 2%) is as large as the size effect. The edge comes from about 4%
fewer helper registers per port at p = 10. Cutting #304's p = 11 modules straight to p = 10 gives only 7235/10⁷, so
the gain comes from re-annealing at p = 10.
What changed
There is one new self-contained package,
research/complex-p10/, plus its own path-filtered workflow (Python 3.12and 3.14). No existing file changes. The package follows #304's structure.
verify.pychecks all 41 source pins and rebuilds #202's tree from the vendored #233 package. It then runs fouranchors:
aligned_word_p.pyat p = 11 reproducessource_aligned_local_v4.py's seven outputs byte for byte;give (42, 21, 46, 4) at h = 22;
Graph.finishcentre patch builds the same graph ascentre46.py, and changes nothing for a36-root pair module.
Then, for each of the six programs:
physical();gx.check1with the exact scalar identity and thegxcoremirror on the rawand normalized program, plus a flipped-sign control rejected by both on E5.
the 10⁻¹⁸ coarse b by two engines.
expected.json.The layout at h = 20 is Sussman's bridged five-stage B₂ formula with the h-dependent idle climbs: H₅ = 5·H_inv +
2v(e_{2h−2} + e_{h−1} + e_{2h+2} + e₄), m = 5h, W = 4v + R. That gives ranks 38/19/42/4 and deficit 2,040 here.
bankPrice h,bridge2_gcert,GX.wht_of_halves, andgxunitfrom
BANK['B2'].Two latent bugs, fixed for p ≠ 11 and documented:
pairs_mw.pyhard-codes the gauge rank f = 18, which equals h − 4 only at h = 22. At p = 9 itreturns no pairs.
pairs_mw_p.pyuses f = h − 4, which is identical at h = 22, and on these layers it changesnothing.
source_aligned_local_v4.pykeeps the births of gauges it drops in its record. On the control's cut modulesthis makes PR A stronger bit supplier: fixed-coordinate and face-diagonal bit local circuit on PR168 v4 (effective bit saving 6.7734e-4) #200's checker reject the word.
aligned_word_p.pyreverses exactly those births. That ischecked, not trusted: the checker recounts the record from the word. Nothing changes when no gauge is dropped,
as anchor (a) shows byte for byte.
Verification
verify.pypasses in fresh copies under Python 3.12 and 3.14 (about 11.5 minutes each), and againafter the final doc edits. The docs are not read by
verify.py.refcheck.pyandgxdry.pyaccepting both programs;floors correctly;
mismatches, centre roots equal to their star sums);
tools/gx/regen_check.py.tools/Compare.leanpasses against challenges that differ from ChallengeB2Gp193x only in namesand exponent.
propext,Classical.choiceandQuot.sound.certificate_sha256values inexpected.json.Status, honestly
m = 100.
prices are therefore not a bound.
priced by the chain.
CI note. This branch also carries Rohan Arun's #318 commit, cherry-picked unchanged (it re-pins the root
MakefileandREADME.mdhashes inresearch/joint-dual/SOURCE.json). Without it the repo-wideverify (…, joint)job fails on main and on every open PR. The commit is identical to #318's and drops out once #318 is merged.
Attribution
Graph.finishframework and Source-assisted common-frame compression for conditional kappa = 6.566436e-4 #184's frame flow and exact lift.source_aligned_local_v4.py.gx.check1,gxcore, the five-stage layout and the Lean chain.bit word).
The module annealing, packaging, audit and Lean runs were prepared by DreamingOfClouds with Claude Opus 5.5
(Anthropic), via Claude Code (Claude Opus 5.5 agents). Every upstream notice is retained; see
NOTICE.🤖 Generated with Claude Code