MONNET.md is a markdown file at the root of every workspace. It’s the persistent brief Monnet reads at the start of every motion. You write it in plain English — no syntax to learn, no schema to follow.
Treat MONNET.md as the place you write down what you’d otherwise re-explain every time.
When to add to MONNET.md
Add a line (or a section) whenever:- Monnet makes the same mistake a second time.
- You type the same clarification into a motion or a chat that you’ve typed before.
- A new project manager joining your team would need the same context to be productive.
What to put in it
Useful things to encode:- About your organization — mission, stage, who’s involved.
- Priorities — top-level goals for the quarter or the year.
- Typical workflows — how specific kinds of motions usually unfold.
- Membership rules — who has to be a reviewer or editor on what.
- Style and format — how motions should be structured if you have preferences.
- Things to avoid — topics, tones, or actions Monnet shouldn’t take.
Example
Here’s a lightly-edited version of Monnet’s ownMONNET.md:
Editing MONNET.md
Open it from the workspace sidebar under MONNET.md. Edit it like any markdown file. Changes take effect on the next motion you create. You can also ask Monnet to help you build or refine it. In a new motion:Let’s define our core product workflows for MONNET.md.
We need to agree on who approves what to be encoded in MONNET.md.Monnet will draft changes, propose them to the team, and (once approved) update the file directly.