Skip to main content
A motion is Monnet’s atomic unit — a natural-language proposal for action. Every non-trivial thing your team does can be captured as a motion: a feature to ship, a vendor to pick, a policy to ratify, a priority to set.

​
The three phases

When you submit a motion, Monnet works through three phases with your team. They blend together — Monnet decides what each step needs based on what it learned on the previous one.
1

Gather input

Research the topic on the web, read past motions, pull context from files, and ask the right people the right questions.
2

Align

Draft and refine the proposal, post comments, ping approvers, iterate — until the team is aligned.
3

Take action

Prompt an agent, open a ticket, send a message, or update a record. Whatever moves the motion from decided to done.
A clear proposal might only need approvals. A small bug fix moves straight to execution. A complex decision goes through several deliberation rounds. You can see what Monnet plans to do next at any point, and you can steer it.

​
How Monnet acts: tools

Tools are what make Monnet capable of coordination. Without tools, an LLM can only answer with text. With tools, Monnet can read, write, message, and delegate. Monnet’s built-in tools fall into four categories:
CategoryWhat Monnet can do
KnowledgeSearch and browse the web, search and read motions, read files.
MotionEdit the document, edit the summary, edit the plan, set the priority.
CommunicationPost comments, send messages, ask for approval.
DelegationPrompt an agent.
Monnet picks which tools to use based on the motion and what it learned along the way. When you say “let’s discuss the impact of Opus 4.7 on us,” Monnet might:
  1. Search and browse the web to learn about Opus 4.7.
  2. Draft a motion.
  3. Ask you a few questions to understand your perspective.
  4. (After you publish) loop in the teammates most impacted.
  5. Identify some next steps.
  6. Get your approval.
  7. Kick off new motions for those next steps.

​
User interfaces

Two pages are where you and your team interact with Monnet:
  • Inbox — what motions need your input, across all your workspaces.
  • Motion page — the proposal itself, its current state, and where you comment, approve, or chat with Monnet.

​
Motion roles

Each motion has its own roles, independent of workspace-level permissions:
RoleWhat they can do
EditorEdit the motion, manage motion members, change its state.
CommenterPost comments and chat with Monnet.
ExternalHold the permissions defined by their role, without broader access to the workspace.

​
Publishing and visibility

A motion is not visible to others until you publish it. Until then, you can iterate with Monnet privately. Once published, it appears in the inbox of the people involved, and they can comment, approve, or take the actions their role allows.