[unpaidmoon]

Change and mathematical scope

Negative result for one named caller. No new κ. The selected conditional exponent stays 781451/250000000. The five framework assumptions remain.

The recorded PR5679 component is

C = 3507410738409/1000000000000000

from research/g20-helper-split/ORDINARY-RESULT.json, with whole_kappa null. This package does not reopen the selected pricing assembly's stock gate and does not change the cover inside that assembly.

The caller outside that assembly is physical in research/p104-productive-controller/caller.py. The selected verifier loads that module and calls C.physical(caller, word) before pricing.run. The function's parameters are word and local, with no defaults and no parameter named bit_saving.

At that call, the first argument is the controller returned by construct(), which the verifier requires to equal CONTROLLER.json. That object has no bit_saving field and does not contain the numerator of C. The second argument is the regenerated edited word held in the verifier's variable word. It is not the replay dictionary the verifier names local, and it is not C.

physical contains one copy of each Gaussian check: "Multiply the Gaussian pair twice with exact real and imaginary parts." and "All idle Gaussian axes". Its only direct return statement builds a dictionary whose keys include whole_idle_jobs and do not include bit_saving. There is no bit_saving input that can be set to C, so this caller does not consume C. physical was not executed. No execution receipt is claimed.

pricing.run is a different function. Its parameters are local, native, word, physical. Inside the body, after atom > ordinary > admitted > TESTED, it assigns 'bit_saving': admitted and passes that dictionary to the PR4359 ledger. That assignment is the assembly already rejected for C. It is not this caller.

At base commit 7c49fe32c55de02c2c873655c804b16e4c3fef0a, git ls-tree -r --name-only lists exactly 15 paths whose final component is caller.py. None of those blobs contains bit_saving. Exactly seven contain Gaussian or gaussian. Five of those seven are blob 6ac5e735691555ecafe2afbcff71edd923178113, the named file and four retained copies. The other two, research/native-involutive-dual/caller.py and research/physical-boundary-rhs-caller/caller.py, do not define physical. This is an exhaustive finite census of that filename at that commit. It is not a proof that no function outside those files can accept C.

Task and overlap

Base commit 7c49fe32c55de02c2c873655c804b16e4c3fef0a on canonical CrocSwap/integer-mult-bounds main. This fork draft is based on cursor/upstream-7c49fe32-pin-cc03, which is that commit, so the diff is this package. It is not an upstream pull request and it does not change the selected frontier.

Priority revision 8. Catalogue card supplier-boundary-audit. Scope status: refined. The card asks whether one changed supplier has complete native, caller, ordinary and outer admission coverage, and says to stop at one resolved gap. The gap taken here is the caller the selected verifier loads before pricing.run.

The question is open question 2 of the note on discussion #1166, comment 19492491, recorded in fork PR 149. A neighbouring task owns a different cover inside the same ordinary formula. This package does not take that cover.

Overlap at 2026-11-10T02:08:04Z searched 885 open PR bodies and 6,934 discussion records, plus the local notes at 7c49fe32. Status POSSIBLE_OVERLAP_NOT_A_NOVELTY_CERTIFICATE. The search hits the source comment, the PR5679 ordinary notes, and the income audit that uses this same caller.py for a different theorem. No open PR states this caller's parameter list. No matches is not proof that a hidden diff is absent.

The family-status expansion gate was not opened. This package does not extend a construction.

Validation

Environment: Python 3.12, standard library, and local Git. Head 95659908a8cd692f54026cd69795a86d6b0067aa. From the repository root:

python3 -I -W error -B research/gaussian-caller-outside-pricing/verify.py
python3 -I -O -W error -B research/gaussian-caller-outside-pricing/verify.py
python3 -B scripts/research_package.py --package research/gaussian-caller-outside-pricing
python3 -B scripts/check_research_commit.py --package research/gaussian-caller-outside-pricing --check-source-history
python3 -B scripts/research_selected_baseline.py

Observed:

• both verifier modes print PASS_GAUSSIAN_CALLER_OUTSIDE_PRICING, with bit_saving_input null, named_caller_consumes_C false, and physical_executed false
• the launcher prints PASS_REGISTERED_RESEARCH_PACKAGE with outcome negative-result
• the commit check prints PASS_RESEARCH_COMMIT_BYTES for this head, with source history 7c49fe32c55de02c2c873655c804b16e4c3fef0a
• the baseline check prints PASS_RESEARCH_BASELINE_BINDINGS_ONLY and still reports selected κ 781451/250000000 and admitted BIT 17/5000

Checks raise SystemExit, so -O does not disable them. Controls: an in-memory signature physical(word, local, bit_saving) is detected, and a snippet that calls pricing.run before physical is rejected.

Not run: physical, the PR5679 caller replay, the pricing assembly, the outer ledger, native maps, compiler, tape, analytic recovery, make frontier6030-verify, Lean, and Docker. Unknown costs are not treated as zero. The baseline command is a source-binding orientation, not a scientific replay of this obstruction.

Credit

The caller and the selected verifier are DreamingOfClouds' PR #6030 chain, with the productive controller caller from the retained P104 lineage. The component C is Ali Romman's PR #5679, recorded in research/g20-helper-split. The assembly rejection of C inside the selected pricing is the earlier note on discussion #1166, not a result of this package. Dugongue, ai-nanachi, and the notices retained in those packages keep their credit.

Prepared by unpaidmoon with substantial Cursor Grok assistance. Apache-2.0.

Open next questions

1. Can a function that is not one of these 15 caller.py files, and is not pricing.run, accept C as a parameter named bit_saving while checking a Gaussian pair or idle Gaussian axis? First step: name that function from a file whose final component is not caller.py and whose path is not research/p104-helper470-twin-rung-removal/pricing.py, then execute it at C. Blocked by the absence of such a checked function. This census does not search other filenames, and it does not execute the ledger.

Workflow feedback (optional)

The selected verifier's variable word is the second argument of physical(word, local), so the call physical(caller, word) has to be read against the signature before naming the inputs. A parameter named word is not, by itself, the edited word.