Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====== Logical Event ====== [[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]] ===== Discussion ===== A Logical Event represents a Logical Data Structure Instance that reports an occurrence, observation, state change, decision, derived result, or other fact relevant to the architecture. A Logical Event reports that something occurred or that a Logical Node observed, produced, derived, decided, or changed something. It does not instruct another Node to act. Commands express intended action; events report occurrence or result. Logical Events support distributed processing by allowing Logical Nodes to communicate changes, observations, and results without requiring hidden coupling between producers and consumers. ===== Definition ===== //Logical Data Structure Instance reporting an occurrence, observation, state change, decision, or result.// ===== Source ===== Specialization of Data Structure Instance from Part 1, Section 7.8; generalised from domain-event and data-plane material in the original FX Demo Reference Architecture. ===== Note ===== A Logical Event is not an event-streaming technology or event-bus implementation. Implementation profiles realize events through selected communication mechanisms. ===== Example ===== A transaction-received event reports that a Transaction Intake Node received a candidate transaction record. ---- [[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]] dido/99_annexes/annex-b-terms-and-definitions/l/logical_event.txt Last modified: 2026/07/18 12:33by 127.0.0.1