SYNTHESIS NOTE
Topics›this note

Can trajectory structure replace hand-annotated process rewards?

Recent methods extract step-level supervision directly from how agent trajectories are structured—trees, expert alignments, tool calls—rather than training separate reward models. Can this structural approach consistently avoid annotation costs?

Synthesis note · 2026-05-18

A pattern recurring across three 2026 methods that solve the same problem from different angles. Each finds a way to convert sparse trajectory-level outcome rewards into dense step-level supervision without requiring a separately-trained process reward model and without requiring step-level human annotations. Each does it by exploiting a structural feature of the trajectory or the training setup itself.

The first, Tree-GRPO: Can tree structure alone convert outcome rewards into process supervision?. The structural feature is tree topology. Rollouts branch at decision points. When outcome rewards arrive at the leaves, they back-propagate up the tree. At each branching point, sibling-subtree differences yield a preference-learning signal — sibling A did better than sibling B, so the action that led to A gets reinforced over B's. Does tree depth automatically produce supervision at multiple granularities?: the depth at which divergence occurs determines the granularity of the resulting signal, and random expansion naturally produces multi-granularity supervision in a single training run.

The second, Supervised RL (SRL): Can step-wise expert rewards help small models learn hard reasoning?. The structural feature is step-level alignment with expert demonstrations. The model is trained to produce reasoning actions, and reward comes from similarity between its actions and expert actions extracted from an SFT dataset — computed step-wise. This provides dense smooth supervision even when every rollout produces a wrong final answer (the regime where outcome-only RL fails entirely).

The third, ToolPO: Can simulated APIs and token-level credit assignment train better tool-using agents?. The structural feature is tool-call position. Rather than backpropagating outcome rewards uniformly across the trajectory, ToolPO attributes advantage specifically to the tokens that constitute tool invocations. A correct tool call in an ultimately successful trajectory gets positive credit; an incorrect tool call still gets penalized even when the trajectory succeeds despite it.

These are three implementations of one design principle: structural features of the trajectory can substitute for separately-trained or hand-annotated process supervision.

The principle matters because process supervision has been the expensive part of agent RL. Process reward models (PRMs) require step-level annotated training data — costly to collect and brittle to construct. Annotation-heavy alternatives have the same problem. The methods catalogued here demonstrate that for at least three trajectory structures (tree topology, expert-aligned action sequences, tool-call positions), the supervision signal is already present in the structure — it just needs to be read out correctly.

The principle generalizes beyond the three methods. Wherever a trajectory has identifiable structural features that correlate with intermediate decision quality, those features can serve as supervision. Action segmentation, attention pattern variance, retrieval call patterns, plan-execution branching — all are candidates. The design space has barely been explored.

Two related earlier notes complete the cluster. Does supervising retrieval steps outperform final answer rewards? establishes empirically that process supervision wins over outcome-only RL for agentic systems — the motivating result that makes this synthesis matter. Why do standard process reward models fail on thinking traces? shows that traditional PRMs degrade when trajectory structure becomes non-linear — exactly the regime where structural-feature methods like Tree-GRPO win.

The methodological lesson: when annotation is the bottleneck, look for structural substitutes. Trajectory geometry is information; it costs nothing to extract.

Inquiring lines that read this note 84

This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.

Should reward models emphasize process understanding or only final outcomes? How do different post-training structures affect learning outcomes? Why does separating planning from execution enhance reasoning performance? How can reward models fail to detect reward-seeking disguised as alignment? Can AI systems autonomously pursue unstated objectives or circumvent design constraints? Should agent evaluation measure execution quality beyond task success? How can agents learn and retain useful knowledge across diverse environments? Can AI agents learn to improve performance from experience? When should retrieval be triggered to augment language model reasoning? What prevents or enables error accumulation in self-training systems? How should conversational agents balance proactive goal-pursuit with user autonomy? How do credentials maintain predictive value when their context changes? Do reasoning traces accurately represent what models actually compute? What determines whether visible reasoning traces improve task performance? Can real-time alliance measurement enable more effective therapy interventions? How should test-time compute be allocated adaptively across task difficulties? How do different reward signals affect model reasoning and calibration differently? Does architectural recurrence enable computational capabilities that fixed-depth models cannot achieve? Is model misalignment inherent to base models or induced by alignment procedures? Does chain-of-thought reasoning faithfully reflect actual model reasoning processes? How do workflow position and structure enable attacks in multi-agent systems? Can individually safe agents collectively violate system-level constraints? How can model evaluations remain robust against gaming and evaluator drift? Which agent-created code should persist in infrastructure versus remain task-specific? Can post-hoc execution traces provide sufficient accountability without real-time oversight? Can oversight systems work against strategically aware agents?

Related concepts in this collection 9

This note in its neighbourhood — explore the map, then jump to a related concept in the list below.

Concept map
19 direct connections · 147 in 2-hop network ·medium cluster Open in graph ↗

Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph

your link semantically near linked from elsewhere

Related papers in this collection 8

Papers most semantically related to this note, ranked by cosine similarity in the embedding space.

Original note title

process supervision can be derived from structural features of agent trajectories — sidestepping the annotation cost of process reward models