Repository navigation
$ oracle: ok_tool_use_tokens@fixture bills toolUsePromptTokenCount as input, 290 cents (rule 21, ledger x rate card; 1.5.5 billed 250) - #1023
Merged
Conversation
…fixture bills toolUsePromptTokenCount as input, 290 cents (rule 21: ledger x rate card; 1.5.5 billed 250) The mock reports promptTokenCount 11, toolUsePromptTokenCount 4, candidatesTokenCount 7, totalTokenCount 18. Under entry 576's ledger classes the ledger is 15 in / 7 out, and the oracle card (100000 / 200000 utok) prices that at 2,900,000 utok = 290 cents exactly. 1.5.5 ledgered 11 / 7 = 250 cents. The premise forgives the effects.usage / effects.metrics difference only while the candidate spends exactly 290 cents.
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
1 participant
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.
$DRAFT (rules 15 and 21). Stacked on #999, which is stacked on #926 (rule 19). It lands alone, after #999.Cell.
llm|gemini|gemini|request|ok_tool_use_tokens@fixture. Its 1.5.5 golden lands in #999 and was recorded from the published 1.5.5 by oracle-rerecord run 38549469444. The upstream answer reports:promptTokenCount11toolUsePromptTokenCount4candidatesTokenCount7totalTokenCount18Ledger x rate card. Entry 576 (owner 2026-10-02) sets the ledger classes: tool-use prompt tokens are billed input, and a total below the itemized sum (18 < 22) adds no line. So the ledger is 15 in / 7 out.
input_utok 100000andoutput_utok 200000on every lane (busbar-releaserecorder/config_emit.rs).1.5.5 ledgered 11 / 7 and spent 250 cents, dropping the 4 tool-use tokens. So 1.5.5 was wrong (rule 21).
Entry.
RULE21-576 ...:kindimprovement, using the CHANGELOG line entry 576 already ships.classeseffects.usageandeffects.metrics.expected_cells1./effects/usage/spend_cents== 290. The difference is forgiven only when 1.6.0 is right.The other eight new cells.
ok_cachepoint_document@fixtureandok_citation@fixture: 11 / 7 = 250 cents. That equals ledger x rate card, so 1.6.0 stays byte-identical and no entry is needed.stream_upstream_error@fixturex6: 1.5.5 bills nothing (usage{requests: 1}), consistent with the owner's mid-stream-failure ruling (M-2: a failed stream is not billed as a completion). No entry is needed. If the candidate bills these, that is a code defect, not a difference to register.