| Next revision | Previous revision |
| fxdemo:02-part:16-logical-requirements:16-6-logical-runtime-plane-requirements:start [2026/07/03 14:32] – created owen | fxdemo:02-part:16-logical-requirements:16-6-logical-runtime-plane-requirements:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| ====== 16.6 Logical Runtime Plane Requirements ====== | ====== 16.6 Logical Runtime Plane Requirements ====== |
| [[fxdemo:02-part:start | Go To Top ]] | [[fxdemo:02-part:16-logical-requirements:start | Go To Logical Requirements ]] |
| | |
| | This section identifies the normative requirements established for the Logical Runtime Plane Model. The canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-02:start|Annex C: Requirements, Part 2, Section 16.6]]. |
| | |
| | <WRAP table-caption> |
| | **Table 16-5:** Logical Runtime Plane requirements. |
| | </WRAP> |
| | |
| | ^ Requirement ID ^ Statement ^ |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-001|P2-REQ-16-6-001]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-001#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-002|P2-REQ-16-6-002]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-002#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-003|P2-REQ-16-6-003]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-003#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-004|P2-REQ-16-6-004]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-004#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-005|P2-REQ-16-6-005]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-005#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-006|P2-REQ-16-6-006]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-006#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-007|P2-REQ-16-6-007]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-007#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-008|P2-REQ-16-6-008]] | {{section>fxdemo:99_part_annexes:annex-c-requirements:part-02:p2-req-16-6-008#statement&noheader& |
| |
| - The Logical Architecture / PIM SHALL define the following Logical Runtime Planes: | |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]] | |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] | |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]] | |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_policy_and_release_plane|Logical Policy and Release Plane]] | |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]] SHALL support operational coordination among [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]]. | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] SHALL carry domain and analytical information among [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]]. | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]] SHALL support observation of operational condition and behaviour. | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_policy_and_release_plane|Logical Policy and Release Plane]] SHALL support governed access, disclosure, safeguarding, and release of information. | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] SHALL support auditability, provenance, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_information_lineage|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 [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node_role|Roles]], governance constraints, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations when those relationships affect governance, release, recovery, auditability, provenance, or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. | |
| |
| ---- | ---- |
| |
| <WRAP centeralign> | <WRAP centeralign> |
| | |
| © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| | |
| </WRAP> | </WRAP> |
| | |