Skip to content

Reduce complete first P104 fold time by 29.94% (no new κ) - #6187

Merged
Mister-Meeseeks merged 1 commit into
CrocSwap:mainfrom
petalas:research/w9-1029a-new-obstruction
Oct 29, 2026
Merged

Mister-Meeseeks merged 1 commit into
CrocSwap:mainfrom
petalas:research/w9-1029a-new-obstruction

Conversation

@petalas

@petalas petalas commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Accelerate the complete first P104 shadow-relay fold from PR6170 while preserving its complete output word and acceptance decisions. This is an empirical tooling improvement with a scoped solver-equivalence proof, not a new kappa or supplier audit.

 solve(A, b)
-  reduce every row above and below each pivot
+  eliminate below each pivot
+  substitute backwards with the same pivot columns and zero free variables

The output word and fold construction remain DreamingOfClouds' work. Standard Gaussian elimination is background. This contribution adds the measured solver integration and its reproducible equivalence evidence.

Evidence

Proof and package.

Median complete-fold time falls from 127.86 s to 89.58 s, a 29.94% reduction, across five alternating pairs. Baseline range is 123.44 to 132.11 s; candidate range is 86.47 to 91.41 s, on the recorded shared macOS host. All ten commands succeed with zero output differences.

The generated BENCHMARK.json supplies five alternating complete-command pairs, including source authentication, both tried variants, unchanged checks and output serialization. Every run must emit the same canonical 22821-event word and FOLDED report. PROFILE.json puts 75.6 of 83.3 discovery-profile seconds in the original solver; that untimed rejected-variant profile is separate from the benchmark.

Exact reproduction from the repository root, CPython 3.12 and NumPy 2.5.4:

/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/research_package.py --package research/p104-fold-elimination
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/check_research_commit.py --package research/p104-fold-elimination --check-source-history
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B research/p104-fold-elimination/verify.py

Both registered normal/optimized checks pass. Direct warning-strict commands take 70.89 s and 71.68 s, each checking 1234 systems, five rejection controls and both complete accepted solver variants. The registered run takes 143.68 s total. Committed bytes, executable modes and declared source-history ancestry pass for all 16 package files at 9a7f206d4e9812d2eec042aed6e40acadacd534d.

Official export/input integrity passes. Optimized replay with Git absent and all exported files read-only passes in 70.45 s; all 17 exported files retain their bytes and modes.

The package README gives the full timing command and minimal retained-source extraction. RETAINED.json identifies all 50 predecessor files by original Git blob and SHA256 at PR6170 head 445fb9124eb3fcb5d4f342c476b9ae3637f185aa; the archive is self-contained. No predecessor source is edited.

Limitations

One shared macOS host and the first H705 fold on the shipped PR6030 word are measured. Solver dimensions are capped at 4096. The retained projection and legality oracle keep their existing scope. Warning-strict controls expose unchanged tkcommon profile-loader ResourceWarnings; these are documented and not suppressed. Full rebuild timing, native/caller/compiler/precision/BIT/outer and formal-kernel checks are unrun. The five selected framework assumptions remain. Independent human and formal proof-kernel review are unclaimed.

Related open work

The completion refresh inspected all fifteen other open account PRs created since the advance CLAIM. None supplies a competing fold-solver result or a number for this same complete-fold workload. No extra mathematical computations were run to check other contributions.

Open next questions

  • Does the same substitution help all remaining fold sites and the complete rebuild? Compare every word and acceptance status along that full path.
  • Can consecutive Newton systems reuse an exact factorization? First establish a certified relation between those actual matrices.

CI notes

Both hosted checks passed at exact head 9a7f206d4e9812d2eec042aed6e40acadacd534d in run 40886077177. Plan passed in 4m23s; replay (research/p104-fold-elimination) passed in 9m27s. The completed check list was read once and both entries report pass.

Hosted replay certifies the registered normal/optimized conformance checks at this head. It does not independently certify the local performance percentage or supplier admission. All recorded local checks also passed. No code changed after these checks. Independent human and formal proof-kernel review remain unclaimed.

Merge Danger

Door: two-way.

Blast Radius: isolated. The new package is opt-in and changes no shared solver or selected frontier.

@Mister-Meeseeks
Mister-Meeseeks merged commit 8c6b69f into CrocSwap:main Oct 29, 2026
2 checks passed
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