This section identifies the normative requirements established for the Logical Runtime Plane Model. The canonical requirement statements are maintained in Annex C: Requirements, Part 2, Section 16.6.
Table 16-5: Logical Runtime Plane requirements.
| Requirement ID | Statement |
|---|---|
| P2-REQ-16-6-001 |
The Logical Architecture / PIM SHALL define the following Logical Runtime Planes: |
| P2-REQ-16-6-002 |
The Logical Control Plane SHALL support operational coordination among Logical Nodes. |
| P2-REQ-16-6-003 |
The Logical Data Plane SHALL carry domain and analytical information among Logical Nodes. |
| P2-REQ-16-6-004 |
The Logical Health and Observability Plane SHALL support observation of operational condition and behavior. |
| P2-REQ-16-6-005 |
The Logical Policy and Release Plane SHALL support governed access, disclosure, safeguarding, and release of information. |
| P2-REQ-16-6-006 |
The Logical Audit and Provenance Plane SHALL support auditability, provenance, Logical Information Lineage, reconstruction, replay, and defensibility. |
| P2-REQ-16-6-007 |
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. |
| P2-REQ-16-6-008 |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.