Repository navigation
Screen recursive cost edits and certify centre-exchange headroom - #5397
Merged
Mister-Meeseeks merged 4 commits intoOct 24, 2026
Merged
Conversation
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.
Local scalar savings can worsen a recursive invoice, and owning helpers removes both paid jobs and productive output credit. Add an exact signed-invoice preflight that compares the complete paid and target histograms before native or compiler replay. It certifies better, equal or worse cost for every concave power tariff when the order is decisive, and reports inconclusive comparisons honestly. The method is classical concave order; the contribution is its reusable interface, explicit accounting contract and source-bound current application.
The current centre-paired helper exchange has a concrete ceiling. Even granting all 144 original exchanges
−H1−H8 paid / −H9 targets, its raw crossing is below 0.00302728824994. The 128-exchange bill in #5383/#5387/#5390 has less than 0.00000061348187 raw saving left through this exact lever. Reaching 0.0034 requires a different paid profile, target tradeoff or caller. This is a ceiling on the stated finite invoice family, not a barrier to all ownership or relation methods.An independent traversal also checks all 3,298 paid events in each source orientation. Under the exact eight backward relations it finds precisely the eight known zero jobs and eight known same-frame proportional snapshots. This corroborates the current investigation in Discussion #5125; it is not a discovery priority claim. The absence result is confined to the retained formal free-word grammar. New native identities, scalar combinations, relations and event graphs remain open.
The preflight distinguishes useful compiler work from recursive-budget gains: #5350's unfiltered H4→2H2 retiming is uniformly worse, while its filtered version preserves the invoice; #5390 usefully improves compiler parameters with the same invoice. The preflight does not dismiss those scalar/compiler contributions. Concurrent #5391 supplies the later trusted receipt/funding join; this earlier arithmetic screen does not duplicate it or fund a candidate from declarations.
Changes:
Validation:
-Oon CPython 3.12.8 and 3.14.5.Limits: histogram declarations do not establish circuit legality or catch omitted source charges; raw order does not establish supplier admission or a compiler endpoint. Full physical phase/tape/precision execution, the selected cold replay and inherited analytic foundations were not rerun. No selected record or research allocation changes.
Credit Cao Yifan (@intqwq), Ali Romman (@aliromman), @Dugongue, Chris R (@Clear1nsight), @ahrazzle, @mightyOil and the retained native/controller/compiler/analytic lineage. Prepared for @zxv with substantial OpenAI Codex GPT-6.1 Sol assistance, including explicitly authorized subagents. Apache-2.0.
Reproduce: