Portal · Work
Work units and workstreams
Understand how Cortex groups captured sessions into work units and rolls related work into workstreams and outcomes.
- Work unitsRelated steps that pursue one piece of work
- WorkstreamsUnits grouped by initiative or outcome
- Evidence attachedContributors, models, cost, progress, and blockers
Work rolled up without losing evidence
Cortex organizes raw activity into a hierarchy that is easier to review. Move from evidence to outcomes without losing the sessions underneath.
From activity to workstreams
| Level | What it represents |
|---|---|
| Captured exchange | One request and response from a supported AI surface |
| Session | A continuous run of a tool or application |
| Work unit | Related steps that pursue one piece of work |
| Workstream | Work units that advance the same initiative or outcome |
Read the workstream view
- Status: Whether the stream is on track, at risk, or blocked.
- Contributors: People and agents carrying the work.
- Work-unit mix: The kinds of work inside the stream.
- Estimated cost: Captured model spend for the selected window.
- Progress and blockers: What advanced and what needs attention.
Open a work unit when you need the sessions, transcript, files, topics, actions, or plans behind the rollup.
Use the hierarchy carefully
- Compare workstreams inside the same date range and visibility scope.
- Use Activity when you need raw session evidence.
- Use Coverage before concluding that a thin workstream had little AI activity.
- Treat estimated spend as an operational signal, not an invoice.
Workstreams group captured evidence by the work it advances. They are not employee performance scores.
Continue from work
Was this helpful?