dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-001:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-001:start [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-01:p1-req-13-5-001:start to dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-001:start nick_didodido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-001:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== P1-REQ-13-5-001 ====== ====== P1-REQ-13-5-001 ======
  
-[[dido:99_annexes:annex-c-requirements:part-01:start|Return to Part 1 Requirements]]+[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
  
 ===== Statement ===== ===== Statement =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-The Conceptual Architecture requires a defined set of Runtime Planes to separate runtime communication and behaviour by architectural purpose. These planes provide the conceptual basis for coordinating Nodes, carrying domain and analytical information, observing operational condition, governing release, and supporting audit and provenance.+The Conceptual Architecture requires a defined set of Runtime Planes to separate runtime communication and behavior by architectural purpose. These planes provide the conceptual basis for coordinating Nodes, carrying domain and analytical information, observing operational condition, governing release, and supporting audit and provenance.
  
 Defining the Runtime Planes at the conceptual level prevents implementation mechanisms, deployment boundaries, or runtime identifiers from replacing architectural purpose. Defining the Runtime Planes at the conceptual level prevents implementation mechanisms, deployment boundaries, or runtime identifiers from replacing architectural purpose.
Line 48: Line 48:
 Related requirement identifiers: Related requirement identifiers:
  
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-5-002:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-002:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-5-003:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-003:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-5-004:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-004:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-5-005:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-005:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-5-006:start]]+  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-006:start]]
  
 ===== Status ===== ===== Status =====
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-5-001/start.1783799863.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido