Repository navigation
Cursor/pr6030 precision envelope mass 7270 - #6522
Open
unpaidmoon wants to merge 2 commits into
Open
unpaidmoon wants to merge 2 commits into
unpaidmoon wants to merge 2 commits into
Conversation
…nk mass. The published 2^(10^9+240152f) bound matches the expanded paid histogram and the raw budget, not the local mass 5952 or the recounted caller bound. This does not discharge precision_tape or change kappa. Co-authored-by: unpaidmoon <unpaidmoon@users.noreply.github.com>
The registered check text now matches the scalar, monomial, and rank-3 Gaussian used by the verifier. Co-authored-by: unpaidmoon <unpaidmoon@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change and mathematical scope
On the selected PR6030 invoice, the application review's coordinate envelope
2^(10^9+240152f)is2^(B+Rf)withR = 240152the complete paid rank mass andB = 10^9the recorded raw budget.This is a scoped identity for assumption ID
precision_tape. It is not a proof of that assumption, not a scalar saving, and not a change to selected κ781451/250000000.The recounted caller bound
126626680is strictly below the allowance184647552, which is strictly below10^9. The same majorant lemma with the caller bound in place of the budget would be smaller by exactly2^873373320. The review states the caller bound and still writes the budget exponent.Task and overlap
Base commit:
7c49fe32c55de02c2c873655c804b16e4c3fef0a. Priority revision 8. Selected record κ781451/250000000.Task card:
uniform-transfer-audit. Scope status: refined. The card asks for one assumption ID and one quantified implication at the actual caller. This binds the publishedprecision_tapeenvelope exponent. It does not treat #5625 row reentry or #5707 root-prefix lowering as a discharge of any of the five assumptions.Session r82, item 5 of the ordered eligible list. The 19 October handoff index is already delivered. Later structured handoffs are excluded when the post is DONE, a later merged result answers them, or the canonical artifact is an open PR, including the H25 requests on #6321, #6326, #6328, #6332, and #6335 and the 2 November review artifacts #6355, #6357, #6359, #6360, and #6361. Unexpired claims: none. Work already delivered by this account is excluded. Revision-8 "Next bounded decisions" then supplies six rows, and unnamed catalogue cards follow. Item 5 is the all-size row.
Nearest work:
research/p104-helper470-twin-rung-removal/RESULT.json: the complete paid histogram this note recounts. It does not state the envelope exponent.docs/research/pr-intake-evidence/pr6030-audit/PROOF-REVIEW.md: states the envelope and the caller bound. This note identifies which invoice quantities those words use.nonrecursive.local_paid_rank_mass = 5952is a different coefficient. Substituting it does not reproduce2^(10^9+240152f).research/p104-allwidth-native-certificate:native_all_columnsfor the older Raise conditional kappa to 0.00310045 with independent helper splits #5599 word. Different assumption and different selected head.A code search of
CrocSwap/integer-mult-boundsfinds the envelope sentence only in the PR6030 review and a vendored copy of that review. Discussion #1166 has no post of240152.Validation
CPython 3.12.3, standard library, Linux. From the repository root:
Both verifier modes printed
The package command printed
PASS_REGISTERED_RESEARCH_PACKAGEwith outcomecompleted. Checks raise exceptions, so-Odoes not disable them.The baseline command printed
PASS_RESEARCH_BASELINE_BINDINGS_ONLYwith selected κ781451/250000000. That is binding orientation only.The failure controls are in the verifier: a negative majorant exponent makes a singleton exceed the full product, and deleting one rank-1 paid call moves the mass off
240152.Not run:
make frontier6030-verify, Lean, Docker, and a source-bound count of non-Gaussian factors. The majorant hypotheses are not proved.Credit
The invoice is DreamingOfClouds' PR #6030. The envelope sentence is the PR6030 application review by Douglas Colkitt with OpenAI Codex assistance. Ali Romman, Mason Hale, Pierre-Loic Doulcet, Matarener, Chris R / Clear1nsight, and the retained native, compiler, and analytic lineage keep the credit in that review.
Prepared by unpaidmoon with substantial Cursor Grok assistance. Apache-2.0.
Open next questions
2^(rf), with every majorant at least 1? First step: one scalar ADD and one rank-r Gaussian, including a COPY into a nonzero residual. Blocked by the inheritedprecision_tapeandowned_erasurepremises.10^9in this sentence be replaced by126626680? That would shrink the envelope by2^873373320for everyf. First step: count non-Gaussian elementary factors in the admitted caller. Blocked because the pinned invoice does not contain that count.Workflow feedback (optional)
The revision-8 table still names the older #5599 exponent in its opening paragraph, while
certificates/selected-result.jsonselects PR6030 at781451/250000000. Reading the selected record before the priority prose avoided auditing the stale checkpoint. A link to discussion #1200 is enough.