Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:c:command_producer_role [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:99_annexes:annex-b-terms-and-definitions:c:command_producer_role [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== Command Producer Role ======
+[[dido:99_annexes:annex-b-terms-and-definitions:c:start|Return to C Terms]]
+===== Discussion =====
+A Command Producer Role identifies a Logical Node's responsibility for issuing a command through a Logical Communication Endpoint.
+Commands express intended operational action. They belong primarily to the Logical Control Plane unless a domain profile defines a more specific logical treatment. A command differs from a domain event because it instructs a participant to act rather than reporting that something occurred.
+A Logical Node performing a Command Producer Role identifies the command, the target Logical Node or role, the expected acknowledgement, the applicable Runtime Plane, and the traceability expectations.
+===== Definition =====
+//Communication Role responsible for issuing a command through a Logical Communication Endpoint.//
+===== Source =====
+Specialization of Communication Endpoint, Node Role, and Control Plane from Part 1, Sections 7.6, 7.4, and 8.2; generalised from control-plane command material in the original FX Demo Reference Architecture.
+===== Note =====
+A Command Producer Role does not require a specific command protocol, middleware feature, orchestration command, or API style.
+===== Example =====
+A logical Control Node performs a Command Producer Role when it issues a request for another Logical Node to report status, pause work, resume work, retry processing, or initiate recovery.
+----
+[[dido:99_annexes:annex-b-terms-and-definitions:c:start|Return to Top]]