Session
Sessions are where you actually do the work. Each one represents one investigation — its briefing, its signals, its reports, its chat threads — while inheriting the workspace’s structure so its outputs stay comparable to its siblings.
What belongs to a session
Briefing, signals, reports, chat threads, and a per-session timeline of workflow runs. Anything structural — categories, metrics, report types, workflow definitions — comes from the workspace and is shared with every other session.
Many sessions, one workspace
A workspace typically holds many sessions over time. Use them to slice the same domain by quarter, by client, by topic, or by iteration. Collections let you stitch the strongest findings back together across sessions.
Running work on a session
From a session you trigger a workflow, manually or in auto mode. The pipeline reads the briefing and the workspace structure, then produces or updates the session’s signals and reports. See Workflow and Signal pipeline for details.