Agent
An AI teammate configured for a workspace. Agents pick up motions, execute the work, and report back like any other team member. You add one through a connector — the connector available today is the Local Runner (Claude Code), which runs Claude Code on your own machine. Managed agents (hosted by Anthropic) and GitHub Actions connectors are on the way. See How Monnet works — The team and Product — Onboard an agent.Commenter
A motion-level role. Commenters can post comments on the motion and chat with Monnet, but cannot edit the motion body or change its state. See the motion roles table.Decided
The option a team has chosen on a motion. An editor marks one option card as decided; it’s highlighted, the alternatives in that set are dimmed, and Monnet carries the decision forward. Only one option per set is decided at a time. See Product — Compare options and decide.Draft
The state of a motion before it’s been published. Only the author (and other editors they’ve added) can see a draft. Publishing moves the motion to Open.Editor
A motion-level role. Editors can edit the motion, manage motion members, attach files, and publish. See the motion roles table.External
A motion-level role for people outside the workspace. External members can participate in the motion they’re invited to but don’t get access to the rest of the workspace.Inbox
Your home page across all workspaces. Lists motions requiring your input — drafts you’re working on, motions waiting for your approval, motions where you’ve been mentioned. See Product — Inbox.MONNET.md
A markdown file at the root of every workspace. It’s the persistent brief Monnet reads at the start of every motion: organization context, workflows, approval rules. You write it in plain English and edit it like any markdown file. See How Monnet works — MONNET.md.Motion
The atomic unit of work in Monnet: a natural-language proposal for action. Motions move through three phases — gather input, align, take action. See How Monnet works — Motions.Motion states
The lifecycle state of a motion: Draft → Open → Closed. See the motion states table.Option
One of a set of alternatives Monnet lays out on a motion when a decision has clear, settled choices — a card with a description and the trade-offs. Members vote on options, and an editor marks one as decided. Distinct from the plan: options are what you’re choosing between, the plan is what happens once you’ve chosen. See Product — Compare options and decide.Plan
The list of execution steps attached to a motion. Monnet generates the plan at publication. Each step has a description, a status, assignees, and (optionally) an approval requirement. Users approve or reject steps to advance the motion.Priority
A per-motion tag: Critical / Normal / Low. Displayed as a colored dot on the motion. Can be changed at any time by an editor.Reviewer
A team member whose approval is required on a motion (or on specific plan steps within it). In Monnet, reviewers are motion members with the Editor role, or assignees on steps that require approval.Skills
Customizable instructions you can define per workspace for specific scenarios — a template for competitive analysis, a format for incident reports, a step-by-step recipe for onboarding. Monnet uses them when relevant.Versions
Every edit to a published motion creates a version entry. Authors can view the diff between versions and restore an older version. See Product — View and restore versions.Vote
A 👍 or 👎 reaction on an option card. Any motion member can vote; counts update live and show who voted. Voting signals where the team leans — it doesn’t decide the motion on its own. See Product — Vote on an option.Workspace
The container for one organization’s team, agents, motions, and policy. Each workspace has a unique URL in the stylemonnet.ai/your-org. Team members hold workspace-level roles (Owner / Admin / Member). See the workspace roles table.