Governance pillar · v0.7.1

bdr Bdr

YAML frontmatter schema for Business Decision Records (extended MADR format). Includes `related` field from report types (D7).

$id · https://corpospec.com/schemas/v0.7.1/bdr.schema.json

Fields

Field Type Required Description
date IsoDate yes ISO 8601 date (YYYY-MM-DD).
decision_makers string[] yes
id PathRef yes Path-based cross-reference relative to .corpospec/ root. Pattern: `^[a-z0-9_-]+(/[a-z0-9_.-]+)+$`
pillars Pillar[] yes
risk_level RiskLevel yes Risk level.
status BdrStatus yes BDR status. Includes Draft and Rejected from server types (D1 exception).
consulted string[]
financial_impact FinancialImpact?
informed string[]
related PathRef[]
review_date IsoDate?
supersedes PathRef[]
title string? Optional explicit title for the decision. When present, the Cockpit and report pipeline prefer this over the first body H1 heading.

Definitions

Shared types referenced within this schema.

BdrStatus
BDR status. Includes Draft and Rejected from server types (D1 exception).
enum: "draft", "proposed", "accepted", "rejected", "deprecated", "superseded"
FinancialImpact
Financial impact of a decision.
type: object
IsoCurrency
ISO 4217 currency code.
pattern: ^[A-Z]{3}$
IsoDate
ISO 8601 date (YYYY-MM-DD).
type: string
PathRef
Path-based cross-reference relative to .corpospec/ root. Pattern: `^[a-z0-9_-]+(/[a-z0-9_.-]+)+$`
pattern: ^[a-z0-9_-]+(/[a-z0-9_.-]+)+$
Pillar
Pillar name.
enum: "entity", "financials", "metrics", "product", "market", "people", "legal", "governance", "integrations", "brand"
RiskLevel
Risk level.
enum: "low", "medium", "high", "critical"

Reference in your YAML

# yaml-language-server: $schema=https://corpospec.com/schemas/v0.7.1/bdr.schema.json