ResearchOne

Deep research dossier platform — A structured source-gathering, reasoning, and long-form research workflow that preserves the distinction between primary evidence and documented sources, built for rigorous scientific and investigative work.

Not a chatbot. Not a hallucination machine. A disciplined investigation engine with epistemic governance built in.

Model change, 13 Oct 2026 (Brandon). Double-check and the internal challenger (double_check, internal_challenger, every research kind) now use Kimi K2 Thinking (moonshotai/kimi-k2-thinking on OpenRouter, moonshotai/Kimi-K2-Thinking on Hugging Face) instead of Hermes 4 70B. Why: OpenRouter has no host for Hermes 4 70B (endpoints: [], checked 13 Oct 2026) and the Hugging Face account has no credit, so those steps had no usable route. Kimi K2 Thinking runs on OpenRouter first and falls back to the same model on Hugging Face; no other model is used in its place. Hermes 4 70B stays on the allowlist and can still be chosen for one run. Change in backend/src/config/researchEnsemblePresets.ts; record in docs/RJ-025-same-model-failover.md.

---

Deployment Topology

Mode B: Recommended — Vercel Frontend + Emma Backend (Split Deployment)

┌─────────────────────────────────────────────────────────────────┐
│                     RECOMMENDED TOPOLOGY                        │
│                                                                 │
│  Vercel (frontend)                                              │
│  └── React + Vite build (served via Vercel CDN)                 │
│      VITE_API_BASE_URL  → Emma runtime VM                       │
│      VITE_SOCKET_URL    → Emma runtime VM                       │
│      VITE_EXPORTS_BASE_URL → Emma runtime VM                    │
│                                                                 │
│  Emma runtime VM                                                │
│  ├── ResearchOne API (Express + Socket.IO)                      │
│  ├── BullMQ Workers (Ingestion, Embedding, Research, Atlas)     │
│  ├── Nginx (API + WebSocket + /exports reverse proxy)           │
│  └── /opt/researchone/exports/ (Atlas JSONL files)              │
│                                                                 │
│  Emma Postgres VM                                               │
│  └── PostgreSQL + pgvector (corpus, chunks, embeddings,         │
│       claims, contradictions, reports, discovery audit)         │
│                                                                 │
│  Emma Redis VM                                                  │
│  └── Redis (BullMQ job queues, job state, caching)              │
│                                                                 │
│  OpenRouter (remote inference — server-side only)               │
│  Tiered defaults (V1) in backend/src/config/index.ts (per-role  │
│  env overrides). Examples: Kimi K2 Thinking + DeepSeek-R1       │
│  (planning & core reasoning); Claude Sonnet 4.5 + Gemini 2.5    │
│  Pro (reports & sections); GPT-5-mini (structured JSON).        │
│                                                                 │
│  V2 ensemble (Research One 2) routes critical-path roles       │
│  through OpenRouter on verified multi-provider open-weights     │
│  reasoners: DeepSeek V3.2 (10+ providers), V3.1 (10+),          │
│  R1-0528 (5), Qwen3-235B Thinking (4), Kimi K2 Thinking (3).    │
│  Adversarial roles use Dolphin-Mistral-24B-Venice-Edition and   │
│  Sao10K L3.3-Euryale-70B. Single-provider Hermes / huihui-ai    │
│  HF slugs are allowlisted for user-opt-in only — see            │
│  docs/V2_MODEL_SELECTION_CRITERIA.md.                           │
└─────────────────────────────────────────────────────────────────┘

Mode A: Legacy — All-in-one on Emma runtime VM

All services including frontend on the same VM. Not recommended for new deployments. The frontend assumes same-origin /api and same-origin socket connection. To use this mode: do not set VITE_API_BASE_URL, VITE_SOCKET_URL, or VITE_EXPORTS_BASE_URL.

---

Research Philosophy

1. Dense centers are context, not final truth. Consensus clustering reflects repetition, not correctness.
2. Outliers are leads, not verdicts. Investigate, don't dismiss or blindly trust.
3. Bridges are high-value. Sparse connections between conceptual regions often indicate overlooked relationships.
4. Reason backward from anomalies. If an outlier were true, what structure would have to exist?
5. Preserve epistemic distinctions. Every claim tagged: established_fact | strong_evidence | testimony | inference | speculation
6. Contradiction is a first-class data type. Never suppressed.
7. Reports must attack themselves. Discovery → Double-check → Synthesizer → Verifier pipeline.
8. Atlas is an investigation map, not an oracle.

Research Pipeline (10 stages)

Stage	Role	Purpose
1	Planner	Decomposes query into sub-questions, retrieval targets, hypothesis, falsification criteria
2	Discovery	Autonomously identifies and ingests external sources when corpus is sparse
3	Retriever	Gathers sources from enriched corpus via hybrid vector+FTS search
4	Retriever Analysis	Evaluates source-corroboration tiers, flags outliers and bridges
5	Reasoner	Builds structured argument chains, tags all claims by source-corroboration tier
6	Double-check	Attacks conclusions, finds alternatives, prevents confirmation bias
7	Synthesizer	Writes the complete long-form research report
8	Verifier	Epistemic quality gate — ensures citation, contradiction, and tier standards are met
9	Report save	Stores report, sections, and verification metadata
10	Epistemic persistence	Extracts and persists claims, contradictions, and section citations

Post-publication Report Revision Workflow

Revision API endpoints:

This is the beginning of the README. Read the rest at the original. Read the full README ↗