Cardinal

Stay in the conversation.

Bring your meeting notes into focus. Review decisions
and carry the next steps into Co-Mo.

CardinalSample meeting

Product launch sync

3 people. One shared direction.

The decisions. The owners. What comes next.

Ready for Friday.

The launch stays on Friday. The team aligned on what needs to happen first.

A clear decision

Keep the Friday launch. Maya reviews the brief on Thursday.

Everyone knows their part

Alex finishes the launch deck by Wednesday.

One complete handoff

Keep the brief, deck, and source files together.

Select a timestamp to see where it came from.

One conversation. A clearer picture. Explore the notes, follow a source, or review the next steps.

The meeting ends.
The important parts stay.

A useful meeting leaves more than a wall of text. Keep the recap, the decisions, and the questions you still need to answer together.

Product launch syncExample
Maya 00:24
“We’re keeping the launch on Friday. I’ll review the launch brief on Thursday so we can lock the final message.”
Decision to review

Keep the Friday launch.

The launch stays on Friday, with Maya reviewing the brief on Thursday.

Original context included 00:24

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.

The why, beside the what.

Return to the original conversation when a decision needs context. Check the source before accepting a next step.

Room for the unresolved.

Keep questions, risks, and dependencies visible, so an open discussion never quietly becomes a settled decision.

A next step.
With somewhere to go.

The conversation is the beginning. Review the actions in Cardinal, then bring the accepted work into Co-Mo with its context intact.

  1. 01

    Decide what moves forward.

    Accept, edit, or reject a proposed action.

  2. 02

    Make the responsibility clear.

    Keep the owner and due date with the task.

  3. 03

    Carry the conversation with it.

    Bring the reviewed actions and original source into Co-Mo.

Try the meeting-to-work flow
Cardinal Co-MoInteractive example
  1. 1Review
  2. 2Accept
  3. 3Create work
Maya
“I’ll review the launch brief on Thursday so we can lock the final message.”
Proposed actionNeeds your review

Review the launch brief

Owner
Maya
Due
Thursday
Source
Product launch sync

Your review decides what moves forward.

Pick up where
you left off.

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 library
A project, with a memory Example
MONDAY / THE DIRECTION

Product launch sync

Keep the Friday launch. Review the brief on Thursday.

Decision
WEDNESDAY / THE FOLLOW-THROUGH

Launch deck review

The deck is ready. The audience statement still needs a final review.

Open question
FRIDAY / A BETTER STARTING POINT

Ready for the next conversation.

The direction, the work, and what’s still open.

Different conversations.
The same clarity.

Less catching up. More moving forward.

Keep the decisions, dependencies, and responsibilities from your team’s conversation in one shared picture.

Explore team workflows
Weekly product syncExample
“We can ship Friday if the design review is done by Thursday.”
Direction
Friday launch, subject to design sign-off.
Next step
Maya to review the launch brief by Thursday.
Still open
Is the audience statement ready for approval?

Your notes. Your judgment. Your next move.

Start with what you have.

Bring in a text transcript or meeting notes. Import .txt, .md, or .markdown files.

Keep the review yours.

Confirm the wording, the owner, and the deadline. Review history keeps your choices visible.

Take your context with you.

Export meeting notes as Markdown. Keep a readable copy wherever your work goes next.

Good questions.

Read the Cardinal guide
What is Cardinal?

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.

What can I try in the preview?

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.

Does Cardinal record or join my meetings?

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.

How does Cardinal connect to Co-Mo?

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.

Can I change a summary or a proposed action?

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.

Where does my preview data go?

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.

Let the conversation
lead somewhere.

Start with a meeting. Leave with a direction.

Try the interactive workspace preview. No account needed.