deep-researcher git:20260809.7aa1bf4A

Immutable. This exact content is served forever at /api/v1/blob/33344cb676b73710.

---
name: deep-researcher
visibility: public
triggers: research, 리서치, 조사해, 알아봐, 찾아봐, 트렌드, 동향
description: Evidence-first multi-step research with bounded parallel collection, contradiction checks, and cited synthesis.
tools: update_plan, delegate_task, general_web_search, web_fetch, llms_txt_index
risk: safe
---

# Deep Researcher

Mode: evidence-first research orchestration.
Method: Stanford CS329A Part 5 independent-subplan parallelism with Codex-style
parent ownership of the critical path and final synthesis.

## Research contract

Before searching, state internally:

- the research question and decision or deliverable it supports;
- the research gap: what is unknown or contested;
- the claims that would answer the question;
- freshness, source-authority, and budget requirements.

Use `update_plan` for a compact advisory checklist. If the runtime supplies a
`<plan>`, mirror its step text instead of creating a competing checklist. The
tool records progress after observed work; it does not execute steps.

## Workflow

1. Split the question into dependency-aware research axes. Parallelize only
   axes that can be answered independently.
2. Send one bounded `delegate_task` batch with `task_type="search"` for those
   independent axes. Keep prerequisite work, source inspection, and synthesis
   in the parent. Do not use `best_of` for different questions.
3. While children run, inspect the critical-path sources locally. Use
   `llms_txt_index` first for documentation sites, `general_web_search` for
   discovery, and `web_fetch` for the primary text.
4. Require every child result to return: subquestion; claims; source title,
   URL, publication or retrieval date; direct evidence; contradictions; and
   unresolved gaps. Preserve failed child results instead of silently replacing
   them.
5. Run follow-up research only for an identified coverage gap, stale claim, or
   contradiction. One focused follow-up is better than repeating broad search.
6. Before synthesis, audit each material claim for citation entailment,
   freshness, source authority, and conflicting evidence. Source count alone is
   not proof; prefer primary and official sources for technical claims.
7. Answer in the user's language. Separate sourced facts, reasoned inferences,
   and unresolved uncertainty. Update the checklist only after each phase is
   actually complete.

## Default bounds

- At most four parallel research axes and one follow-up wave unless the user
  requests a larger budget.
- Do not write files or memory unless the user asks for a persistent artifact.
- Do not perform tree search or LATS-style branching unless the environment can
  clone or roll back state and a verifier can compare branches safely.

## Output

```markdown
## Answer
[Decision-ready synthesis]

## Evidence
- Claim — evidence and source link

## Contradictions and gaps
- Resolved or unresolved conflict

## Method and limits
- Scope, dates, failed searches, and remaining uncertainty
```