Core concepts
mDecide has a small vocabulary, and most of what the platform does becomes obvious once you hold it. This section defines that vocabulary for an architect or analyst evaluating the platform. It assumes no prior exposure to mDecide.
The words here are the same words used on the product’s screens, in decision pack configuration, and in the documentation your team would use after a deployment. Learning them once is enough.
Where to start
Read the pages in order the first time through. Each one builds on the one before it.
| Page | What it covers |
|---|---|
| Decisions and Decision Value Loops | The decision as a durable record, the five-phase loop it runs in, and the difference between a loop and one pass through it |
| Decision Packs | An industry decision workflow delivered as packaged, versioned configuration |
| Data products and plugins | How data travels from a system you already run into evidence a decision can stand on, and onto a screen |
| Agents and runtimes | Agents, the containers they run in, the tools they hold, and how authority is divided between people and agents |
| Workstreams and phases | The unit of agent-led work, how phases are structured, and what a phase gate checks |
| Glossary | Every term above, defined in one line |
If you would rather see the concepts in motion before you read the definitions, the tour of one decision cycle follows a single decision end to end.
The one idea underneath all of it
mDecide treats the decision itself as the thing worth keeping — not the data that fed it, not the conversation that produced it, not the task that followed it.
Most tools that touch a decision handle the material around it. Spreadsheets, dashboards, business intelligence platforms, and chat interfaces all surface information that supports a decision, then let the decision evaporate. What remains afterward is a reconstruction: transcripts, slides, email, and memory.
mDecide keeps the decision as a structured record — the context it was made in, the alternatives that were weighed, the evidence that informed it, the person who made the call, what they expected to happen, and later, what actually happened. Every concept in this section exists to make that record trustworthy, so the next decision of the same kind starts from what the last one learned.