Overview

The Reference Data domain contains foundational entities that other domains reference. These entities describe the types of materials, organizations, and facilities that appear across transactional and operational modules.

Context

The domain’s modules and their relationships, with the client and server domains wired to the actual modules they depend on. Clients sit to the left of the servers they depend on; every arrow is a dependency the client calls, and together they form a DAG.

Inside the domain there is one dependency — Item resolves suppliers and pins vendor roles in Business Affiliate; Staff stands alone. Every other domain is a client: procurement pins all three modules from its orders, receiving pins items and carriers, and operations and resources read items.

Modules

Module	Description
Items	Material types tracked for inventory, purchasing, and production
Business Affiliates	Legal entities participating in business transactions
Staff	People and other real-world agents that work is assigned to

Characteristics

Reference data entities follow the full Data Authority Pattern with bitemporal persistence, draft management, and tenant scoping. They serve as stable reference points for transactional data.

They also share a common lifecycle and reference discipline — versioned records, the Live → Retired lifecycle, version pins with floating and frozen reads, and retirement gates at the point of choice — stated once in the Reference-Data Module Pattern. Each module’s page covers only what is specific to its own entities.