Revisiting Domain-Driven Design: Shared Invariants and the Domain Zero Pattern

This paper revisits the conceptual foundations of Domain-Driven Design (DDD) from the perspective of real enterprise operations. While DDD proposes organizing software systems around domain models and bounded contexts, many real-world organizations operate through end-to-end processes that span multiple departments and functional areas. The paper argues that such processes rely on a small set of shared organizational entities — including counterparties, products, contracts, financial transactions, documents, and employees — that participate simultaneously in multiple business processes. These entities function as shared invariants of enterprise systems and cannot be cleanly partitioned across isolated domain boundaries without introducing duplication of data, synchronization mechanisms, and loss of a unified organizational view. To formalize this observation, the paper introduces a process–entity model of enterprise systems and shows that entities participating in multiple processes inevitably become shared invariants of the system. Based on this analysis, the concept of Domain Zero is proposed as a foundational architectural domain responsible for maintaining the shared informational core of an organization. Domain Zero corresponds conceptually to Master Data Management (MDM), but is treated here as an explicit architectural component rather than an external integration layer. The paper concludes that enterprise systems are structurally organized around shared invariants rather than isolated domains, and that effective enterprise architectures must explicitly preserve this shared informational core.