Repository navigation
feat: local model-mix what-if repricing (v0.10.0 draft) - #54
Merged
Merged
Conversation
Signed-off-by: Vijay <evijay@gmail.com>
Signed-off-by: Vijay <evijay@gmail.com>
Signed-off-by: Vijay <evijay@gmail.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.
Summary
Proposed for v0.10.0, independently of the next v0.9.0 row-coverage release.
Draft for review; no release or site changes are included.
fleetdiff what-ifcommand for dated model-mix re-pricing of covered LiteLLM records, with simple moves, scenarios, key/team scopes, workload mappings, price overrides, text and JSON.Measurement Contract
The study's estimator is the geometric mean of paired token ratios, with approximate 95% log-mean intervals. The cross-provider input pool is about 0.669, not a claim that token counts differ by less than 5%. The report labels these as measured factors and assumptions, not validated per-request or billing prediction ranges. The original failed range result stays recorded.
Current summaries do not carry per-model input/output/cache splits, so the summary path reports that concrete gap. Valid recorded usage from failed requests stays included; unsupported records and missing identities needed for scoped moves are excluded and counted. Default existing command output and identity bytes stay unchanged.
Verification
--network none.No version bump, dependency change, paid call, merge or tag. Please review this separately after the v0.9.0 release review.