Stepwise preference
rlhf-stepwise.jsonOne step, scored, with the correction a researcher would make.
File metadata
- traj_id
- 39f66dce-80f2-49b1-9d52-3cea6b7ee976
- step_id
- 3
- category
- research
- task
- hidden-state-novelty-decoding-for-passk
- success
- null
- gt
- null
- score
- 2
history
10 results. Related work covers token-level entropy/min-p sampling, diverse beam search, and tree-of-thought branching. No prior work found that uses residual-stream novelty as the diversity signal.
Researcher answers (two of three overridden with free text rather than picking an offered option): - Mechanism: "intuitively, it makes sense to try a different trajectory each time a dominant idea has been arrived at? maybe when the model reaches a new thinking point" - Model & evals: "1.5B distilled, math" - Scope: "i just want to compare normal pass@k with this new method"
current_step
after_step_observation
Proposal 8062df13-330f-4616-bdd6-65f837ab9c51 created; awaiting researcher approval. Researcher returned it for revision with two inline plan comments: - on section 1: "can we actually first test if this is a reasonable way to detect idea boundaries? maybe if we can see a side by side of the tokens outputted and whether there is an idea happening right now." - on section 2: "lets do this after we derisk the first idea boundaries"
judge
The proposal builds a two-stage method in which stage 2 (novelty-steered forking) is entirely load-bearing on stage 1 (hidden-state change-points actually marking new ideas). Stage 1 is an unproven empirical claim about the model's internals, not a design choice. 1. Assumption stacking: the whole result is void if change-points do not correspond to ideas. That assumption is cheap to test in isolation and expensive to discover as a confound after a full Pass@k run. 2. No inspectable artifact: the plan produces Pass@k numbers, which cannot tell you whether the detector worked or whether the forking helped. There is no way to look at the mechanism. 3. Compute risk: an H100 run of the full method is spent before the premise is checked. The researcher's correction asks for exactly the missing thing — validate the detector first, and produce a token-by-token side-by-side so a human can see whether a detected boundary coincides with a real change of idea. {"Score":2}