Project Overview¶
Purpose¶
Unified Commerce has become one of the most widely used concepts in modern retail. UC-BoK aims to define a vendor-neutral reference model describing the full Unified Commerce domain, independent of any product or vendor.
Scope¶
UC-BoK documents concepts, not products.
| Domain | Coverage |
|---|---|
| Business Domains | 8 bounded domains |
| Business Capabilities | 22 classified capabilities |
| Business Services | 60+ services |
| Business Objects | 39 domain objects |
| Business Processes | 12 end-to-end processes |
| Business Events | 73 domain events |
| Application Archetypes | 12 application types |
| Vendor Mapping | Growing |
Audience¶
- Enterprise Architects
- Solution Architects
- Product Managers
- Retail CIOs and CTOs
- System Integrators
Deliverables¶
- Formal ontology specifications (
specifications/) - YAML catalog models (
catalogs/) - Capability maps and reference architectures
- Vendor coverage mapping
- Validation pipeline (
make check)
Current Release¶
v1.1.1-alpha — Knowledge Graph + Assessment Engine
The meta-model is stable and formally specified. The v1.x stream delivers a fully navigable Knowledge Graph (819 nodes, 3 764 relationships), three vertical Reference Architectures (Fashion, Grocery, Specialty Retail), the UCMI Assessment Engine, and 17 Architecture Decision Records.
The success metric is no longer "how many catalogs do we have?" but "how many Unified Commerce concepts are formally defined, validatable, and queryable — and how precisely can we assess a retailer against them?"
References¶
- UCBOK-001 — Meta Model
- UCBOK-002 — Principles
- UCBOK-003 — Taxonomy
- UCBOK-004 — Source Model Governance