This is an old revision of the document!
3.1 Traceability to SIP-RA
SIP-RA supplies the parent architecture discipline for structured information processing systems. This part applies and specialises that discipline for the Foreign Exchange Domain.
The FX Demo Logical Profile preserves the SIP-RA emphasis on structured information, explicit interfaces, separation of concerns, traceable interpretation, governed processing, reviewability, and implementation independence. It applies those concerns by defining FX-specific logical Nodes, logical Communication Endpoints, logical information structures, logical Runtime Planes, logical interaction patterns, logical governance relationships, and logical Traceability relationships.
Table 3-1: SIP-RA concerns addressed by the FX Demo Logical Profile.
| SIP-RA concern | Part 3 FX logical treatment |
|---|---|
| Structured information processing | Defines FX logical information structures, including FX Transaction Candidate, FX Validation Result, FX Contract State, FX Cash-Flow Obligation, FX Policy Decision, FX Audit Record, and FX Provenance Record. |
| Explicit interfaces | Defines FX logical 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 Logical Control Plane, Logical Data Plane, Logical Health and Observability Plane, Logical Policy and Release Plane, and Logical Audit and Provenance Plane. |
| Traceable interpretation | Defines Traceability from FX input records through validation, semantic interpretation, contract state, cash-flow computation, policy decisions, audit, provenance, and 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 Evidence expectations at the logical profile level. |
| Implementation independence | Avoids binding the FX Demo Logical Profile to DDS, IDL, QoS, Python, Kubernetes, K3s, Docker, RTI Connext DDS, Crucible, Protocol Buffers, REST, RPC, or other implementation mechanisms. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.