Captured Work
Captured work is activity turned into usable progress. Connected apps, manual entries, finished initiatives, finished bugs, pull requests, comments, meetings, and agent activity can help explain what changed without making people rewrite every update by hand.
Completed tasks
Completed tasks are finished work shown in the Journal, Daily recap, standups, release notes, and Insights. A completed task can start from a todo, a finished initiative or bug, captured tool activity, agent work, or a manual Journal entry.
Do not use Todo as a synonym for completed work. A todo is unfinished personal work. A completed task is the finished result.
Connected activity
Connected activity gives the product evidence for completed work, planned work, blockers, and attribution. For example:
| Activity | How it can be used |
|---|---|
| Commits and pull requests | Explain shipped code and review work. |
| Synced issues | Add issue status, assignment, and execution context. |
| Calendar events | Explain meetings and planned focus time. |
| Comments and discussions | Preserve decisions and review notes near the work. |
| Agent sessions | Attribute agent-assisted work back to the initiative, bug, or todo. |
When the match is clear, captured activity can attach to an initiative, bug, todo, or completed task. If the match is wrong, open the item and adjust the linked work.
Where captured work appears
Captured work powers Recaps, Standups, Release Notes, and Insights.
In Daily recap, captured completed work appears in Worked on. Planned work and blockers appear in their own columns so the day stays readable.
Finished initiatives and bugs
Closing an initiative or bug updates the roadmap or bug record. When the recap still needs a clear completed item for that closure, Preferences can ask whether to create a completed task, create it automatically, or skip it.
If the initiative or bug already has visible linked work, the recap can use that existing evidence instead of creating another completed task.
Attribution
Attribution connects work to people, teams, taxonomy, coding tools, and agents. It makes recaps and Insights easier to read without turning the docs into a raw activity log.
For taxonomy setup, see Taxonomy. For agent attribution in reporting, see Agent Analytics.