Project Actions.

The per-recording Action Items feed has been there since v2.5. What v3.0 adds is the layer above it: the project-level and library-level aggregations.

Project Actions shows every open commitment, every decided decision, and a "mine" filter scoped to the entire project. If your project has sub-projects, the tree rolls up automatically. The Acme client engagement has six recordings spanning four sub-projects (kickoff, vendor selection, contract, cutover plan); Project Actions shows all of them in one view, sortable by deadline or owner.

My Action Items is the same engine, scoped differently: every action item assigned to you, across every recording in your library, regardless of which project it lives in. Open it Monday morning to see what's on your plate before you open the projects themselves.

Same engine, scoped to you across the whole library. Monday morning view: every action item assigned to your speaker identity, across every project, sorted by deadline by default. Filterable by project if you want to focus.

The deliberate choice here is that "mine" is bound to your speaker identity, not to a manual assignment. If a meeting recorded that you said "I'll handle the legal note", that becomes a "mine" item without you tagging it. If a meeting recorded that someone else said "You should look at the contract", the parser captures the recipient as you and routes it to your "mine" feed.

This is why the speaker library matters. Mine only works if your identity in the speaker library is stable across recordings — which the cross-recording Voice ID layer is what makes possible.