root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-4221): complete Step 1 — document unified research execution model

Browse Source 
Fusion-Task-Id: FN-4221
Fusion-Task-Lineage: d710caa1-18b8-40d9-a70a-c5a4568484e3
This commit is contained in:
Fusion
2026-05-13 20:33:03 -07:00
committed by gsxdsm
parent 2401f7ab5b
commit 29e15613b2
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/research.md
View File

@@ -4,6 +4,16 @@
Fusion Research is a cited search-and-synthesis pipeline: create bounded research runs, gather sources with built-in web tools, and synthesize findings into actionable task context from the dashboard, CLI, or agent sessions.
## Execution model (FN-4221)
All Fusion surfaces use one execution model:
- Dashboard, CLI, pi extension, and engine agent tools **enqueue** runs through `ResearchStore.createRun(...)`.
- The engine is the **only** execution dispatcher. `ProjectEngine` owns a single shared `ResearchOrchestrator`, and `ResearchRunDispatcher` polls queued runs and calls `ResearchOrchestrator.startRun(...)`.
- Surfaces do not construct ad-hoc orchestrators.
If no engine is running, enqueue still succeeds but the run remains `queued` until an engine starts and the dispatcher picks it up. CLI `--wait` and pi-extension `wait_for_completion` poll persisted status and return a timeout/no-progress message that explicitly calls out this engine requirement.
---
> **Not pi-autoresearch:** Fusion Research is a cited search/synthesis pipeline. The autonomous try-measure-keep-revert loop from upstream `pi-autoresearch` is a separate domain (experiment sessions); see [naming-decision-2026-05.md](./research/naming-decision-2026-05.md).