====== 10.4 Publish Domain Information ======
[[fxdemo:02-part:start | Go To Top ]]

The Publish Domain Information pattern allows a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] to produce domain, financial, analytical, lifecycle, validation, or derived information through a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]].

A publishing [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] produces a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|Logical Data Structure Instance]] governed by a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definition]]. The publication identifies the producing [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], the endpoint, the Runtime Plane, the information structure, and the [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] expectations associated with the publication.

The interaction belongs primarily to the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]]. It also supports the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] by recording provenance for published information in the logical architecture.

Table 10-3:	Publish Domain Information logical interaction pattern

^ Element ^ Logical treatment ^
| Primary Runtime Plane | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] |
| Producing Logical Node Role | [[dido:99_annexes:annex-b-terms-and-definitions:p:publisher_role|Publisher]], [[dido:99_annexes:annex-b-terms-and-definitions:e:event_producer_role|Event Producer]], Assertion Producer, or Domain Information Producer |
| Consuming Logical Node Role | [[dido:99_annexes:annex-b-terms-and-definitions:s:subscriber_role|Subscriber]], [[dido:99_annexes:annex-b-terms-and-definitions:e:event_consumer_role|Event Consumer]], Validator, Interpreter, Auditor, or Oversight Node |
| Primary information | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_event|Logical Event]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_message|Logical Message]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_assertion|Logical Assertion]], or [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_record|Logical Record]] |
| Supporting information | Producing [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], endpoint identity, information definition, timestamp, and provenance reference |
| Traceability expectation | Published information traces to its definition, producing [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], endpoint, Runtime Plane, and provenance context. |
| Evidence expectation | Captured publication supports review of information flow and downstream processing. |

----

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