dido:99_annexes:annex-b-terms-and-definitions:c:control_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:c:control_plane [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:control_plane to dido:99_annexes:annex-b-terms-and-definitions:c:control_plane nick_didodido:99_annexes:annex-b-terms-and-definitions:c:control_plane [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Control Plane ====== ====== Control 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 =====
  
-The Control Plane supports operational coordination among [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]]. It allows the architecture to manage registration, capability advertisement, health reporting, command handling, configuration coordination, schema and model version coordination, work assignment, retries, recovery, replay, and other runtime management concerns.+The Control Plane supports operational coordination among [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]]. It allows the architecture to manage registration, capability advertisement, health reporting, command handling, configuration coordination, schema and model version coordination, work assignment, retries, recovery, replay, and other runtime management concerns.
  
 The Control Plane does not normally carry domain truth. It coordinates how Nodes operate, but it does not replace the Data Plane, Policy and Release Plane, Health and Observability Plane, or Audit and Provenance Plane. The Control Plane does not normally carry domain truth. It coordinates how Nodes operate, but it does not replace the Data Plane, Policy and Release Plane, Health and Observability Plane, or Audit and Provenance Plane.
  
-A later implementation profile may realise Control Plane interactions through DDS Topics, service interfaces, message queues, APIs, configuration channels, or other runtime mechanisms. Those mechanisms do not redefine the Control Plane.+A later implementation profile may realize Control Plane interactions through DDS Topics, service interfaces, message queues, APIs, configuration channels, or other runtime mechanisms. Those mechanisms do not redefine the Control Plane.
  
 ===== Definition ===== ===== Definition =====
  
-//Runtime Plane supporting operational coordination among [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]]//+//Runtime Plane supporting operational coordination among [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]]//
  
 ===== Source ===== ===== Source =====
Line 25: Line 25:
 ===== Example ===== ===== Example =====
  
-A command requesting a [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|Node]] to report status, reload configuration, retry work, or initiate recovery may belong to the Control Plane.+A command requesting a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] to report status, reload configuration, retry work, or initiate recovery may belong to the Control Plane.
  • dido/99_annexes/annex-b-terms-and-definitions/c/control_plane.1783793671.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido