Differences

This shows you the differences between two versions of the page.

--- fxdemo:01-part:13-conceptual-requirements:13-5-runtime-plane-requirements [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:13-5-runtime-plane-requirements to fxdemo:01-part:13-conceptual-requirements:13-5-runtime-plane-requirements owen
+++ fxdemo:01-part:13-conceptual-requirements:13-5-runtime-plane-requirements [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 13.5 Runtime Plane Requirements ======
-[[fxdemo:01-part:start | Go to Top ]]
+[[fxdemo:01-part:13-conceptual-requirements:start | Go to Conceptual Requirements]]
-  - The Conceptual Architecture SHALL define the following conceptual Runtime Planes:
+This section identifies the normative requirements for runtime planes established by Part 1. The canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-01:start|Annex C: Requirements, Part 1]].
-    - Control Plane
-    - Data Plane
-    - Health and Observability Plane;
-    - Policy and Release Plane
-    - Audit and Provenance Plane
-  - The Control Plane SHALL support operational coordination among Nodes.
-  - The Data Plane SHALL carry domain and analytical information among Nodes.
-  - The Health and Observability Plane SHALL support observation of operational condition and behaviour.
-  - The Policy and Release Plane SHALL support governed access, disclosure, safeguarding, and release of information.
-  - The Audit and Provenance Plane SHALL support auditability, provenance, lineage, reconstruction, and defensibility.
-  - The Conceptual Architecture SHALL distinguish Runtime Planes from implementation mechanisms.
-  - The Conceptual Architecture SHALL NOT treat a Runtime Plane as a DDS Domain, DDS Topic, DDS partition, Kubernetes namespace, network segment, container group, security zone, or deployment environment.
-  - Cross-plane relationships SHALL preserve the distinct architectural purpose of each Runtime Plane involved.
-  - Cross-plane relationships SHALL be traceable when they affect governance, release, recovery, auditability, provenance, or evidence.
-  - The Policy and Release Plane SHALL support conceptual separation between full transaction detail, transaction metadata, aggregate summaries, derived indicators, redacted views, masked views, exception views, and full-detail release views.
-  - The Policy and Release Plane SHALL support data sovereignty and data residency as conceptual release and movement concerns.
-  - The Policy and Release Plane SHALL support policy-governed release without requiring all protected information to pass through a single central policy mechanism.
-  - The Policy and Release Plane SHALL support later logical realisation through policy enforcement, policy decision, policy administration, policy information, obligation, release, and audit/evidence capabilities.
-  - The Policy and Release Plane SHALL NOT treat metadata release or aggregate release as authorisation to release full transaction detail.
+<WRAP table-caption>
+**Table 13.5-1:** Part 1 runtime plane requirements.
+</WRAP>
+^ Requirement ID ^ Statement ^
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-001:start|P1-REQ-13-5-001]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-001:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-002:start|P1-REQ-13-5-002]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-002:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-003:start|P1-REQ-13-5-003]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-003:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-004:start|P1-REQ-13-5-004]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-004:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-005:start|P1-REQ-13-5-005]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-005:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-006:start|P1-REQ-13-5-006]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-006:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start|P1-REQ-13-5-007]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-008:start|P1-REQ-13-5-008]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-008:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-009:start|P1-REQ-13-5-009]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-009:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-010:start|P1-REQ-13-5-010]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-010:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-011:start|P1-REQ-13-5-011]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-011:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-012:start|P1-REQ-13-5-012]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-012:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-013:start|P1-REQ-13-5-013]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-013:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-014:start|P1-REQ-13-5-014]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-014:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-015:start|P1-REQ-13-5-015]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-015:start#statement&noheader&nofooter}} |
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>