Inspect captured work
Follow grouped work to captured sessions and source references, and interpret provenance, ownership, and estimated cost rollups.
Find related work
- Open Work and narrow the person, time or stream to the task. Confirm scope, time window and freshness.
- Choose a work unit, then follow its sessions or source references and check attribution.
- Read the summary as an interpretation. Check estimated hours, ticket-status provenance and pricing coverage separately before verifying a specific result.
Read the workstream view
Use Open exact activity to inspect retained tool input/results and follow available references. A file link alone does not prove completion.
| What you see | Provenance and limits |
|---|---|
| Source text, time, model and references | Captured evidence. Follow the reference for context when available; samples are selective. |
| Counts, usage and estimated cost | Calculated over a population, time window and visibility. Cost needs available usage and pricing. |
| Work-unit titles, summaries and groupings | Inferred meaning, not a captured overall goal or observed successful result. Missing source data limits the summary. |
| Contributors and sources | People and tools represented in the evidence. |
| Linked ticket status | That source's status, not verification of every claim. |
| Estimated human hours | An estimate, not measured labor or time saved. |
Session titles may be inferred or drawn from captured source text. An early instruction is not automatically the session goal. Session duration is elapsed captured time, not active human labor. Conversation claims and work groupings do not establish completed outcomes, acceptance or deployment.
From activity to related work
| Record | Meaning |
|---|---|
| Captured exchange | Permitted request, response and metadata from a supported source. |
| Session | Activity under one session identity; it can include several conversations. |
| Work unit | Related captured activity grouped under a work identity. |
| Workstream | A grouping of related work units. |
Counts at these levels differ. New sessions may appear before grouping; unassigned activity is not missing capture.
Read a work-unit rollup
In this example, $0.42 plus $0.18 gives $0.60 available cost. The unpriced session is unknown, not free.
| Pricing coverage | Meaning |
|---|---|
| Complete | Included activity is priced; capture coverage can still be incomplete. |
| Partial | Some activity lacks pricing; the amount is the available portion. |
| No cost estimate | Usage or pricing is missing; do not substitute zero. |
| Unknown | An amount may exist without established pricing coverage. |
See AI spend for invoice and estimation boundaries. Do not add overlapping groupings as distinct activity.
Scope, time windows, and freshness
Compare organization, people, visibility, dates and pricing coverage. List filters and detail rollups can cover different periods. A workstream preview is a bounded selection, not the full population; use totals/pagination rather than counting visible cards.
A newly loaded page can contain earlier processed activity; delays do not mean nothing was captured. Distinguish missing fields from confirmed empty lists. Check coverage for sparse activity, user profiles for sessions, and Search for connected source evidence.
People, teams, and ownership
Participants contributed activity; a suggested owner is not confirmed ownership or team assignment. Grouping and membership do not grant access. Evidence, aggregates and external records remain subject to visibility and source permissions. Workstreams are not employee performance scores.