Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:f:fx_command_acknowledgement [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:f:fx_command_acknowledgement to dido:99_annexes:annex-b-terms-and-definitions:f:fx_command_acknowledgement nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:f:fx_command_acknowledgement [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== FX Command Acknowledgement ======
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 ===== Discussion =====
@@ Line 7: / Line 7: @@
 An FX Command Acknowledgement represents the outcome of receiving or processing an FX Control Command.
-The FX Command Acknowledgement identifies the original command, acknowledging FX logical [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|Node]], acknowledgement status, timestamp, reason, resulting lifecycle state, and [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] or [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] reference.
+The FX Command Acknowledgement identifies the original command, acknowledging FX logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], acknowledgement status, timestamp, reason, resulting lifecycle state, and [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] reference.
-FX Command Acknowledgements participate primarily in the FX Logical [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]]. They also support the FX Logical [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane|Health and Observability Plane]] when the acknowledgement reports operational state and the FX Logical [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] when command outcomes support review or evidence.
+FX Command Acknowledgements participate primarily in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]]. They also support the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane|Health and Observability Plane]] when the acknowledgement reports operational state and the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] when command outcomes support review or evidence.
 ===== Definition =====
@@ Line 17: / Line 17: @@
 ===== Source =====
-Specialisation of Logical Acknowledgement from [[fxdemo:02-part:start]], Section 8.7, Logical Command from [[fxdemo:02-part:start]], Section 8.6, and [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from [[fxdemo:01-part:start]], Section 7.10; generalised from command acknowledgement and control-plane material in the original FX Demo [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
+Specialization of Logical Acknowledgement from [[fxdemo:02-part:start]], Section 8.7, Logical Command from [[fxdemo:02-part:start]], Section 8.6, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from [[fxdemo:01-part:start]], Section 7.10; generalised from command acknowledgement and control-plane material in the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
 ===== Note =====
-An FX Command Acknowledgement does not require synchronous communication, blocking calls, command middleware, orchestration status, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:a:api|API]] response, DDS sample, or queue message.
+An FX Command Acknowledgement does not require synchronous communication, blocking calls, command middleware, orchestration status, [[dido:99_annexes:annex-b-terms-and-definitions:a:api|API]] response, DDS sample, or queue message.
 ===== Example =====