---
title: 'DuMate-DeepResearch: Auditable DR Framework'
url: https://www.emergentmind.com/topics/dumate-deepresearch
type: topic
---

# DuMate-DeepResearch: Auditable DR Framework

Searching arXiv for the cited DuMate-DeepResearch paper and closely related benchmark papers to ground the article.
DuMate-DeepResearch is a Deep Research (DR) framework introduced as “an auditable multi-agent system with recursive search and rubric-grounded reasoning” that is built on the Qianfan Agent Foundry and designed for complex, open-ended research tasks requiring iterative problem framing, evidence acquisition, verification, and long-form report synthesis [2606.07299]. It is characterized by an explicit separation between an Agent Core and an extensible Tool Ecosystem, a graph-based dynamic planning strategy that expands a research roadmap coarse-to-fine, a recursive two-level execution design centered on an inner Search Agent, and a rubric-based test-time optimization mechanism that generates task-specific quality criteria as live reasoning scaffolds [2606.07299]. In benchmark evaluation, it reports the best overall score of 58.03% on DeepResearch Bench and the best overall score of 61.95% on DeepResearch Bench II, ranking first in information recall and analysis on the latter benchmark [2606.07299].

## 1. Conceptual setting and problem formulation

DuMate-DeepResearch is situated within the broader DR paradigm, where systems are expected to address open-ended, underspecified research queries by clarifying intent, planning a research roadmap, iteratively acquiring and verifying evidence, and producing long-form reports with explicit structure and citations [2606.07299]. In this setting, the output is not a short factual answer but a report intended to cover multiple subtopics, integrate heterogeneous sources, and present analysis rather than retrieval alone [2606.07299].

The technical report identifies four limitations in current DR systems. The first is long-horizon planning over an underspecified scope: complex queries unfold into many interdependent sub-questions, while common ReAct-style approaches are described as myopic and unable to systematically re-plan when tools fail or evidence contradicts earlier assumptions [2606.07299]. The second is a single-agent decomposition and scheduling bottleneck, in which one agent is expected to perform both high-level planning and low-level noisy search, allowing local retrieval failures to derail the entire trajectory [2606.07299]. The third is hallucination risk in long-form synthesis, especially when systems must decide when evidence is sufficient and how to keep claims grounded during generation [2606.07299]. The fourth is limited process auditability, since many DR systems expose only final reports rather than intermediate plans, tool calls, evidence, and rationales [2606.07299].

This formulation places DuMate-DeepResearch in direct dialogue with benchmark-oriented work on deep research evaluation. DeepResearch Bench introduced a frozen “RetroSearch” environment for evaluating AI web research agents on multi-step tasks with stable web snapshots [2506.06287]. DeepResearch Bench II shifted evaluation toward long-form reports scored by 9,430 fine-grained binary rubrics across information recall, analysis, and presentation, and reported that even the strongest systems satisfy fewer than 50% of rubrics [2601.08536]. This suggests that strong DR performance requires both search competence and report-level evidence integration. A plausible implication is that DuMate-DeepResearch’s architectural emphasis on planning, recursive search isolation, and rubric-grounded reasoning is designed to target precisely those failure modes.

## 2. System architecture and auditable execution model

The framework is built on Qianfan Agent Foundry and separates the Agent Core from the Tool Ecosystem [2606.07299]. The Agent Core contains a Router for task understanding and analysis, a Planner for task thinking and planning, and an Execution Module for task scheduling and execution [2606.07299]. The Tool Ecosystem provides retrieval, evidence acquisition, and report rendering, and this separation is explicitly motivated by extensibility and auditability because every intermediate decision and tool invocation is traceable [2606.07299].

The Router takes a user query and produces a structured task specification. The Writer uses early coarse evidence to generate a fixed outline, and together the topic representation and outline form a fixed context
\[
z = (x, \mathcal{O})
\]
where \(x\) is the structured task representation and \(\mathcal{O}\) is the outline [2606.07299]. The global research session is modeled as a state-transition process with state
\[
s_t = \langle z,\; p_t,\; e_t,\; \rho_t \rangle
\]
where \(p_t\) is the current plan, \(e_t\) is the global evidence base, and \(\rho_t\) is the current guidance signal in the form of rubrics [2606.07299]. The Planner selects actions
\[
a_t = \mathcal{P}(s_t),
\]
the Execution Module collects new evidence
\[
\Delta e_t = \mathcal{X}(s_t, a_t),
\]
and the state updates through
\[
s_{t+1} = \mathcal{T}(s_t, a_t, \Delta e_t)
\]
before the final Writer synthesizes a report
\[
y = \mathcal{W}(x, \mathcal{O}, e_t, \rho^p)
\]
when the stopping condition holds [2606.07299].

This design makes the system auditable in a strong procedural sense. The Router logs structured task representations; the Planner logs plan graphs, decisions, reflection results, and re-planning; the Execution Module logs tool calls, parameters, timestamps, Search Agent invocations, and evidence; and the Writer logs how evidence and rubrics map into outline construction and report synthesis [2606.07299]. This suggests an explicit process trace rather than a purely prompt-internal latent trajectory.

## 3. Graph-based dynamic planning

The central planning object is a dynamic directed acyclic graph
\[
p_t = (V_t, E_t)
\]
where each node \(v \in V_t\) is a sub-task with depth \(d(v) \in \mathbb{Z}^+\) and execution status \(\chi(v) \in \{0,1\}\), and each edge \((u,v) \in E_t\) denotes that \(v\) depends on \(u\) [2606.07299]. The ready frontier is defined as
\[
\mathcal{F}_t = \{\, v \in V_t \;:\; \chi(v) = 0 \ \wedge\ \forall (u,v) \in E_t,\ \chi(u) = 1\,\},
\]
so only dependency-satisfied unexecuted nodes may be scheduled [2606.07299].

The planning strategy is coarse-to-fine. In an early coarse phase, the framework explores broad, high-level search tasks and uses the resulting evidence \(e_{t_c}\) to construct a fixed outline \(\mathcal{O}\) [2606.07299]. In later fine phases, the Planner expands the DAG with more specific sub-tasks for each outline section, introducing additional search, lightweight reasoning, and final synthesis nodes [2606.07299]. This coarse-to-fine organization operationalizes the idea that scope is initially vague and only becomes more concrete as evidence accumulates.

The plan is updated by a re-planning operator
\[
p_{t+1} = \Pi(p_t, e_{t+1}, \rho_{t+1}),
\]
which may expand the frontier, add finer subtasks, prune unproductive branches, or rewire dependencies in light of new evidence and rubric feedback [2606.07299]. Executed nodes are not reverted: once \(\chi(v)=1\), they remain executed [2606.07299]. Before execution, a reflection gate inspects proposed actions for relevance, redundancy, and consistency with rubric and task constraints, and actions may be revised for a bounded number of rounds [2606.07299].

This planning formulation differs from sequential search loops that lack an explicit global roadmap. Related work makes that contrast explicit. “Deep Researcher with Sequential Plan Reflection and Candidates Crossover” argues for sequential refinement with a centralized Global Research Context rather than parallel self-consistency, using reflection, progress estimation, and one-shot report generation [2601.20843]. “A Tale of Two Graphs” later formalizes a distinct but related dual-memory architecture separating an Outline Graph from a Knowledge Graph, and reports that separating what the agent knows from how it writes improves report depth, breadth, and factual grounding [2602.13830]. DuMate-DeepResearch instead keeps the graph formalism in the planner and uses the evidence base plus rubrics as live state, but the shared theme is that global structure is necessary for long-horizon DR.

## 4. Recursive two-level execution and Search Agent design

A defining mechanism of DuMate-DeepResearch is its recursive two-level execution architecture [2606.07299]. The outer Research Agent, denoted \(\mathcal{A}^{(0)}\), owns the global state \(s_t\), maintains the DAG \(p_t\), and decides which sub-task should be executed next [2606.07299]. When a node corresponds to an open-ended search sub-task rather than a direct tool call, execution is delegated to an inner Search Agent \(\mathcal{A}^{(1)}\) [2606.07299].

The inner Search Agent is itself a full Foundry Agent with its own Router, Planner, and Execution, but it is restricted to a local search problem and does not spawn additional agents [2606.07299]. Recursion depth is therefore exactly two: an outer Research Agent and inner Search Agents [2606.07299]. Formally, when the outer execution encounters a search node \(v\) with associated query \(q(v)\), it invokes
\[
\Delta e^{(v)} \leftarrow \mathcal{A}^{(1)}(q(v)),
\]
and merges the returned evidence into the outer evidence increment \(\Delta e_t\) [2606.07299].

This mechanism is intended to isolate noisy retrieval. The inner agent may perform multiple search rounds, query reformulations, and tool invocations for one sub-task, but the outer agent only receives aggregated evidence and local failure signals [2606.07299]. The technical report specifies that the inner Search Agent runs up to 10 retrieval rounds, with up to 3 sub-queries per round and 3 results per query [2606.07299]. The outer planning loop is allowed up to 15 iterations [2606.07299].

A plausible implication is that this separation reduces the coupling between retrieval noise and global scheduling decisions. That interpretation is consistent with domain-specific findings in other DR work. DEEPMED argues that blindly scaling tool calls in medicine can inject noisy context and trigger repetitive evidence-seeking, motivating both a difficulty-aware turn penalty during RL and an Over-Evidence Monitor during inference [2601.18496]. Although DuMate-DeepResearch is not specialized to medicine and does not use the same mechanisms, both systems treat uncontrolled search growth as destabilizing and seek architectural control over local exploration.

