Skip to content

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

Closed
DreamingOfClouds wants to merge 2 commits into
CrocSwap:mainfrom
DreamingOfClouds:research/complex-p10
Closed

DreamingOfClouds wants to merge 2 commits into
CrocSwap:mainfrom
DreamingOfClouds:research/complex-p10

Conversation

@DreamingOfClouds

@DreamingOfClouds DreamingOfClouds commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

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.

program (gcert/1, five-stage layout at h = 20, m = 100, W = 4v + R) R saving a p = 11 counterpart gain
centre-sharing modules, #233 pairs 6,455 7795/10⁷ #315/#325's centre-sharing program, 7727/10⁷ +0.88%
#304's recipe on annealed p = 10 modules, #233 pairs 6,515 7737/10⁷ #304, 7635/10⁷ +1.34%
control: PR #168 v4 modules cut to p = 10, #233 pairs 7,125 7375/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¹⁰) and wht_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.py and complex_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 network

Why 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.

p 9 10 11 12
five-stage price (·10⁻⁴), mean ± se 6.48 ± 0.06 6.45 ± 0.04 6.30 ± 0.05 6.08 ± 0.05

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.12
and 3.14). No existing file changes. The package follows #304's structure.

verify.py checks all 41 source pins and rebuilds #202's tree from the vendored #233 package. It then runs four
anchors:

Then, for each of the six programs:

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.

Two latent bugs, fixed for p ≠ 11 and documented:

Verification

  • Replays: verify.py passes in fresh copies under Python 3.12 and 3.14 (about 11.5 minutes each), and again
    after the final doc edits. The docs are not read by verify.py.
  • Independent audit by a separate read-only Claude Opus 5.5 agent that I directed, with no blockers:
    • its own replay;
    • Sussman's refcheck.py and gxdry.py accepting both programs;
    • its own 150-digit pricing of all six programs: every claim holds, the next point fails and every coarse b
      floors correctly;
    • an independent decoder check of the control, anneal and centre graphs (921,600 target–source pairs each, 0
      mismatches, centre roots equal to their star sums);
    • the patch re-applied byte for byte, both bug fixes reproduced, and the module cuts reproduced.
  • Lean (local; not pinned in the package):
    • Setup: wht-power-saving-lean at f010392 (Lean v4.34.1, Mathlib d13f23b) with his unchanged
      tools/gx/regen_check.py.
    • Build: 31 of 31 modules built per program with 0 errors, one kernel check at a time.
    • Comparison: tools/Compare.lean passes against challenges that differ from ChallengeB2Gp193x only in names
      and exponent.
    • Axioms: propext, Classical.choice and Quot.sound.
    • Hashes: the checked gcert hashes (370fae73…23ff and 433848305e…16e5, uncompressed) equal the
      certificate_sha256 values in expected.json.
    • Not run: the official comparator and a build from nothing.
    • Scope: this covers the Walsh–Hadamard saving only, not any κ assembly.

Status, honestly

CI note. This branch also carries Rohan Arun's #318 commit, cherry-picked unchanged (it re-pins the root
Makefile and README.md hashes in research/joint-dual/SOURCE.json). Without it the repo-wide verify (…, 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

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

DreamingOfClouds and others added 2 commits October 10, 2026 13:37
…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)
@Mister-Meeseeks

Copy link
Copy Markdown
Contributor

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: 40ed0456ab1990beb3440e61bb883ccf95fdcea4. Publication: 4040a0f46d67b41c36a472a7cd4af791fd4c36cc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants