Repository navigation
Conditional κ = 0.001601486955392486: PR576 kernels with A-entrance 5-to-4 promotions and PR575 plain joint prefix - #582
Conversation
… 5-to-4 promotions and PR575 plain joint prefix
|
Thank you @jeremykothe2. This contribution at The #587 fixture reconstructs this exact declared witness twice (generation and strict replay) and compares all published expected construction/provider/global fields. This is the proposed execution coverage for #582, not a claim to have run its original standalone driver. Full fixture completion and input binding remain required. Preserved implementation and research: The family review and individual disposition record the scope, evidence and attribution. Parallel and intermediate contributions remain credited even where a later composition has a stronger bound. The published multiplication bound remains conditional on the documented compiler, realization, hosting and analytic assumptions; these finite checks are not a full Lean multiplication proof. |
Summary
Conditional κ = 0.001601486955392486. This is +2.27e-7 over PR579 (0.001601260169988325) and +3.28e-7 over our PR578. The conservative model gives 0.001601486952579549.
This PR combines three existing providers with one new provider:
build_entrance_promotions.py. The 12 kernels are re-applied after the promotions, and they still give an exact zero dirty response.build_joint_prefix.A new literal owner map hosts all 72 calls. The paid profile is
{1:174540,2:40064,3:23928,4:14024,5:4038,6:4032,8:576,30:1,48:1857}.How it was found
Package
research/complex-571-free4f/contains 17 files. Four sources are pinned externally by manifest and file hashes, and nothing is copied from them:research/complex-multicold,71c99ac);research/larger-gain,897213a);research/structural-gain,b7bdc5a);research/complex-joint-prefix,eac6f7e).The package is fully data-driven.
data/SPEC.jsondescribes each provider as a typed chain of build steps (pinned base word, thenpromote,greedy_kernelsorjoint_prefix, each with its paired omission and coverage audits), plus the dispatch, the owner and plan hashes, and every expected value. The singleverify.pyandcode/contain no witness constants. They rebuild every provider from the pinned sources, recompute everything, and compare the results with the spec.Verification
PR568, PR569, PR571 and PR575 are not merged, so fetch their pinned commits first:
Add
--check-pinsto check only the package and source pins.verify.pyuses only the standard library. It runs:Local result (Windows, CPython 3.11.11):
PASS_FREE4F_NATIVE_COMPLEX_AND_CITED_BIT, κ 0.001601486955392486, 38/38 stages exit 0, 371 s. A fresh clone of this commit is byte-identical to the verified package tree, its committed blobs equal its MANIFEST, and its pin check passes. A second official run from that clean clone of commit 747ec97 also passed:PASS_FREE4F_NATIVE_COMPLEX_AND_CITED_BIT, κ 0.001601486955392486, 38/38 stages exit 0, 371 s.GitHub CI has not run, and I make no claim about it.
Credits
AI disclosure and authorship: Claude Opus 5.5 (Anthropic), running in the omp coding harness, did the work for this PR: the promotion search, the screening, the owner solve, the spec-driven package and this description. Jeremy Kothe (jeremykothe2) directed and reviewed it and is submitting it.
Scope
The result is conditional on the inherited all-size compiler, common-label/mutable-source realization, whole-call hosting, precision/tape/exact recovery, analytic transfer and the bit H1–H5 assumptions. It is finite exact evidence. It is not an unconditional theorem, a complete Lean proof, or a practical speedup.