## 5. Rubric-grounded reasoning and test-time optimization

The third major mechanism is rubric-based test-time optimization [2606.07299]. A rubric is defined as a set
\[
\rho = \{c_1, \dots, c_k\}
\]
whose criteria are tuples
\[
c = \langle \text{name}, \text{description}, \text{guidance} \rangle,
\]
where the guidance field provides actionable instructions rather than scalar scores [2606.07299]. In DuMate-DeepResearch, rubrics are not only used for ex post evaluation; they are injected into planning, search, and writing as live reasoning scaffolds [2606.07299].

The framework distinguishes persistent and ephemeral rubrics. A persistent rubric is generated once from the topic and outline,
\[
\rho^p = \mathcal{G}_p(x, \mathcal{O}),
\]
and encodes long-horizon quality criteria for the report, such as cross-validation of vendor claims, quantitative comparison, or discussion of limitations and risks [2606.07299]. An ephemeral rubric is refreshed after each cycle from the outline and evidence,
\[
\rho^e_{t+1} = \mathcal{G}_e(\mathcal{O}, e_{t+1}),
\]
and captures current evidence gaps, inconsistencies, or sections requiring further support [2606.07299]. The active rubric state is
\[
\rho_t = (\rho^p, \rho^e_t).
\]

Planning and writing are explicitly conditioned on rubrics:
\[
a_t \sim \pi_{\mathcal{P}\bigl(\,\cdot \mid x, \mathcal{O}, p_t, e_t, \rho^p, \rho^e_t \bigr)
\]
for Planner actions, and
\[
y \sim \pi_{\mathcal{W}\bigl(\,\cdot \mid x, \mathcal{O}, e_t, \rho^p \bigr)
\]
for final report synthesis [2606.07299]. The ephemeral rubric also participates in stopping: if \(\rho^e_{t+1}\) indicates that there is “no outstanding gap,” the loop can terminate early [2606.07299].

This mechanism aligns with a broader trend toward rubric-driven DR evaluation and optimization. DeepResearch Bench II introduced 9,430 fine-grained binary rubrics derived from expert-written reports and used them to diagnose deficiencies in information recall, analysis, and presentation [2601.08536]. “Learning Query-Specific Rubrics from Human Preferences for DeepResearch Report Generation” proposed RL-trained rubric generators and a Multi-agent Markov-state workflow, showing that query-specific rubrics deliver more discriminative and human-aligned supervision than generic rubric strategies [2602.03619]. DuMate-DeepResearch differs in that its rubrics are generated and consumed at test time as guidance signals, rather than primarily as training rewards, but these lines of work converge on the view that fine-grained criteria are necessary for reliable DR behavior.

## 6. Tool ecosystem, evidence handling, and benchmark performance

The Tool Ecosystem includes Baidu Search integration and report rendering tools [2606.07299]. Search actions expose query expansion, search, URL crawling, page extraction, and evidence normalization, while report rendering proceeds through a pivot report that can then be converted to formats such as Markdown, HTML, or PPT [2606.07299]. Each tool output is standardized as an evidence record containing content snippet, URL, metadata when available, and a short summary [2606.07299]. The global evidence base \(e_t\) is monotone growing and is available to the Planner, Writer, and rubric generators [2606.07299].

The framework distinguishes tool-based and lightweight reasoning tasks in its graph. Tasks of type `llm` are restricted to operations such as deduplication, summarization, cross-consistency checks, or computations over existing evidence and are not permitted to generate final conclusions outside the report stage [2606.07299]. This design appears intended to preserve evidence-groundedness by reserving final synthesis for the Writer and by logging intermediate transformations.

The system is evaluated on two benchmarks. DeepResearch Bench consists of 100 tasks across 22 domains and uses Reference-based and Adaptive Criteria-driven Evaluation with dimensions of comprehensiveness, insight, instruction following, and readability [2606.07299]. DeepResearch Bench II contains 132 tasks across 22 domains and evaluates long-form reports by 9,430 fine-grained binary rubrics across information recall, analysis, and presentation [2601.08536]. On DeepResearch Bench, DuMate-DeepResearch reports 59.48 for comprehensiveness, 61.48 for insight, 53.87 for instruction following, 54.34 for readability, and 58.03% overall, which is reported as the best overall score [2606.07299]. On DeepResearch Bench II, it reports 57.58 for information recall, 71.70 for analysis, 89.89 for presentation, and 61.95% overall, also reported as the best overall score [2606.07299].

Ablations show that removing rubric guidance from the report stage reduces overall score from 58.03 to 57.61 on DeepResearch Bench, and removing rubric guidance from the entire pipeline reduces it further to 57.53 [2606.07299]. Replacing only the report-generation LLM while keeping planning and search fixed leads to larger drops, with DeepSeek V4 Pro at 57.21, GLM 5.1 at 56.69, Qwen-3.7 Max at 55.55, and MiniMax-M3 at 55.21 [2606.07299]. This suggests that while planning, recursive search, and rubric scaffolding matter, final synthesis quality remains sensitive to the report-stage model.

Benchmark context clarifies the significance of these results. DeepResearch Bench was introduced as a benchmark of 89 multi-step web research tasks with a frozen RetroSearch environment, and strong live-web ReAct agents achieved scores in the approximate range of 0.45–0.51, still below a rough human noise ceiling near 0.8 [2506.06287]. DeepResearch Bench II later showed that even frontier commercial DRSs satisfy fewer than 50% of fine-grained rubrics, with the best reported TotalScore at 45.40 for OpenAI-GPT-o3 Deep Research in the benchmark paper’s comparison table [2601.08536]. DuMate-DeepResearch’s reported 61.95% on DeepResearch Bench II therefore implies a substantial improvement under that rubric-centric evaluation regime. This suggests, though does not by itself prove, that auditability, recursive search isolation, and rubric-guided planning combine effectively under fine-grained report evaluation.

## 7. Relation to adjacent deep research architectures and limitations

DuMate-DeepResearch belongs to a rapidly evolving family of DR systems that differ in how they represent state, control search, and supervise report quality. Deep Researcher Reflect-Evolve emphasizes sequential research plan refinement, a centralized Global Research Context, Candidates Crossover, and one-shot report generation, reporting an overall score of 46.21 on DeepResearch Bench [2601.20843]. S1-DeepResearch instead focuses on trajectory construction and supervised training for a native deep research model, spanning long-horizon reasoning, instruction following, report generation, file understanding, and skill usage across 20 benchmarks [2606.15367]. DualGraph separates memory into an Outline Graph and Knowledge Graph and reports 53.08 RACE on DeepResearch Bench with GPT-5 [2602.13830]. NoveltyAgent specializes DR methods to paper novelty analysis by using point-wise novelty decomposition, citation-graph-grounded retrieval, and self-validation, outperforming GPT-5 DeepResearch by 10.15% on its checklist-based evaluation [2603.20884].

Against this background, DuMate-DeepResearch’s distinctive contribution is the combination of a graph-based planner, recursive two-level search execution, and test-time rubric scaffolding within an explicitly auditable Foundry architecture [2606.07299]. Unlike training-centric approaches such as query-specific rubric RL [2602.03619] or evidence-grounded RL against tool-call hacking [2510.10931], the technical report emphasizes inference-time system design rather than policy optimization. That leaves several plausible limitations.

The report notes computational cost, since 15 outer iterations with many inner Search Agents can be expensive, although parallel execution mitigates wall-clock latency [2606.07299]. It also implies sensitivity to tool quality because Baidu Search is the retrieval backbone, and weak or sparse domains may still lead the rubric system to premature “no gap” judgments [2606.07299]. The planning and exploration balance remains heuristic: overly aggressive stopping or over-expansion are both possible [2606.07299]. Finally, report quality is still strongly dependent on the report-stage LLM, as shown by the model replacement ablations [2606.07299].

Other recent work points to adjacent risks. Proof-of-Use argues that RL-trained DeepResearch agents can exhibit tool-call hacking, including mode collapse onto a single tool and spurious grounding, and proposes step-wise contracts, perturbation rewards, and answer-evidence alignment to enforce causal use of retrieved evidence [2510.10931]. This suggests a possible future extension of DuMate-DeepResearch: the auditable traces, explicit evidence records, and rubric-conditioned planning could in principle be paired with evidence-grounded RL or verification-style training. Similarly, DeepResearch-ReportEval emphasizes report-level quality, redundancy, and factuality, arguing that deep research systems are evaluated most naturally through their reports rather than isolated subskills [2510.07861]. DuMate-DeepResearch’s auditable report pipeline appears compatible with that perspective, although the technical report evaluates primarily on DeepResearch Bench and DeepResearch Bench II [2606.07299].

Overall, DuMate-DeepResearch can be characterized as an auditable, multi-agent DR framework whose core technical claim is that explicit graph-based planning, recursive delegation of noisy search subtasks, and rubric-conditioned reasoning materially improve long-form research performance on public DR benchmarks [2606.07299]. Its results situate it at the intersection of system architecture, benchmark-driven evaluation, and process transparency, rather than purely model-scale or training-scale advances.

Source: https://www.emergentmind.com/topics/dumate-deepresearch