====== FX Command Acknowledgement ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] ===== Discussion ===== 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: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: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 ===== //receipt, acceptance, rejection, completion, failure, or outcome of an FX Control Command// ===== Source ===== 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:annex-b-terms-and-definitions:a:api|API]] response, DDS sample, or queue message. ===== Example ===== An FX Command Acknowledgement reports that the FX Validation Node accepted a retry command and entered the Recovering lifecycle state.