Repository navigation
A question the developer hands back, told by the report and no longer called better or worse - #98
Merged
Merged
Conversation
… called better or worse Since the interview asks for the rules a user of the feature would see (#81), its developer hands some of its questions back as not theirs to decide (#94), and the harness counts them as `questions_handed_back` (#96). The report gave that measure a better way, fewer, like `corrections`. The developer decided on 2026-10-07 that this is no fault of the chain. A rule of the interview precise enough to decide without judgement was specific to the host of the evaluations, and a general one was vague or wrong elsewhere: the stop rule of the interview stays as it is, and so does the brief of `06-borrow-limit`, which plays a developer who delegates. Where such a question is not asked, the blueprint is to show the assumption to confirm (#60). So the measure stays in the report as a sign to follow, and loses its better way: a move of it is told as moved, like a move of `questions`. - `evals/surface_evals/report.py`: `questions_handed_back` leaves `DIRECTION`. - `evals/README.md`: the report tells it and never calls it better or worse, and why. - `tests/evals/test_report.py`: holds both. No session was played: nothing of the chain changes, and the measure is read as before.
This was referenced Oct 7, 2026
Closed
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.
Since the interview asks for the rules a user of the feature would see (#81), its developer hands some of its questions back as not theirs to decide (#94), and the harness counts them as
questions_handed_back(#96). The report gave that measure a better way, fewer, likecorrections.The developer decided on 2026-10-07, in #94, that this is no fault of the chain. A rule of the interview precise enough to decide without judgement was specific to the host of the evaluations, and a general one was vague or wrong elsewhere. So the stop rule of the interview stays as it is, and so does the brief of
06-borrow-limit, which plays a developer who delegates. Where such a question is not asked, the blueprint is to show the assumption to confirm (#60).What changes
The measure stays in the report as a sign to follow, and loses its better way: a move of it is told as moved, like a move of
questions.evals/surface_evals/report.py:questions_handed_backleavesDIRECTION.evals/README.md: the report tells it and never calls it better or worse, and why.tests/evals/test_report.py: holds both, and that a move either way is told as moved.Not measured
No session was played: nothing of the chain changes, and the measure is read from the runs as before.
Closes #94