Fivo keeps two related things: tasks, which are concrete items of work, and commitments, which are promises recorded in the graph. The distinction matters because most promises never become a ticket, and the ones that do often lose their "why".
Tasks
After every meeting Fivo detects tasks and action items and assigns them to the speaker who took them when it can. Tasks appear in two places: inside the meeting report they came from, and on the Home screen, where you see your tasks across meetings.
Each task has a title, an owner, a status and, when one was mentioned, a due date. You can edit them, mark them done and share them to your task tools.
Sharing tasks to other tools
From a report you can share its tasks to Trello, Jira and other connected task tools. The task keeps a link to the card or issue it created. When the card moves in the external tool, the status syncs back to Fivo, and the graph records the change with the time it happened. You get one source of truth for status without typing it twice.
See Connect code and project tools for the tools that support this.
Commitments
A commitment is a promise the graph has recorded: who promised what, to whom, by when, and where they said it. Commitments come from every source: "I'll send the proposal Friday" on a call, "we'll have it by Q2" in an email, "I'll pick that up" in Slack.
Each commitment has:
- An owner: the person who promised.
- A counterpart: who it was promised to, when known.
- A due date, when one was mentioned.
- A status: open, fulfilled or no longer relevant.
- Its sources, with the exact context.
When a task is completed and it matches a commitment, the graph records that the task fulfilled it. That is how "did we deliver what we promised Acme?" gets a real answer.
Asking about commitments
In Fivo or from your AI assistant you can ask:
- What did I commit to this week?
- What is overdue?
- What did we promise Acme that has not been delivered?
- What did Laura promise on the kickoff call?
Commitments default to you, so "what do I owe?" needs no further detail. You can ask about any person or company you are allowed to see. See Track commitments after a call.
Commitments in the daily consultant
On paid plans Fivo scans the graph every day for dropped promises and decisions with no owner, no ticket and no next step, and reports them before anyone has to ask.
Dates and status
Everything in the graph is temporal. A commitment whose date moved keeps its history: the graph knows it was first due Friday and then pushed to Tuesday. A fulfilled commitment is not deleted; it is marked fulfilled with the task or event that closed it.
Status from external tools arrives with the time of the change at the origin, so a stale update never overwrites a newer one.
Permissions
You see commitments whose sources you can read. A promise made in a meeting you were not in and that was not shared with you does not appear in your lists, and the same applies to your assistant. See Permissions: what your Brain can see.
Limits
A task shared to Jira appears in the graph as two linked items, the Fivo task and the Jira issue, rather than one. Commitments without an explicit date have no due date; ask for "open" rather than "overdue" to see them.
- tasks
- commitments
- follow-up