The Logical Architecture / PIM defines communication roles and interaction patterns without prescribing how a selected technology implements them.
A logical publication does not require DDS or an event stream. A logical subscription does not require topic-based middleware. A logical request does not require REST or RPC. A logical command does not require an orchestration command or control API. A logical acknowledgement does not require synchronous communication.
Implementation profiles select communication patterns and technologies that realize the logical interaction while preserving logical meaning, Traceability, Runtime Plane classification, governance constraints, and Evidence expectations.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.