Repository navigation
docs(bench): record proof find against no-brief on the 10x graph - #286
Draft
tonyketcham wants to merge 1 commit into
Conversation
Haiku answered every question on the 10x graph twice with `proof find` and twice without it, one fresh session per question. On the 245 comparable questions: - `find` got 231.1 and 229.1 right per run, against 210.9 and 210.7. Over both runs, it alone was right 48 times and no-brief alone 12 times (sign test p < 0.0001). - It read 61% fewer tokens and made 9 tool calls instead of 21. - "Unknown" answers fell from 32 and 35 per run to 14 and 12. - The gain held on the questions the cards were not tuned on, and with the seven timed-out sessions set aside. - On the 24 questions that name no Effort, `find` got 46 of 48 and no-brief 31 of 48. Every pass mark in the plan is met. The README gives the tables and what the runs do not show. A measurement Finding records the result in `.flatbread-proof/`, derived from the 10x Finding. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DVVnhYL1Bz7mCfEKDoyLMW
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 of changes
This is layer 6 of a stack. It sits on #285, which sits on #284, #283, #282 and #281.
This PR adds no code. It records the first paid test of
proof find. Haiku answered every benchmark question on the 10x graph (4,980 records) twice with thefindtask text and twice with no-brief. Each question ran in its own fresh, headless session: 540 sessions per run. The cards were those from #284 (find_hashe5be6532…).Results on the 245 comparable questions (all but
world-077, whose count includes filler), pooled over both runs:findThe sign test gives p < 0.0001. Counting each question once,
finddid better on 37 and worse on 10.The plan's pass marks, measured on the plan's comparable set: the 245 less the 13 retraction questions, which leaves 232.
Checks on the result:
findgot 46 of 48 and no-brief 31 of 48.finddid better on 10 questions and worse on none.Files:
benchmarks/proof-recall/runs/x10-find-r{1,2}-{find,nobrief}.json: answers and costs.benchmarks/proof-recall/README.md: a new section with the tables above, and what the runs do not show. Thebriefarm was not rerun, only Haiku was tested, and the filler is easier to tell apart than real records. The look-alike-filler run tests that last point..flatbread-proof/findings/fnd-search-cards-raise-accuracy-and-cut-reading-on-t--ydqm2ybyqjedzw9y.md: a measurement Finding derived from the 10x Finding.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Does this introduce any non-backwards compatible changes?
Does this include any user config changes?
Generated by Claude Code