| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:01-part:13-conceptual-requirements:13-5-runtime-plane-requirements [2026/07/01 14:28] – 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 |
|---|
| ====== 13.5 Runtime Plane Requirements ====== | ====== 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 [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:runtime_plane|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]]. |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] | |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]] | <WRAP table-caption> |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane|Health and Observability Plane]] | **Table 13.5-1:** Part 1 runtime plane requirements. |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] | </WRAP> |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] SHALL support operational coordination among [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:n:node|Nodes]]. | ^ Requirement ID ^ Statement ^ |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]] SHALL carry [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:domain|Domain]] and analytical information among [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:n:node|Nodes]]. | | [[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}} | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane|Health and Observability Plane]] SHALL support observation of operational condition and behaviour. | | [[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}} | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL support governed access, disclosure, safeguarding, and release of information. | | [[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}} | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] SHALL support auditability, provenance, lineage, reconstruction, and defensibility. | | [[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}} | |
| - The Conceptual Architecture SHALL distinguish [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]] from implementation mechanisms. | | [[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}} | |
| - The Conceptual Architecture SHALL NOT treat a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] as a DDS Domain, DDS Topic, DDS partition, Kubernetes namespace, network segment, container group, security zone, or deployment environment. | | [[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}} | |
| - Cross-plane relationships SHALL preserve the distinct architectural purpose of each [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] involved. | | [[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}} | |
| - Cross-plane relationships SHALL be [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceable]] when they affect [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]], release, recovery, auditability, provenance, or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. | | [[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}} | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|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. | | [[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}} | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL support data sovereignty and data residency as conceptual release and movement concerns. | | [[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}} | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL support policy-governed release without requiring all protected information to pass through a single central policy mechanism. | | [[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}} | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL support later logical realisation through policy enforcement, policy decision, policy administration, policy information, obligation, release, and audit/evidence capabilities. | | [[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}} | |
| - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL NOT treat metadata release or aggregate release as authorisation to release full transaction detail. | | [[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> |