10.7 Acknowledge Control Command [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 10.7 Acknowledge Control Command ======
[[fxdemo:02-part:start | Go To Top ]]

The Acknowledge Control Command pattern allows a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] to report receipt, acceptance, rejection, completion, failure, or outcome of a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_command|Logical Command]].

A command-consuming [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] produces a Logical Acknowledgement. The acknowledgement identifies the original command, the acknowledging [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], the acknowledgement status, timestamp, reason, resulting lifecycle state, and provenance or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] reference.

The interaction belongs primarily to the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]]. It also supports the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]] when the acknowledgement reports operational state, and the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] when the architecture records command outcome.

Table 10-6:	Acknowledge Control Command logical interaction pattern

^ Element ^ Logical treatment ^
| Primary Runtime Plane | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]] |
| Producing Logical Node Role | [[dido:99_annexes:annex-b-terms-and-definitions:c:command_consumer_role|Command Consumer]], Managed Node, Worker Node, or Controlled Node |
| Consuming Logical Node Role | [[dido:99_annexes:annex-b-terms-and-definitions:c:command_producer_role|Command Producer]], Control Node, Coordinator, or Operator-facing Node |
| Primary information | Logical Acknowledgement |
| Supporting information | Command identifier, acknowledgement status, reason, timestamp, resulting lifecycle state |
| Traceability expectation | Acknowledgement traces to the original command, acknowledging [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], outcome, and related lifecycle state. |
| Evidence expectation | Acknowledgement record supports review of command handling and operational accountability. |

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>