====== 3.1 Traceability to SIP-RA ======
[[fxdemo:03-part:start | Go To Top ]]

SIP-RA supplies the parent architecture discipline for structured information processing systems. This part applies and specializes that discipline for the [[dido:99_annexes:annex-b-terms-and-definitions:f:foreign_exchange_domain|Foreign Exchange Domain]].

The FX Demo Logical Profile preserves the SIP-RA emphasis on structured information, explicit interfaces, separation of concerns, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceable interpretation]], governed processing, reviewability, and implementation independence. It applies those concerns by defining FX-specific logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], logical interaction patterns, logical governance relationships, and logical [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships.

<WRAP table-caption>
**Table 3-1:** SIP-RA concerns addressed by the FX Demo Logical Profile.
</WRAP>

^ SIP-RA concern ^ Part 3 FX logical treatment ^
| Structured information processing | Defines FX logical information structures, including [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_transaction_candidate|FX Transaction Candidate]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result|FX Validation Result]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state|FX Contract State]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_obligation|FX Cash-Flow Obligation]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_decision|FX Policy Decision]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_audit_record|FX Audit Record]], and [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_provenance_record|FX Provenance Record]]. |
| Explicit interfaces | Defines FX logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]] for intake, validation, interpretation, contract state, cash-flow obligations, policy decisions, release packages, audit, provenance, status, control, and replay. |
| Separation of concerns | Preserves FX-specific separation among [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_policy_and_release_plane|Logical Policy and Release Plane]], and [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]]. |
| Traceable interpretation | Defines [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from FX input records through validation, semantic interpretation, contract state, cash-flow computation, policy decisions, audit, provenance, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations. |
| Governed processing across boundaries | Defines FX policy and release interactions before external oversight participants receive released information. |
| Audit and review | Defines FX audit, provenance, replay, reconstruction, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations at the logical profile level. |
| Implementation independence | Avoids binding the FX Demo Logical Profile to [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]], [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]], [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|QoS]], [[dido:99_annexes:annex-b-terms-and-definitions:p:python|Python]], [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes|Kubernetes]], [[dido:99_annexes:annex-b-terms-and-definitions:k:k3s|K3s]], [[dido:99_annexes:annex-b-terms-and-definitions:d:docker|Docker]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rti_connext_dds|RTI Connext DDS]], [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]], [[dido:99_annexes:annex-b-terms-and-definitions:p:protocol_buffers|Protocol Buffers]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|REST]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rpc|RPC]], or other implementation mechanisms. |

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>