Skip to main content
This page is the canonical reference for Monnet terminology. Terms are listed alphabetically. Reference tables (workspace roles, motion roles, motion states, plan steps) are at the bottom.

Agent

An AI teammate configured for a workspace. Agents pick up plan steps, do the work, and report back like any other team member. You add one through a connector — the connector available today is the Local Runner, which runs Claude Code or Codex on your own machine. See Agents.

Check-in

A one-off reminder you ask Monnet to schedule on a motion for a specific moment — “check in with me Thursday afternoon”. Monnet resolves the moment in your local timezone, then comes back where you asked for it: the public feed, or your private conversation. Check-ins run on Open motions only, fire once, and can be updated or cancelled at any time. Distinct from a due date, which is about work rather than a moment. See Ask Monnet to check in later.

Commenter

A motion-level role. Commenters post comments and chat with Monnet, but can’t edit the motion or change its state. See the motion roles table.

Company brain

Your workspace’s wiki: what the team knows, maintained by Monnet from closed motions and uploaded sources. Motions record what happened; the brain records what you ended up believing. See Company brain.

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 Motion — Compare options and decide.

Draft

The state of a motion before it’s kicked off. Only the author and editors they’ve added can see it. Kicking it off moves it to Open.

Due date

An optional date on a plan step. Monnet checks dated steps daily and follows up on the ones slipping. Computed in your workspace’s timezone.

Editor

A motion-level role. Editors edit the motion, manage members, attach files, kick it off, close it, and reopen it. See the motion roles table.

General access

A motion’s workspace-wide sharing setting, like a shared document: Restricted (only the author and explicit members — the default) or Workspace (everyone in the workspace, as an editor or a commenter). Sharing with the workspace also makes a motion eligible for the brain’s nightly ingest once closed. See Motion — Sharing.

Guest

Someone invited to a single motion from outside the workspace. A guest takes part in that motion as a commenter and sees nothing else — not your other motions, not your company brain. Guests are usually reached by email.

Inbox

Your home page across all workspaces. Lists motions requiring your attention. See Inbox.

Motion

The unit of work in Monnet: a natural-language proposal for action, with a document, a plan, members, and a discussion. Every motion begins as a thread. See Motion.

Motion states

Draft → Open → Closed, and back to Open on reopen. See the motion states table.

Option

One of a set of alternatives Monnet lays out when a decision has clear, settled choices — a card with a description and the trade-offs. Members vote on options; an editor marks one decided. Distinct from the plan: options are what you’re choosing between, the plan is what happens once you’ve chosen.

Perspectives

Per-member profiles Monnet refreshes nightly: what’s top of mind, how to engage someone, their recurring concerns and past positions. Built from the team’s shared record, never from private conversations.

Plan

The tree of execution steps attached to a motion. Steps sit in groups that run in parallel or in sequence; each step has one assignee, a type, a status, and optionally a date or an approval requirement. See Plan.

Playbooks

Reusable instructions telling Monnet how to draft and coordinate a particular kind of motion. Three ship with every workspace — decision, bug-fix, new-feature — and you can write your own. Previously called Skills. See Workspace — Playbooks.

Policies

Your workspace’s standing rules: how the team works, what it prioritizes, who approves what. Monnet reads them on every engagement. They live on a page in the company brain named after your workspace. Previously a MONNET.md file in workspace settings.

Priority

A per-motion tag: Critical / Normal / Low. Displayed as a colored dot. Changeable at any time by an editor.

Runner

The process on your own machine that executes an agent’s work — Claude Code or Codex, your subscription, your repositories. A runner belongs to you and serves every workspace you’re in. See Agents — What a Local Runner is.

Sources

The raw material the company brain is built from: files you upload, and closed motions shared workspace-wide. Sources are read, never edited — when a page is wrong, you correct the page.

Step type

What a plan step asks of its assignee: task, approval, decision, interview, or closing. See the plan steps table.

Thread

A private one-to-one conversation with Monnet about an idea — no document, no plan, nobody else. A thread becomes a motion when Monnet writes the document. During web onboarding, Write spec makes that transition after your first idea review. It’s the same object throughout; nothing is copied.

Versions

Every edit to an open motion creates a version entry. You can view the diff between versions and restore an older one — as a new version, so nothing is lost.

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.

Workspace

The container for one organization’s team, agents, motions, and brain. Team members hold workspace-level roles (Owner / Admin / Member). See the workspace roles table.

Reference tables

Workspace roles

Motion roles

Motion states

Plan steps