Skip to content

A stronger complex supplier: compile-cost-annealed complex modules, five-stage complex saving 7635/10⁷ (+1.17% over #233; no new κ) - #304

Closed
DreamingOfClouds wants to merge 1 commit into
CrocSwap:mainfrom
DreamingOfClouds:research/complex-module-anneal
Closed

DreamingOfClouds wants to merge 1 commit into
CrocSwap:mainfrom
DreamingOfClouds:research/complex-module-anneal

Conversation

@DreamingOfClouds

@DreamingOfClouds DreamingOfClouds commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

A stronger complex supplier (no new κ by itself): re-annealing the three query modules of the
source-assisted complex word gives these five-stage complex savings:

pair recipe this word PR #233's word (PR #256) PR #193's word
PR #233's maximum-weight reuse pairs 7635/10⁷ 7547/10⁷ (+1.17%)
PR #193's parity-avoiding pairs 7586/10⁷ 7474547/10¹⁰ (+1.50%)

The current frontier is bit-bound, about 0.6% below #233's complex price (7.54736·10⁻⁴): #303/#300 at
κ = 7.49983·10⁻⁴ (12:00 UTC Oct 10), and #299 with bit coarse 7.50462·10⁻⁴. This
package raises the complex cap it is approaching from 7.547·10⁻⁴ to 7.635·10⁻⁴. It lifts nothing on
its own, because the bit supplier binds.

python -m pip install numpy==2.3.5 scipy==1.17.0
python3 -B research/complex-module-anneal/verify.py      # about 12 minutes, no network; -O is refused

What changed

There is one new self-contained package, research/complex-module-anneal/, plus its own path-filtered
workflow. No existing file changes. It is built in the mould of #256: the same vendored gcert_emit.py,
Jacob Sussman's gx/gx.py (unchanged) and the PR #233/#202 references.

The source-assisted complex word of #184/#194 calls three PR #168-v4 query modules:

  • the pair module (n = 10, 22 instances);
  • the all-but-one module (n = 9, 110 instances);
  • the disjoint-triple module (one instance).

They were re-annealed against the exact compile ledger of the aligned word, as #285 did on the bit side.
The new modules are not smaller in total (2,462 additions against 2,353), but they are cheaper to compile:
the frame flow needs R = 9,160 slots instead of 9,412.

program (gcert/1, five-stage m = 110, W = 4v + R) modules pairs R N gx.check1 certified a
control PR #168 v4 PR #193 recipe 9,412 262,944 accepted 7469/10⁷
control PR #168 v4 PR #233 recipe 9,412 262,944 accepted 7522/10⁷
result re-annealed PR #193 recipe 9,160 257,400 accepted 7586/10⁷
result re-annealed PR #233 recipe 9,160 257,400 accepted 7635/10⁷

Each certified value has exact rational bounds, and the next 10⁻⁷ grid point is rejected. The controls run
the same recipe on PR #168 v4's own modules: fresh carrier arcs, PR #200's descended frames, then the two
pair recipes. They measure the modules' effect alone: +1.50% and +1.57%.

The recipe is slightly weaker than PR #168's inherited physical layer on the old modules: −0.07% against
#193 and −0.33% against #233. The comparison above is therefore conservative.

What verify.py checks

verify.py checks every pin and rebuilds PR #202's 308 files from the vendored PR #233 package. It runs
two anchors:

Then, for each of the four words, it runs:

Verification

  • Replays: two fresh-copy replays in other working directories (Python 3.14, numpy 2.3.5, scipy
    1.17.0) reproduce every certificate byte for byte.
  • Independent audit: read-only, no package code.
    • Exact two-sided moment bounds reproduce all four values: 7469, 7522, 7586 and 7635.
    • Its own GF(2) label and exact scalar replays agree, as does Sussman's gxcore mirror.
    • It re-checked the modules, pairs and layers, including make_layer.py reproducing all 12 frozen
      layer files.
    • It found no blocker.

Status, honestly

Follow-up (not packaged)

A centre-sharing variant (pair-module root = centre, about 10 lines in Graph.finish) measured about
+2.7% in exploration. It needs a reviewed code change and is left for whoever owns Graph.finish.

Attribution

The module annealing (exact compile-ledger evaluators and annealers, run by Claude Opus 5.5 agents) and the packaging
were prepared by DreamingOfClouds with Claude Opus 5.5 (Anthropic), via Claude Code. Every upstream notice is retained; see
NOTICE.

🤖 Generated with Claude Code

…ive-stage complex saving 7635/10^7 (no new kappa)

New package research/complex-module-anneal (in the mould of CrocSwap#256): the three
query modules of the source-assisted complex word (pair n=10, all-but-one
n=9, disjoint triple) re-annealed against the exact compile ledger. With
PR CrocSwap#233's max-weight reuse pairs the gcert/1 program (R 9,160) is accepted
by gx.check1 and certified at 7635/10^7 in the five-stage layout (+1.17%
over CrocSwap#233's 7547/10^7); same-recipe controls 7522/10^7 and 7469/10^7.
No new kappa: the bit supplier binds. Plus its own CI workflow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@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: Compile-cost annealing of complex query modules.

Review and limits: A stronger complex primitive, not a new multiplication bound. Four complete scalar programs and controls are replayed; the generic layout and inherited all-size interfaces retain the source qualifications. Saved Lean claims are separate from Python admission.

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: 7ac169c58c96cebdb5cd490842331dff3610af62. 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.

2 participants