16.6 Logical Runtime Plane Requirements

Go To Top

The Logical Architecture / PIM SHALL define the following Logical Runtime Planes:Logical Control PlaneLogical Data PlaneLogical Health and Observability PlaneLogical Policy and Release PlaneLogical Audit and Provenance PlaneThe Logical Control Plane SHALL support operational coordination among Logical Nodes.The Logical Data Plane SHALL carry domain and analytical information among Logical Nodes.The Logical Health and Observability Plane SHALL support observation of operational condition and behaviour.The Logical Policy and Release Plane SHALL support governed access, disclosure, safeguarding, and release of information.The Logical Audit and Provenance Plane SHALL support auditability, provenance, lineage, reconstruction, replay, and defensibility.The Logical Architecture / PIM SHALL distinguish Logical Runtime Planes from DDS domains, DDS topics, DDS partitions, REST resource groups, RPC service groups, message queues, event streams, Kubernetes namespaces, network segments, security zones, deployment environments, and runtime configuration groupings.Cross-plane logical relationships SHALL preserve the distinct architectural purpose of each Logical Runtime Plane involved.Cross-plane logical relationships SHALL identify the originating plane, related plane, interaction, information structure, participating Nodes or Roles, governance constraints, and Evidence expectations when those relationships affect governance, release, recovery, auditability, provenance, or Evidence.

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