Skip to content

Architecture Decision Records

ADRs document the significant architectural decisions made in UC-BoK — including context, rationale, and consequences. They are normative: all catalog content, specifications, and tooling must conform to accepted ADRs.


ADR Register

Code Title Status
ADR-001 Canonical Repository Layout Superseded by ADR-002
ADR-002 Source of Truth Strategy Accepted
ADR-003 Canonical Knowledge Model Accepted
ADR-004 Ontology Modularization Accepted
ADR-005 YAML as Canonical Source Layer Accepted
ADR-006 Canonical Relationship Vocabulary Accepted
ADR-007 Business Object Ontology Accepted
ADR-008 Capability Ontology Accepted
ADR-009 Business Event Ontology Accepted
ADR-010 Process Ontology Accepted
ADR-011 Application Ontology Accepted
ADR-012 Semantic Constraints Model Accepted
ADR-013 Reference Architecture as Vertical Composition Accepted
ADR-014 Unified Commerce Maturity Index (UCMI) Accepted
ADR-015 Semantic Model Specification Accepted
ADR-016 Operational Experience Model Accepted
ADR-017 Vendor Assessment Requires Evidence-Based Workshop Accepted
ADR-018 UC-BoK Editorial Publishing Platform (ED-001) Accepted
ADR-019 UC-BoK MCP Server Accepted
ADR-020 Object Lifecycle Model Accepted
ADR-021 UC Rust Reference Implementation and Feedback Loop Accepted

Status Definitions

Status Meaning
Accepted Decision is in force — all new work must comply
Superseded Replaced by a later ADR — kept for historical record
Deprecated No longer relevant — retained for traceability
Proposed Under discussion — not yet binding

How to Read an ADR

Each ADR contains:

  • Context — the problem or question that triggered the decision
  • Decision — what was decided and why
  • Consequences — what changes, what becomes easier, what becomes harder

ADRs are immutable once Accepted. New decisions create new ADRs; they do not edit previous ones.