Decisions
A decision record your team never has to write
Ask any AI meeting tool what you decided and it will find the meeting where you decided it. The problem is that the answer it finds is often wrong now.
The second sentence is the product
Decisions get revisited. A commitment made in June is quietly undone in July by a different group of people in a different meeting, and nobody goes back to correct the June notes. Six weeks later somebody builds a plan on a number that stopped being true.
Dot keeps the link. When it answers, it tells you what was decided, when, and by whom, and then whether anything since has changed it. If two meetings conflict and it cannot tell which is current, it says so and shows you both.
A worked example, not a feature list
Somebody asks: “Are we still going with Vendor A?”
You chose Vendor A on 12 August. After the security review, the 2 September ops sync moved to Vendor B. Priya owns the migration plan.
From Weekly Ops Sync · 2 September. The reversed decision is not deleted. Ask about August and it will tell you what was decided then, and what happened to it.
One record across Teams, Zoom and Meet
The decision log is not scoped to one platform’s recap. A pricing call on Teams and an ops sync on Zoom are the same conversation as far as the business is concerned. Native assistants treat them as strangers. Dot does not.
Questions
Is this a project-management decision log?
No. You do not file decisions by hand. They are taken from the meeting, with the date and the meeting they were said in, and they stay attached to the transcript. It is a record the minutes already implied, kept so a later meeting can find it.
What if Dot is not sure which decision is current?
It shows both, with dates. It will not pick a winner and read it as the only answer. An assistant that invents certainty about your commercial terms is worse than no assistant.