Tell the model how to look at a result it has not seen before - #36
Merged
Merged
Conversation
There was a problem hiding this comment.
Sorry @CNSeniorious000, you've used your own review budget of 250,000 diff characters for the last 7 days.
You can request another review in 4 days and 17 hours by commenting @sourcery-ai review. Upgrade to get a review now.
This was referenced Aug 31, 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.
filter and aggregate in code and surface just the conclusionassumes the model knows which fields it wants. The first time through an unfamiliar tool it does not, and ending the cell on the whole value is then the rational move — you cannot project fields you have never seen. The block offers nothing cheaper, so that is what happens.Two lines instead of one, and the first costs a few hundred characters instead of the whole answer.
Measured — 4/4 tasks, 3 arms, all complete
Carried with #27, #30 and #35 as one arm.
gpt-5.6-terra, band 2K–20K, dump rate with median ratio in brackets.private_lending_33dhsa_medical_bill_liquidity_guard_30dbroadcast_exam_posture_breathing_32dfood_safety_dispute_33d4/4 tasks improved, against 2/4 for #27 + #30.
Why this clause specifically
The slice-bound histogram in #34. Under #27 + #30 the model stopped echoing raw results and started printing
[:12000]slices — median bound 12000, 22 of 23 above 2000 — which is howbroadcast_examwent from 9.1% to 38.2% andfood_safetyfrom 44.7% to 100%. With this clause in the arm, slice bounds collapse to a median of 300 on one task and 30 on another, nothing above 5000:macaron-v1-venti's regime (median 120, max 1200).Giving the model a cheap first look is what removes the reason to print the payload. Telling it not to print the payload, without that, just changes which statement does the printing.
Note
Attribution between this and #35 is not separated — measured together, and the arm does not carry #34.