Research and design deep-research execution adapters #45

New issue

Closed

opened 2026-07-27 01:07:23 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-27 01:07:23 +00:00

(Migrated from github.com)

Goal

Define deep research inside the Auto Research / ADARD control plane rather than in Quasar UI.

Required architecture

ADARD remains the research-run supervisor, branch DAG, ledger owner, evaluator, and promotion gate.
External deep-research systems execute as bounded adapters/workers.
Quasar may later display or invoke runs, but it does not own deep-research semantics or durable run state.
Browser JavaScript actors are an optional Auto Research worker runtime, not a Quasar-only research framework.

Research scope

Compare the official architecture and integration boundaries of:

LangChain Open Deep Research
GPT Researcher
STORM / Co-STORM
PaperQA2

Extract reusable capability routes, request/result contracts, provenance requirements, cancellation/resource limits, and evaluation fixtures.

Design deliverables

research node under roam/research/auto-research/
dependent design under roam/design/auto-research/
updated Auto Research project index
adapter registry and normalized request/event/result envelopes
fixed initial engine-routing policy
process/service isolation boundary
browser-worker adapter boundary
deterministic validation and evaluation contract

Constraints

no second control plane
no canonical Org writes by adapter workers
no engine-specific objects leaking into ADARD ledgers
no automatic promotion
no Quasar implementation in this issue
preserve the single active implementation slot

## Goal Define deep research inside the Auto Research / ADARD control plane rather than in Quasar UI. ## Required architecture - ADARD remains the research-run supervisor, branch DAG, ledger owner, evaluator, and promotion gate. - External deep-research systems execute as bounded adapters/workers. - Quasar may later display or invoke runs, but it does not own deep-research semantics or durable run state. - Browser JavaScript actors are an optional Auto Research worker runtime, not a Quasar-only research framework. ## Research scope Compare the official architecture and integration boundaries of: - LangChain Open Deep Research - GPT Researcher - STORM / Co-STORM - PaperQA2 Extract reusable capability routes, request/result contracts, provenance requirements, cancellation/resource limits, and evaluation fixtures. ## Design deliverables - research node under `roam/research/auto-research/` - dependent design under `roam/design/auto-research/` - updated Auto Research project index - adapter registry and normalized request/event/result envelopes - fixed initial engine-routing policy - process/service isolation boundary - browser-worker adapter boundary - deterministic validation and evaluation contract ## Constraints - no second control plane - no canonical Org writes by adapter workers - no engine-specific objects leaking into ADARD ledgers - no automatic promotion - no Quasar implementation in this issue - preserve the single active implementation slot