Skip to content

Decision Schema Must Be Structured

Rule

All decisions must be expressed using a structured YAML decision schema and not as unstructured narrative text.

Rationale

Enables machine processing, UI rendering, and consistent interpretation across the system.

Applies To

  • applies to ADR only, not rules
  • enforces separation between architect decision and governance approval

Output Schema must include:

---
id: "adr-<pattern-id>-<decision-type>-<date>"
knowledgeType: "architecture_decision_record"
pattern_id: "<pattern-id>"
decision_scope: "pattern | system | component | workflow | governance"
decision_target: "<pattern-id | component-name | system-element>"

classification: "core | supporting | project | system | component"

decision:
  type: "<adoption|keep|promotion|demotion|creation|definition|refactor>"
  status: "proposed"  # architect decision status
  decided_by: "architect"
  date: "<YYYY-MM-DD>"

  rationale:
    summary: "<short explanation>"

  evidence:
    strength: "<high|medium|low>"

  confidence: "<high|medium|low>"

governance:
  forum_status: "pending"   # accepted | rejected | deferred"
  forum_decision_date: null # YYYY-MM-DD
---

See Also