====== Logical Acknowledgement ====== [[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]] ===== Discussion ===== A Logical Acknowledgement represents a Logical Data Structure Instance that reports receipt, acceptance, rejection, completion, failure, or other outcome for a command, request, message, event, or processing step. Logical Acknowledgements support coordination and review by making outcomes explicit. They help Logical Nodes avoid hidden assumptions about whether another Node received information, acted on a command, completed processing, or encountered an error. A Logical Acknowledgement supports traceability by identifying the acknowledged item, acknowledging the Logical Node, status, timestamp, reason, and provenance or evidence reference. ===== Definition ===== //Logical Data Structure Instance reporting receipt, acceptance, rejection, completion, failure, or outcome.// ===== Source ===== Specialization of Data Structure Instance, Communication Endpoint, and Traceability from Part 1, Sections 7.8, 7.6, and 7.10; generalised from command acknowledgement and control-plane material in the original FX Demo Reference Architecture. ===== Note ===== A Logical Acknowledgement does not require synchronous communication. Implementation profiles realize acknowledgements through selected communication mechanisms. ===== Example ===== A retry-command acknowledgement reports that a Logical Node received a retry command, accepted it, and started recovery processing. ---- [[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]] ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.