====== 2.3 Relationship to FDIS-RA ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:02-relationship-to-the-architecture-documents:start | Return to Relationship to the Architecture Documents ]]

[[dido:99_annexes:annex-b-terms-and-definitions:f:fdis-ra|FDIS-RA]] gives the project its financial-domain interpretation alignment. It helps the team distinguish [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]], metadata, attributes, parameters, [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|Lifecycle]] behaviour, monitoring, signals, indicators, and oversight.

This handbook does not implement the full FDIS-RA. Instead, it prepares the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] so that later phases can add financial-domain [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]] without turning the system into ad hoc code. Phase 0 establishes the [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] structure, [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] pattern, generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] discipline, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] topic conventions, logging expectations, and [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] behaviour that later FDIS-aligned work will need.

The team should use FDIS-RA as the source of financial-domain Interpretation meaning. The team should use this handbook to carry that meaning into executable Artifacts in a disciplined and repeatable way.

----

<WRAP centeralign>

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

</WRAP>