Briefing
A briefing tells the pipeline what to look for. It is written by you in plain text or markdown and is the primary instrument for shaping what signals show up in a session.
What to put in a briefing
The subject of investigation, the time horizon, who the research is for, the scope (inclusions and exclusions), and any constraints — geographies, sectors, languages, source types. Be concrete: the more specific the briefing, the sharper the signals.
What it is not
The briefing is the prompt, not the corpus. Don’t paste articles or evidence into it — that’s what sources are for. Keep it tight enough that an agent can hold the whole thing in mind while it works.
Iterating on it
You can edit the briefing at any time. Subsequent workflow runs pick up the new version on the next task. Older signals remain; re-running source-and-verify or report-writing will incorporate the updated brief.