Deep Research

Core Purpose

Deliver citation-tracked research reports through a structured pipeline with evidence persistence, source identity management, claim-level verification, and progressive context management.

Autonomy Principle: Operate independently. Infer assumptions from context. Only stop for critical errors or incomprehensible queries. Surface high-materiality assumptions explicitly in the Introduction and Methodology rather than silently defaulting.

Dependencies

• sgc-dev-blog owns the LovStudio website blog publishing contract.

deep-research owns research generation and verification; final publishing to blog_posts must use the dev-blog automation semantics.

Decision Tree

Request Analysis
+-- Simple lookup? --> STOP: Use WebSearch
+-- Debugging? --> STOP: Use standard tools
+-- Complex analysis needed? --> CONTINUE

Mode Selection
+-- Initial exploration --> quick (3 phases, 2-5 min)
+-- Standard research --> standard (6 phases, 5-10 min) [DEFAULT]
+-- Critical decision --> deep (8 phases, 10-20 min)
+-- Comprehensive review --> ultradeep (8+ phases, 20-45 min)

Default assumptions: Technical query = technical audience. Comparison = balanced perspective. Trend = recent 1-2 years.

Workflow Overview

Note: Phases 3-5 operate as an evidence loop per section (retrieve → evidence store → refine outline → draft → verify claims → delta-retrieve if needed), not as strict sequential gates.

Execution

On invocation, load relevant reference files:

1. Phase 1-7: Load [methodology.md](./reference/methodology.md) for detailed phase instructions
2. Phase 8 (Report): Load [report-assembly.md](./reference/report-assembly.md) for progressive generation
3. HTML/PDF output: Load [html-generation.md](./reference/html-generation.md)
4. Quality checks: Load [quality-gates.md](./reference/quality-gates.md)
5. Long reports (>18K words): Load [continuation.md](./reference/continuation.md)

Templates:

• Report structure: [reporttemplate.md](./templates/reporttemplate.md)
• HTML styling: [mckinseyreporttemplate.html](./templates/mckinseyreporttemplate.html)

Scripts:

• python scripts/validate_report.py --report [path]
• python scripts/verify_citations.py --report [path]
• python scripts/mdtohtml.py [markdown_path]

Post-report publishing (LovStudio):

• This is a mandatory completion gate, not an optional follow-up. Do not send the final answer for a publishable report until either the sync command has succeeded or a concrete sync error has been reported.
• After Phase 8 successfully generates the Markdown report, automatically publish it to the LovStudio blog system unless the user explicitly says "private", "do not publish", "不要发布", or equivalent.
• This gate depends on sgc-dev-blog. The website sync command below is

the dev-blog publishing contract for research-origin artifacts.

• Use the generated Markdown file path as the source of truth:

cd /Users/mark/lovstudio/coding/web && pnpm run sync:research -- [markdown_path]

• If multiple Markdown reports were generated or the exact Markdown path is uncertain, run:

cd /Users/mark/lovstudio/coding/web && pnpm run sync:research -- --limit 5

• Publishing semantics are owned by sgc-dev-blog and executed by the

website sync script: - New reports are public detail pages (isvisible=true). - New reports appear in the /blog index by default (showin_index=true). - Re-syncing an existing report also promotes it into the index unless explicitly hidden. - Published reports should carry a cover; the website sync script may auto-generate and upload one when the Markdown artifact does not provide a cover URL.

• Tell the user the final public URL in the form:

https://lovstudio.ai/blog/[slug]

• In the final answer, include a one-line publishing status: Published to LovStudio: yes/no, plus the public URL when yes.
• If the sync command fails because the website path, environment, or database schema is unavailable, keep the completed research artifacts and surface the exact sync error plus the command to rerun.

Output Contract

Required sections:

• Executive Summary (200-400 words)
• Introduction (scope, methodology, assumptions)
• Main Analysis (4-8 findings, 600-2,000 words each, cited)
• Synthesis & Insights (patterns, implications)
• Limitations & Caveats
• Recommendations
• Bibliography (COMPLETE - every citation, no placeholders)
• Methodology Appendix

Output files (all to ~/Documents/[Topic]Research[YYYYMMDD]/):

• Markdown (primary source of truth)
• sources.jsonl — stable source registry with canonical IDs
• evidence.jsonl — append-only evidence store with quotes and locators
• claims.jsonl — atomic claim ledger with support status
• run_manifest.json — query, mode, assumptions, provider config
• HTML (McKinsey style, auto-opened)
• PDF (professional print, auto-opened)

Quality standards:

• 10+ sources, 3+ per major claim (cluster-independent, not just count)
• All factual claims cited immediately [N] with evidence backing in evidence.jsonl
• Claim-support verification mandatory: no unsupported factual claims pass delivery
• No placeholders, no fabricated citations
• Prose-first (>=80%), bullets sparingly

When to Use / NOT Use

Use: Comprehensive analysis, technology comparisons, state-of-the-art reviews, multi-perspective investigation, market analysis.

Do NOT use: Simple lookups, debugging, 1-2 search answers, quick time-sensitive queries.