Differences

This shows you the differences between two versions of the page.

--- fxdemo:00-part:01-introduction:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:00-part:01-introduction:start [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 2: / Line 2: @@
 [[fxdemo:00-part:start | Go to Top ]]
-[[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:f:financial_system]] increasingly depend on automated and semi-automated processing of structured information. These systems must preserve meaning, traceability, auditability, governance, and evidence across changing business, technical, and institutional environments.
+[[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system]] increasingly depend on automated and semi-automated processing of structured information. These systems must preserve meaning, traceability, auditability, governance, and evidence across changing business, technical, and institutional environments.
-The [[fxdemo:dido_99_annexes:annex-a-acronyms:start#sdis| SDIS/SIP-RA]] discipline provides high-level guidance for structured information processing systems generally. It addresses concerns such as forms, interpretation pipelines, data and control separation, traceable transformations, audit and review, and governance. The SIP-RA overview frames the issue as cross-domain and identifies financial transactions and regulatory/compliance reporting as examples within a broader class of structured information systems.
+The [[dido:99_annexes:annex-a-acronyms:start#sdis| SDIS/SIP-RA]] discipline provides high-level guidance for structured information processing systems generally. It addresses concerns such as forms, interpretation pipelines, data and control separation, traceable transformations, audit and review, and governance. The SIP-RA overview frames the issue as cross-domain and identifies financial transactions and regulatory/compliance reporting as examples within a broader class of structured information systems.
-The Financial Systems [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:a:archetype]] applies that general discipline to financial systems. It does so through a layered set of documents. The layers begin with stable concepts, then develop platform-independent logical architecture, domain-specific profiles, implementation mappings, physical deployment, testability, and [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:e:evidence]].
+The Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype]] applies that general discipline to financial systems. It does so through a layered set of documents. The layers begin with stable concepts, then develop platform-independent logical architecture, domain-specific profiles, implementation mappings, physical deployment, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence]].
 Read the document set from the inside outward. Begin with the stable concepts, then move to the logical architecture, domain profile, implementation profile, deployment profile, and evidence layer.