13.5 Runtime Plane Requirements

Go to Top

1. The Conceptual Architecture SHALL define the following conceptual Runtime Planes:

   1. Control Plane
   2. Data Plane
   3. Health and Observability Plane
   4. Policy and Release Plane
   5. Audit and Provenance Plane
2. The Control Plane SHALL support operational coordination among Nodes.
3. The Data Plane SHALL carry Domain and analytical information among Nodes.
4. The Health and Observability Plane SHALL support observation of operational condition and behaviour.
5. The Policy and Release Plane SHALL support governed access, disclosure, safeguarding, and release of information.
6. The Audit and Provenance Plane SHALL support auditability, provenance, lineage, reconstruction, and defensibility.
7. The Conceptual Architecture SHALL distinguish Runtime Planes from implementation mechanisms.
8. 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.
9. Cross-plane relationships SHALL preserve the distinct architectural purpose of each Runtime Plane involved.
10. Cross-plane relationships SHALL be Traceable when they affect Governance and Authority, release, recovery, auditability, provenance, or Evidence.
11. 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.
12. The Policy and Release Plane SHALL support data sovereignty and data residency as conceptual release and movement concerns.
13. The Policy and Release Plane SHALL support policy-governed release without requiring all protected information to pass through a single central policy mechanism.
14. 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.
15. The Policy and Release Plane SHALL NOT treat metadata release or aggregate release as authorisation to release full transaction detail.