HerrHruby/mr-rollout-viewer
MR / E / FA Rollout Viewer
A static viewer for meta-reasoning RL rollouts: the planner (MR) layers, the frontier each layer was working from, the directions it proposed, the judge's per-direction verdict, the explorer (E) execution of each direction, the final answer (FA), and the task judge.
Two runs, switchable from the top bar:
Run B never called the per-direction progress judge, so direction verdicts, categories, the direction bonus and the frontier text do not exist for any of its rollouts. The viewer hides that UI rather than showing it empty.
Reading a rollout
Disclosure runs three levels deep, so an eight-layer rollout is navigable:
- L1 — layer. Closed by default. The header carries the layer number, the direction count, how many were actually executed, a per-direction ✓/✗ strip and a "5 of 6 progressing" tally, so you can pick the interesting layer without opening anything.
- L2 — frontier | directions. Both open when you open the layer, and each collapses independently. Direction verdicts, categories and reasons stay inline next to the direction they judge.
- L3 — chain-of-thought. Closed. One fold for the planner's deliberation (the
<think>block), one per direction for the explorer's full response.
Expand all / Collapse all are scoped to the current rollout (keys e / c; j / k step between rollouts).
The five-exploration cap
At step 89 the planner routinely proposes more directions than the explorer budget allows. Explorations are hard-capped at five per layer, but layers now emit six, seven, even eight directions. Across the dump, 462 of 14,925 directions (3.1%) in 169 of 536 branches were emitted and judged but never executed. This did not happen at all in the step 56 dump.
Those directions are marked not executed, their layer header shows 6 directions → 5 executed plus an N unexplored badge, and the layer carries a notice explaining the cap. It matters for interpretation: the direction judge scores the proposal text, so an unexecuted direction can still be scored as progressing.
Buffer provenance
The dumps carry no buffer field, but provenance is exactly recoverable from trace[0].layer: the number of layers already completed before the branch was sampled. First layer 0 means a fresh rollout; first layer N means an N-layer prefix that is not in the dump. Measured over the full dumps:
Every rollout says plainly whether it is fresh or warm-started, a marker sits above the first shown layer when earlier layers are missing, and the prefix layers are called out inside the frontier that summarises them. The claim is independently corroborated: the first frontier of a branch starting at layer N lists exactly N earlier layers, checked on all run-A rows that carry judging, with zero mismatches.
Sampling
25 rollouts per run.
Run A is stratified jointly on termination and buffer prefix, with largest-remainder proportional allocation over the joint cells, so both marginals track the dump. Layer count is not a tiebreak.
The prefix marginal tracks the dump to within one draw. The termination marginal under-weights completed by about 14 points, and that is deliberate: the dump now has five termination types, and guaranteeing at least two rollouts of each (one, for the types with only one branch in the whole dump) costs eight of the 25 draws against the 5.5 that proportionality alone would spend.
Run B is unchanged and still carries the older termination-only sample, which leans fresh. Its sidebar says so and shows sampled against full.
Truncation
Kept in full: the problem, every planner layer, the frontier, every direction and its judge verdict including the full reason prose, the final answer, and all scalars. Truncated: explorer responses at 6,000 characters, reference solution at 4,000, judge verdict at 4,000, rubric at 3,000. Planner and explorer prompts were dropped — they are fixed boilerplate. The frontier is cumulative (each layer's text extends the previous one verbatim), so it is stored as a per-layer delta and reassembled in the browser, at 27% of its raw size.