Tasks and projects
Where work items come from, and how they resolve to projects.
Tasks in Suvi are not a board you fill in by hand. They are extracted from what is already happening.
Where tasks come from
One intake path handles every source: chat, mail, meeting transcripts and calendar invites. A commitment mentioned in a message becomes a task without you opening anything.
Extraction is followed by deduplication using embeddings plus a model tie-break, so the same commitment mentioned in a call and again in an email becomes one task rather than two.
Projects
Tasks resolve to projects automatically where a project is obvious from context. A project carries health and at-risk signals derived from its tasks: what is stalled, what is slipping, who is carrying the load.
Owners and admins get a manager digest summarising this. Members get their own work.
Auto-drafting
Some tasks Suvi can do itself. Those are drafted automatically and wait for your review rather than executing. A task Suvi cannot do sits as a task.
Attachments and history
Files sent in chat attach to the relevant task automatically. Every status change is recorded with who made it, so a project has a real activity history rather than a current state.
What to expect early
In the first fortnight, task extraction over-produces. It is easier to dismiss a task than to miss a commitment, so the intake errs that way. Dismissing is a signal and the rate settles.