A recap you can shape.
Edit the summary and keep your own notes alongside it. Make the record useful to the people doing the work.
Bring your meeting notes into focus. Review decisions
and carry the next steps into Co-Mo.
3 people. One shared direction.
The launch stays on Friday. The team aligned on what needs to happen first.
Keep the Friday launch. Maya reviews the brief on Thursday.
Alex finishes the launch deck by Wednesday.
Keep the brief, deck, and source files together.
Select a timestamp to see where it came from.
We’re keeping the launch on Friday. I’ll review the launch brief on Thursday so we can lock the final message.
I’ll finish the launch deck by Wednesday and share it here for review.
I’ll add the source files to the handoff on Thursday, before the launch.
Great. Let’s keep the brief, deck, and source files together. Everything is in one place for Friday.
Review the suggested actions. Try checking one off.
0 of 3 sample actions complete
One conversation. A clearer picture. Explore the notes, follow a source, or review the next steps.
A useful meeting leaves more than a wall of text. Keep the recap, the decisions, and the questions you still need to answer together.
“We’re keeping the launch on Friday. I’ll review the launch brief on Thursday so we can lock the final message.”
The launch stays on Friday, with Maya reviewing the brief on Thursday.
Edit the summary and keep your own notes alongside it. Make the record useful to the people doing the work.
Return to the original conversation when a decision needs context. Check the source before accepting a next step.
Keep questions, risks, and dependencies visible, so an open discussion never quietly becomes a settled decision.
The conversation is the beginning. Review the actions in Cardinal, then bring the accepted work into Co-Mo with its context intact.
Accept, edit, or reject a proposed action.
Keep the owner and due date with the task.
Bring the reviewed actions and original source into Co-Mo.
“I’ll review the launch brief on Thursday so we can lock the final message.”
Your review decides what moves forward.
The brief changed. A decision was made. A question stayed open. Keep that history close, so the next conversation has a better starting point.
Explore past meetings, revisit the source, and keep decisions connected to their follow-up work.
Explore the meeting libraryKeep the Friday launch. Review the brief on Thursday.
DecisionThe deck is ready. The audience statement still needs a final review.
Open questionThe direction, the work, and what’s still open.
Keep the decisions, dependencies, and responsibilities from your team’s conversation in one shared picture.
Explore team workflows“We can ship Friday if the design review is done by Thursday.”
Bring in a text transcript or meeting notes. Import .txt, .md, or .markdown files.
Confirm the wording, the owner, and the deadline. Review history keeps your choices visible.
Export meeting notes as Markdown. Keep a readable copy wherever your work goes next.
Cardinal is the meeting side of Modeus. It brings your conversation notes, source material, decisions, and next steps into one place, then connects reviewed actions to work in Co-Mo.
Explore sample meetings, import a text transcript or notes, edit the summary, and review proposed decisions and actions. You can accept or reject proposals, set owners and due dates, export Markdown, and turn accepted actions into Co-Mo tasks. The examples on this page are illustrative; the full preview lets you try the workflow yourself.
The current preview starts with sample meetings or text you provide. It does not record audio, join calls, generate AI transcripts, or connect to meeting platforms. You can import notes or a transcript as a .txt, .md, or .markdown file.
Review a proposed action and choose whether to accept it. In the preview, select an accepted action to create its Co-Mo project, including the owner, due date, and meeting source. You can return to the original context as the work develops.
Yes. You can edit the meeting summary and notes, inspect source evidence, change an action’s wording, owner, or due date, and accept or reject it. Review history keeps those choices visible.
The interactive workspace preview saves changes in this browser’s local storage. It does not sync with other people or devices, and no AI service receives the content. Export anything you want to keep before clearing browser data. The separate signed-in workspace stores account data on this website’s server, described in the privacy page.
Start with a meeting. Leave with a direction.
Try the interactive workspace preview. No account needed.