Concept
What is Decision Memory in MDM
Decision Memory keeps context around why rules, schemas, and approvals were created — so teams stop re-debating the same choices.
Definition
Decision Memory is the combination of model definitions, change history, approval events, and operational metadata that explains how a master data decision was made.
Why it matters
- Reduces repeated debates about naming, validation, and ownership rules.
- Improves onboarding: new team members can see both data and rationale.
- Supports compliance by linking published records to accountable decisions.
Concrete example
- A steward rejects a supplier bank-account change — the approval event and reason stay in audit history.
- The entity YAML in Git shows why tax-ID validation was added (regex + required).
- Months later, an AI agent or new teammate can read the same governed surface instead of inventing a new rule.
How EntiHub supports it
- YAML entity definitions store explicit structure and validation intent.
- Approvals and audit records preserve stewardship decisions.
- CLI + Git workflow keeps model evolution visible over time — see CLI & AI and MDM and AI agents.