Research Workspace: Two Agents, One Source of Truth
Run a research loop with two agents and shared notes so sources live in one place. Do not let two models invent conflicting citations.
By the flAim team
A research workspace is two agents and one notes doc for sources. The notes are the source of truth. The models are staff. If the notes and the answers disagree, the notes win until you verify.
The failure mode is specific: two fluent models invent two citation lists. You merge them in a hurry. A claim that never had a source ships.
Setup
- Create a workspace from the Research template, or add two agents and a Notes surface.
- Paste the question, audience, and “must cite / must not guess” rules into notes first.
- Agent A: gather claims and candidate sources into the notes, not only into chat.
- Agent B: attack the notes. Flag unsourced claims. Do not add new facts without a source line.
- You (or a teammate) confirm or delete. Only then draft.
The citation rule
| If you see | Do | Do not |
|---|---|---|
| Two URLs that disagree | Keep both in notes with a one-line conflict | Pick the more confident-sounding model |
| A claim with no source line | Delete it from the notes or mark UNVERIFIED | Let it into the outline “for now” |
| A model offering a DOI-looking string | Open it. If it 404s, it is not a source | Assume academic tone equals a real paper |
| Chat disagreement | Treat it as a signal. Score against the notes | Average the two answers into a third fiction |
Chat vs Build for research
Use Chat when you want to steer: @ agent A to gather, @ agent B to attack the notes (it already saw A), then send to both. Use Build when the chain is gather → critique → outline and you do not want to run that playbook by hand. Inspect the plan. The orchestrator is reasonable routing, not a librarian.
Shared notes how-to: Documentation. Next playbook in this series: writing studio.
Start from the Research Workspace template
Two research agents plus shared Notes for sources. Free credits, no API key.
Related: Shared context · Comparison method · Docs
We're building this in the open and we read everything. If you try it and something's clumsy, tell us. We'd rather hear it from you than not hear it.