====== Data Structure Instance ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]] ===== Discussion ===== A Data Structure Instance is a populated occurrence of a [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]]. It contains actual values that conform to the governing Data Structure Definition. A Data Structure Instance may appear as a message, record, event, assertion, command, command acknowledgement, status report, heartbeat, policy decision, release record, audit event, provenance record, or persisted entry. A Data Structure Instance may move through a Communication Endpoint, reside in a persistence mechanism, support an audit trail, or appear in an evidence package. It remains distinct from the Data Structure Definition that governs it. ===== Definition ===== //populated occurrence of a [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]]// ===== Source ===== Adapted from FX Demo Reference Architecture, Section 2.1.4, Data Structure Instance; aligned with SIP-RA separation of structured artifacts from their definitions and interpretations. ===== Note ===== A Data Structure Instance is not a [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]], [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], DDS Topic, [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], or [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]]. ===== Example ===== A specific cash-flow obligation record with a transaction identifier, payment date, currency, amount, payer, and receiver is a Data Structure Instance governed by a cash-flow obligation [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]]. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.