mDecide documentation
These pages describe mDecide: what the platform is, the concepts it is built on, how a single decision runs on it, how it deploys, and how organizations adopt it.
They are written for people evaluating mDecide against a specific decision in their own operations — the person who owns that decision, the architect who will review the deployment before it goes anywhere near production data, and the program leader accountable for what it returns.
The register is documentary rather than promotional. What is described here as present is capability the platform has today. Planned work is confined to What’s coming, where it is labeled forward-looking and carries no dates.
Already running mDecide?
Operational documentation ships with your deployment instead of living here: onboarding and first login, per-surface how-to guides, decision-pack configuration, administration, and troubleshooting. Sign in to your environment and open Help from the primary navigation.
Those pages are pinned to the release your deployment is running, so the procedures and screens you read about match the ones in front of you. For anything they do not cover, email mdecidesupport@metricsiq.ai.
What’s here
| Page | What it covers |
|---|---|
| What is mDecide | Platform definition, who it is for, and the capabilities it includes |
| Core concepts | The working vocabulary: decisions and Decision Value Loops, decision packs, data products and plugins, agents and runtimes, workstreams and phases, and a glossary |
| Tour: one decision cycle | A walkthrough of one decision from human framing through to recorded outcome |
| Architecture overview | Deployment shape, single-tenant isolation, and how the deployment scales with decision volume |
| Trust and security | Data handling, security controls, compliance posture, and the split of responsibilities between your team and ours |
| Adopting mDecide | The mPlan, mPilot, mLaunch, and mOperate progression, and what onboarding involves |
| What’s coming | Curated forward look at platform direction; subject to change |
| FAQ | Questions that come up during evaluation, including the support and service posture |
If you are new to mDecide, read What is mDecide first, then take the tour. If you are reviewing the platform on behalf of IT or security, start with Architecture overview and Trust and security.
Talking to us
To see mDecide worked against one of your own decisions and your own data, use the Book a Consultation link in the site header. Evaluation conversations start from a named decision, not a demo.