Expand description
Decision model for MADR-compliant decision records
Implements the Data Decision Log (DDL) feature for tracking architectural and data-related decisions using the MADR (Markdown Any Decision Records) template format.
§File Format
Decision records are stored as .madr.yaml files following the naming convention:
{workspace}_{domain}_adr-{number}.madr.yaml
§Example
id: 550e8400-e29b-41d4-a716-446655440000
number: 1
title: "Use ODCS v3.1.0 for all data contracts"
status: accepted
category: datadesign
domain: sales
date: 2026-01-07T10:00:00Z
deciders:
- data-architecture@company.com
context: |
We need a standard format for defining data contracts.
decision: |
We will adopt ODCS v3.1.0 as the standard format.
consequences: |
Positive: Consistent contracts across domainsStructs§
- Asset
Link - Link to an asset (table, relationship, product, etc.)
- Compliance
Assessment - Compliance assessment for the decision
- Decision
- MADR-compliant Decision Record
- Decision
Contact - Contact details for decision ownership
- Decision
Driver - Driver/reason for the decision
- Decision
Index - Decision log index (decisions.yaml)
- Decision
Index Entry - Decision index entry for the decisions.yaml file
- Decision
Option - Option considered during decision making
- Raci
Matrix - RACI matrix for decision responsibility assignment
Enums§
- Asset
Relationship - Relationship type between a decision and an asset
- Decision
Category - Decision category
- Decision
Status - Decision status in lifecycle
- Driver
Priority - Priority level for decision drivers