Repository navigation
Explain recursive invoice comparisons with exact tariff witnesses - #5731
Merged
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.
An inconclusive signed-invoice comparison currently gives hinge values but no worked cost comparison. Add
explain_recursive_invoices.py: it emits explicit capped-linear tariffs with exact old/new paid-minus-target costs for each available sign. The existing comparator is unchanged.Use
python3 -B scripts/explain_recursive_invoices.py OLD.json NEW.json. The guide includes a mixed-hinge example whose power difference is(2^t-1)^2; this shows why opposite concave witnesses do not prove a power crossing.Validation: all 15 invoice/comparator tests pass on Python 3.12; the 5 new tests pass under
-O. The new suite independently replays every witness for 625 signed profiles, checks target debits and tests the real CLI under-I -Owith SHA256 input binding.git diff --checkpasses.The method is classical concave order, credited to the existing comparator, mightyOil’s T16 audit and retained predecessors. This is arithmetic on declared invoices, not circuit validation or a new κ. Fresh main/priorities and live overlap checks found no matching scope. The initial hosted plan failed the two existing current-status navigation checks. Their repair is now in main through PR #5703.
This PR was integrated before the test-discovery correction. The integrated head below is the verified source for this PR. The four CI-registration renames are available in PR #5749; its hosted log records all 69 new contribution tests as passing. The shared plan still has revision-8 task-picker failures, documented in the contribution handoff.
Base:
df0137efd35e11b4445734bf612bdd4c7ebc330c. Verified head:6e1640f84f83dfa68fbd1d8db6b10630708732fd.Prepared for aliromman with OpenAI Codex assistance. Existing tool and predecessor credits remain in place. No selected-frontier change.