The conversation, next to the work.
What it will do.
Scoped to the client or project it belongs to, and visible to exactly the people who can already see that work.
A thread per client and project
Conversation filed where the work is, so a question about one brand is never in the same list as another.
Team and client in one place
Clients see the threads on their own work and nothing else, with the same scoping the rest of the app already enforces.
Mentions
Pull someone in by name and it reaches them through the notifications that already exist.
Why it is separate from review comments.
Two different jobs, and merging them makes both worse.
Comments point at a frame
They are pinned to a timestamp on a version, they get resolved, and they disappear when the cut ships. That is the right shape for a note about a frame and the wrong shape for a conversation.
Discussions carry the conversation
They outlive any one cut, they are never resolved, and they belong to the client rather than the file.
See how this fits the rest of the workflow on the features page.