16.7 Logical Interaction Requirements

Go To Top

The Logical Architecture / PIM SHALL define reusable Logical Interaction Patterns.The Logical Architecture / PIM SHALL define the following Logical Interaction Patterns:Register NodeReport Node StatusPublish Domain InformationSubscribe to Domain InformationIssue Control CommandAcknowledge Control CommandRequest Policy DecisionRecord Audit and ProvenanceReplay or Reconstruct InformationEach Logical Interaction Pattern SHALL identify participating Logical Nodes or Logical Node Roles.Each Logical Interaction Pattern SHALL identify the Logical Communication Endpoints involved.Each Logical Interaction Pattern SHALL identify the Logical Data Structure Instances exchanged, recorded, or referenced.Each Logical Interaction Pattern SHALL identify the Logical Runtime Plane(s) involved.Each Logical Interaction Pattern SHALL identify Traceability expectations.Each Logical Interaction Pattern SHALL identify Evidence expectations for later deployment, testability, and Evidence planning.Logical Interaction Patterns SHALL remain independent of DDS, REST, RPC, Protocol Buffers, message queues, event streams, file exchange, shared services, databases, logs, or deployment mechanisms.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.