EDCP — Event Domain-Centric Pattern Layer 4 of the SDIA Ecosystem — Final Version EDCP is the semantic topology governance layer for event-driven fabrics within the SDIA ecosystem (Semantic Domain Integration Architecture). Its role is not to define routing logic or payload schemas, but to govern how event artifacts are named, segmented, owned, and audited across brokers, queues, event meshes, IoT fabrics, service meshes, and edge runtimes. In EDCP, the domain becomes the primary key of all event topology. Topics, queues, consumer groups, mesh subjects, IoT topics, service mesh resources, edge routes, and cache keys are named with the domain as the first segment — not by technology, team, or platform. The artifact is not immutable. Governance is the goal. The Essentials: One domain namespace for all event artifacts ABNF grammar (RFC 5234) for 10 artifact types Domain Authority ownership and lifecycle governance Domain-scoped ACLs (finance.*) for security Multi-team, multi-division, multi-project qualifiers Validated patterns for: Broker topics (Kafka, Pulsar, RabbitMQ, AWS SNS, Azure Event Hubs) Message queues (AWS SQS, Azure Service Bus, RabbitMQ, JMS) Consumer groups (Kafka) Event mesh subjects (Solace, AWS EventBridge, Azure Event Grid) IoT fabrics (MQTT) Service mesh (Kubernetes / Istio) Edge routes and cache keys Schema registry subjects This is the FINAL version of EDCP. No further structural updates will be made. The grammar, PVRL validation rules, and governance model are complete and stable. Author: Ricardo Luz Holanda Viana · ORCID: 0009-0009-9549-5862Repository: github.com/rhviana/deipDEIP Ecosystem DOI: 10.5281/zenodo.19004802License: CC BY 4.0 Citation: Viana, R. L. H. (2026). Event Domain-Centric Pattern (EDCP) — Version 1.0. Zenodo. https://doi.org/10.5281/zenodo.19068766 The domain never lies. The event artifact is governable. 👁️
Viana Ricardo Luz Holanda (Tue,) studied this question.