# Hypothesis Tree Refinement (HTR) — methodology and evidence Background reference for the `arbor` skill. Source: *Toward Generalist Autonomous Research via Hypothesis-Tree Refinement* (Jin et al., 2026, [arXiv:2606.11926](https://arxiv.org/abs/2606.11926); [code](https://github.com/RUC-NLPIR/Arbor)). Reviewed against v1, the current paper version on 2026-09-30. Read this when you want the reasoning behind a design choice in the main loop. ## The problem: Autonomous Optimization (AO) AO is the operational core of autonomous research. An agent starts from an initial artifact and a research objective, then improves the artifact through experimental feedback **without step-level human supervision**. Formally a task is a tuple `P = (M_0, O, E_dev, E_test)`: - `M_0` — mutable initial material (usually a codebase + its data). - `O` — objective: what "better" means, as a metric direction over the artifact's output. - `E_dev` — development evaluator the agent may use freely during search. - `E_test` — held-out test evaluator. Same objective, different evidence. The goal is to return `M* = argmax over candidates of S_test(M')`, subject to the constraint that hypotheses and implementation decisions are made **without using `E_test` as an exploration oracle**. A candidate that exploits dev-split idiosyncrasies may raise `S_dev` but is not a successful AO solution unless the gain also transfers to `S_test`. Why this is hard: feedback is delayed, experiments are expensive, and failed attempts contain information that should guide later search. If an agent treats each trial as an independent local attempt, it loses the structure of the research process — what was tried, what evidence came back, how each result reshapes the space of future hypotheses. ## The three design requirements HTR is built to satisfy three requirements that ordinary agentic tool use does not: 1. **Branching with coherence.** Multiple competing hypotheses can be plausible at once, so exploration must branch — but unrestricted branching degenerates into an unstructured log. The frontier must keep competing directions organized, comparable, and actionable. 2. **Global strategy with local execution.** Strategic decisions depend on evidence across the whole run; implementing one hypothesis is short-horizon code editing. Separate the two so low-level traces don't obscure the global state, and outcomes stay attributable to the hypotheses that produced them. 3. **Exploration with held-out admission.** Dev feedback guides search; artifact-level progress is admitted only when it transfers beyond that feedback. The system must distinguish exploratory dev improvement from verified test improvement. ## The hypothesis tree as research state A rooted tree `T = (V, E)`. Each node is a research unit `n = `: - **Hypothesis `h_n`** — a verifiable/falsifiable claim about how changing the material improves the objective. Granularity tracks depth: nodes near the root are broad directions; deeper nodes are concrete interventions an executor can implement and evaluate. This organizes exploration as progressive refinement rather than a flat sequence of independent trials. - **Insight `iota_n`** — the reusable interpretation of evidence. For an executed leaf: what was tried, what happened, and *why* the result supports, weakens, or constrains the hypothesis. For an internal node: an abstraction over its children's insights — the current understanding of that direction. It is **not** an execution transcript; it is compact semantic memory for later ideation and selection. - **Metadata `mu_n`** — connects the semantic hypothesis to executable evidence: node status, dev score, factual result, implementation reference (git branch or commit), optional background. The material itself is **not** duplicated in the tree — only references to external artifact states produced in isolated worktrees. This keeps the state compact while every hypothesis stays grounded in a verifiable implementation. Internal nodes hold abstract directions and accumulated lessons; leaves hold candidate interventions to dispatch. After a leaf executes, its score, result, artifact ref, and insight are written back, and the insight is propagated upward along the path to the root. Through this abstraction, local outcomes become direction-level lessons and eventually a compact global understanding. The tree therefore plays three roles at once: a **search frontier** (which directions are active/validated/pruned), a **long-term memory** (reusable evidence from successes *and* failures), and an **auditable record** (each artifact change linked to the hypothesis and evidence that motivated it). ## The coordinator–executor split - A persistent **coordinator** owns the shared tree and decides where to expand, which evidence to trust, what to prune, and when to merge. It sees the whole frontier but does not perform every low-level implementation step. - Short-lived **executors** are invoked to test one hypothesis each. An executor gets `h_n`, relevant ancestor insights, and the current best artifact; it creates an isolated git worktree, implements the minimal change `h_n` requires, evaluates on `E_dev`, repairs its own broken/inactive code, and returns structured evidence. The boundary is the point: exploratory code changes stay isolated until they pass the merge gate, and the tree records only decision-relevant evidence (scores, factual outcomes, artifact refs, distilled insights) rather than a raw log of tool calls. This is how transient execution traces become persistent research state. ### Executors are hypothesis-bound (and why) An executor's local loop may involve many edits and reruns, but it stays bound to the assigned hypothesis: `h_n` is fixed. If an executor were allowed to change the hypothesis when the metric stalls, the returned score would no longer be evidence about the assigned node, and ancestor insights built from it would become impossible to interpret. Keeping executors hypothesis-bound preserves the semantic meaning of every tree update while still allowing local engineering flexibility. ## The six-step cycle (Algorithm 1, HTR) Each coordinator cycle is a controlled mutation of the tree through a narrow interface: 1. **Observe** — re-ground in a structured projection of the tree (frontier, root/global insights, ancestor insights, current best). Makes the tree the authoritative state after context compression, instead of relying on lossy conversation history. 2. **Ideate** — under a chosen parent, propose `k` child hypotheses, each a refinement/alternative/correction. Ideation is conditioned on tree evidence: validated insights are assumptions to build on, pruned nodes are negative constraints, recent reports suggest what's feasible or under-tested. 3. **Select** — choose pending nodes to execute. Balance expected utility against the evidence already accumulated around ancestors and siblings. A node may be selected because it has strong prior evidence, because its siblings exposed an unresolved ambiguity, or because its failure would clarify an important assumption. Selection is frontier control under partial, delayed feedback — not raw score maximization. 4. **Dispatch** — selected hypotheses go to independent executors in fresh worktrees. Parallel sibling execution yields comparative evidence within one direction, which feeds later pruning and abstraction. 5. **Backpropagate** — write each executor's evidence into its leaf, then update insights along the path to the root. The propagated signal is not just a scalar: it includes causal attributions, applicability conditions, and reusable lessons. A leaf-level data-interface mismatch can become a direction-level constraint and then a global prior. 6. **Decide** — continue expanding a direction, prune a falsified subtree, or attempt a merge. Promotion is guarded by the **held-out merge gate**: the candidate is evaluated on `E_test` in a fresh worktree and merged into `M_best` only if it improves under `O`. This separates exploratory success on `E_dev` from verified artifact-level progress. ## Empirical lessons (use these to prioritize effort) From the paper's experiments across six AO tasks (model training, harness engineering, data synthesis) plus MLE-Bench Lite: - **Insight feedback is the dominant component.** Ablating insight propagation while *keeping* the tree caused a larger drop than removing the tree entirely (on MLE-Bench Lite with Claude Opus 4.6: full 81.82% any-medal vs. 54.54% w/o insight feedback vs. 63.64% w/o tree). Hierarchy alone is not enough — a tree without propagated lessons organizes experiments syntactically but provides no semantic memory. **Invest your judgment in the abstraction at Backpropagate**, not just in generating more hypotheses. - **Structured search, not a bigger budget.** Arbor used a comparable token budget to single-trajectory baselines (~20–43M tokens) yet got larger held-out gains. The win is in how the budget is *organized*: maintaining competing hypotheses, isolated execution, comparison, and an updated frontier. - **The dev/test split exposes overfitting.** Across tasks, many nodes improved dev but only a subset passed the test gate. On Terminal-Bench, the highest-dev candidate was *not* the best on test. Always report the merged-vs-explored gap honestly; a high-dev/low-test result is evidence of feedback exploitation. - **Refinement deepens task understanding.** Early nodes test whether a broad mechanism holds; later nodes localize where it stops working; ancestor insights compress these into the constraints the final design must satisfy. Successful proposals are usually *evidence-conditioned* responses to earlier failures, not fresh guesses. - **Lessons transfer.** A harness optimized only on one task's dev feedback improved unrelated held-out tasks, indicating HTR discovers generally useful design changes rather than fitting the source benchmark — in the reported experiment. This does not establish that the gate is sufficient for generalization on arbitrary tasks. - **What HTR does *not* fix.** Arbor is strongest at a sequence of concrete refinements once a runnable solution exists. It is weaker when progress requires a genuinely new high-level formulation only weakly connected to the current tree — that still leans on good human task design (the choice of `M_0`, evaluator, metric, and interface). ## Interpretation boundary Repeated gate scores are selection feedback. Worktree isolation prevents file contamination but does not make an adaptively queried holdout independent. Reserve a separate final assessment, or disclose repeated-gate selection. The bundled helper implements bookkeeping, not upstream runtime enforcement; its strict score comparison is not a significance test.