Semantic Domain Integration Architecture (SDIA): A Vendor‑Agnostic Semantic Governance Model for Enterprise Integration — v2.0

SDIA — Semantic Domain Integration Architecture Version 2.0 — The Essentials in 5 Lines Step What it means 1. Define a semantic address /domain/entity/action/target — business intent, not technology 2. Route through the gateway GDCR — one proxy per domain, immutable, vendor-agnostic 3. Resolve at runtime DDCR — 7-stage deterministic engine, metadata lookup, sub-4ms 4. Execute in orchestration ODCP — domain package, iFlow DNA, tiered credentials 5. Emit to the event layer DCEP — domain.entity.action.v1 — PVRL-validated channel Done. One address. One grammar. Four layers. Zero translation loss. Why it works Domain-first invariant → same semantic token at every layer, always Immutable structure → proxies, engine, packages, and event channels never change Metadata-driven control plane → new vendor = one metadata entry, zero redeployment Unified PVRL grammar → violations detected at build time, deploy time, and runtime Fail-fast enforcement → invalid address = immediate rejection before execution What is SDIA? SDIA — Semantic Domain Integration Architecture — is the runtime semantic layer of the DEIP ecosystem. It is a unified end-to-end enterprise integration framework in which business domain semantics govern every layer of the integration stack simultaneously. Unlike traditional integration approaches — where structure is organized by technology, vendor, or platform — SDIA enforces a single invariant: 👉 The business domain is the primary key. Everywhere. Always. 👉 The same semantic token that enters at the gateway exits at the event stream — unchanged. Integration is no longer indexed by technology. It is indexed by business intent. What SDIA Solves Problem Traditional Approach SDIA Proxy Sprawl 1 proxy per backend — 41 for 4 domains 1 proxy per domain — immutable Package Sprawl 39 packages named by vendor 4 packages named by domain Credential Sprawl 1 credential per integration unit Sub-domain tiered governance Event Chaos Ad-hoc topic naming per system PVRL-governed domain channels Vendor Onboarding Proxy + package + credential 1 metadata entry — 30 seconds Routing Failures Non-deterministic, static config 100% accuracy — zero failures SDIA Core Model Component Role Semantic Address Expresses business intent — /sales/orders/create/salesforce GDCR — Gateway Layer Semantic facade — one domain proxy — immutable DDCR — Resolution Engine Deterministic 7-stage pipeline — metadata lookup — sub-4ms ODCP — Orchestration Layer Domain package — iFlow DNA — tiered credential governance DCEP — Event Layer Domain channel grammar — PVRL-validated — broker-agnostic PVRL Grammar Unified formal grammar — enforced at every layer The Semantic Chain /sales/orders/create/salesforce ← GDCR — semantic address dcrporderscsalesforceid01:http ← DDCR — routing key id01.o2c.salesforce.order.s4hana.c.in ← ODCP — iFlow DNA sales.orders.created.v1 ← DCEP — event channel One domain token. Four layers. Zero translation. Validated Results 13 configurations · 8 enterprise platforms · 5 programming languages 42 IoT sensors · 4 IoT environments ~2,067,904 requests processed 100% routing accuracy Zero routing failures Sub-4ms resolution latency 🌍 Simple Orientation Real-World Analogy What It Means Hospital Patient says "emergency" — that word guides every internal system Airport Traveler follows "boarding" — internal complexity stays invisible SDIA Business says "sales/orders/create" — that meaning never changes 📦 Composition of SDIA Component Role GDCR Semantic gateway — defines what enters DDCR Resolution engine — defines how it resolves ODCP Orchestration layer — defines where it executes DCEP Event layer — defines what propagates asynchronously PVRL Unified grammar — defines what is valid at every layer 📚 Version History Version Status DOI v2.0 ✅ CURRENT — Stable Release 10.5281/zenodo.18877635 v1.0 ⚠️ Deprecated — 🔗 Links Repository: github.com/rhviana/gdcr SDIA (Zenodo): https://doi.org/10.5281/zenodo.18877635 DEIP (Source of Truth): https://doi.org/10.5281/zenodo.19004802 📖 Citation (v2.0) APA: Viana, R. L. H. (2026). Semantic Domain Integration Architecture (SDIA) — Version 2.0. Zenodo. https://doi.org/10.5281/zenodo.18877635 👤 Author Ricardo Luz Holanda Viana Enterprise Integration Architect | SAP BTP Integration Suite Expert | SAP Press Author