M-Builder is where team workflows are made — any step-by-step process you want to run with the AI. Describe the stages and what good looks like at each one, publish, and every project can run it.
A workflow is a recipe the AI follows with you: stages in a fixed order, each one saying what it needs from you, what the AI does with it, and what "good enough" means before moving on. Nothing hidden — you can read exactly what each stage will do before you run it.
If you can describe a process, you can build one — no code involved. AI Translators, PMs, and Sales all define their own. And when a workflow is improved, projects already running it keep working the way they started — nothing shifts under you mid-project.
Four moves from idea to running project — you build in M-Builder, you run in M-Workflow, and the vault carries everything in between.
Every published workflow lives in one shared library in the vault, so the whole team draws from the same set. Pick one for your project — or build your own when none fits.
The 4-stage AI Translator flow — prep, workshop, synthesis, spec draft, capped by a QA gate — was built this way and is ready to use. It's the proof of the pattern, not the boundary of it.
See it run in M-WorkflowA desktop app for macOS and Windows, distributed internally. First run connects it to the team's workflow library.