Repository navigation
Prove exponential invoice frontiers at fixed count and rank mass - #5901
Merged
Mister-Meeseeks merged 1 commit intoOct 27, 2026
Merged
Conversation
This was referenced Oct 27, 2026
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.
Summary
Prove an explicit exponential-size obstruction to increasing-concave invoice pruning, even with a common call count, paid rank mass, target and paid rank bound. Claim type: scoped mathematical proof with exact finite corroboration.
At m=11, all 462 middle-layer candidates survive concave-order pruning. Each has 22 paid calls, rank mass 264, paid ranks at most 23, and the same target H264. This exceeds PR #5778's 256-candidate cap with small integer ranks. The proof gives an explicit hinge tariff with exact gap one in each direction for every incomparable pair.
The explicit invoice family, proof application and verifier were produced by Nick Petalas. Credit Ali Romman #5778 for the frontier contract, zxv for complete signed invoice accounting, mightyOil and retained predecessors for moment-order context, and Dugongue for the distinction between concave and power order. Mean-preserving spreads, hinge tariffs and binomial identities are classical. No predecessor is audited or replayed, and no general literature priority is claimed.
Evidence
Before: the #5778 contract retains every incomparable pool member. Equal count and rank mass alone leave the possible surviving pool size unspecified.
After: the written proof gives the exact reverse-subset order for every m>=1. Local CPython 3.12.15 warning-strict normal and optimized checks pass 254 complete cube members, all 21,844 ordered cube pairs, 714 middle-layer members, all 138,117 unordered layer pairs, 276,234 direct counter-tariff evaluations, and 17 rejection controls. The two registered verifier commands took 1.058 and 1.122 seconds locally, below their 120-second limits. These are replay timings, not a performance improvement claim.
Exact reproduction from the repository root:
Direct replay prints
PASS_CONCAVE_INVOICE_ANTICHAINSand a generated receipt bound to all five package hashes. Registered normal/optimized replay and exact committed-byte/source-history checks pass at3ee3c8ebd2c1afe945fe906cbb9b77186bc070bf. Standard library only; no pending source commit is needed. Full provenance is pinned to canonical mainde5ec2e7a6074068452f45b1a191b5c72832df4a, priority revision 8.Live overlap covered 448 open PRs and 5,379 Discussion records with complete pagination, followed by fresh open-PR and handoff checks before commit. Distinctive all-main README and merged-PR searches supplement the sparse local-note search, whose 7,631 omitted note paths were explicitly reported. This coverage is not proof of novelty. Advance CLAIM.
Limitations and unrun obligations
These are synthetic complete signed accounting objects. Their common boundary is a declaration, not a physical construction. No supplier, native implementation, target independence, ownership/restoration, compiler admission or new kappa is claimed. The five framework assumptions remain. Selected cold replay, Lean, independent human review and formal proof-kernel review were not run.
The obstruction concerns replacement by supplied pool members under every increasing-concave tariff. It does not rule out useful typical-case pruning, approximate methods, extra representatives or stronger power-only comparisons. The fully spread cube member dominates all other cube members if it is added to the pool; the antichain assertion concerns the supplied middle layer. Hinge incomparability does not establish a power-curve crossing. The proof covers every m; the finite verifier enforces m<=11 and streams certificates.
Open next questions
Related open work
Related work was refreshed against this account's eight other open PRs created since the advance CLAIM: #5897, #5898, #5899, #5900, #5902, #5903, #5904 and #5905. They study other objects and do not compute this concave-invoice frontier or a conflicting same-instance value. No extra mathematical computations were run to check those contributions.
CI notes
At head
3ee3c8ebd2c1afe945fe906cbb9b77186bc070bf, run 40501075176 finished with plan failed; replay skipped. The only failed step is Onboarding helper tests.All ten failure/error entries are in unchanged
tests/test_research_current_assignment.py, endingFAILED (failures=8, errors=2, skipped=22). The two errors areKeyError: 'follow_up_steps'intest_cli_distinguishes_current_orientation_from_historical_controlandKeyError: 'catalog_first_step'intest_cli_preserves_legacy_output_and_emits_both_commands. The eight failed assertions concern the frozen-card count, missing-helper/reference rejection, and sparse current/historical command receipts, including four missing-historical-reference subtests.The ten failure/error headers, both KeyErrors and the final summary match the inspected PR #5897 plan log exactly. This confirms the reported shared onboarding failure on canonical main
de5ec2e7a6074068452f45b1a191b5c72832df4a. No shared test or implementation file was changed; maintainers will handle that repair.The package replay job was skipped. Hosted replay has not certified this package. Only the local mathematical and package checks listed above have run.
Merge Danger
Door: two-way. Blast radius: isolated. The diff adds one opt-in research package and changes no shared implementation, predecessor credit, frozen evidence or selected result.