dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane

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-b-terms-and-definitions:r:runtime_plane [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:runtime_plane to dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane nick_didodido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Runtime Plane ====== ====== Runtime Plane ======
  
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
  
-A Runtime Plane classifies the architectural purpose of runtime communication and behaviour. Runtime Planes help the architecture keep distinct the different kinds of runtime activity, including control, data, health and observability, policy and release, and audit and provenance.+A Runtime Plane classifies the architectural purpose of runtime communication and behavior. Runtime Planes help the architecture keep distinct the different kinds of runtime activity, including control, data, health and observability, policy and release, and audit and provenance.
  
 Runtime Plane classification helps authors and reviewers understand why an interaction exists, what concern it supports, and which governance, traceability, evidence, or access-control expectations may apply. Runtime Plane classification helps authors and reviewers understand why an interaction exists, what concern it supports, and which governance, traceability, evidence, or access-control expectations may apply.
Line 13: Line 13:
 ===== Definition ===== ===== Definition =====
  
-//classification of runtime communication and behaviour by architectural purpose//+//classification of runtime communication and behavior by architectural purpose//
  
 ===== Source ===== ===== Source =====
Line 25: Line 25:
 ===== Example ===== ===== Example =====
  
-A heartbeat message may belong to the Health and Observability Plane, while a command acknowledgement may belong to the [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]].+A heartbeat message may belong to the Health and Observability Plane, while a command acknowledgement may belong to the [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]].
  • dido/99_annexes/annex-b-terms-and-definitions/r/runtime_plane.1783793683.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido