Differences

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

--- fxdemo:00-part:02-scope:start [2026/07/07 11:38] – owen
+++ fxdemo:00-part:02-scope: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]]
-This part defines the scope, structure, and intended use of the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:f:financial_system|Financial Systems]] [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set.
+This part defines the scope, structure, and intended use of the [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial Systems]] [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set.
-It explains how the document set applies the SDIS/SIP-RA discipline to financial systems by separating conceptual architecture, logical architecture, domain profiles, implementation profiles, deployment profiles, testability, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|evidence]]. It gives readers a common map for understanding the relationships among the parts and the proper use of each.
+It explains how the document set applies the SDIS/SIP-RA discipline to financial systems by separating conceptual architecture, logical architecture, domain profiles, implementation profiles, deployment profiles, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]]. It gives readers a common map for understanding the relationships among the parts and the proper use of each.
-This part applies to all documents in the Financial Systems Archetype document set, including the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:conceptual_model]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_model]] / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model]], FX Demo Logical Profile, Phase 0 Implementation Profile / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_specific_model]], and Phase 0 Deployment, Testability, and Evidence Plan.
+This part applies to all documents in the Financial Systems Archetype document set, including the [[dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model]] / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model]], FX Demo Logical Profile, Phase 0 Implementation Profile / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model]], and Phase 0 Deployment, Testability, and Evidence Plan.
-This part does not define the Financial Systems Archetype concepts. [[fxdemo:01-part:start]] defines those concepts. This part does not define the platform-independent [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Model]]. [[fxdemo:02-part:start]] defines that model. This part does not define the FX demonstration profile, Phase 0 implementation mappings, deployment procedures, Crucible scenarios, acceptance checks, scripts, repository structure, or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:runtime_plane|runtime]] evidence. Later parts and supporting repository documentation address those concerns.
+This part does not define the Financial Systems Archetype concepts. [[fxdemo:01-part:start]] defines those concepts. This part does not define the platform-independent [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Model]]. [[fxdemo:02-part:start]] defines that model. This part does not define the FX demonstration profile, Phase 0 implementation mappings, deployment procedures, Crucible scenarios, acceptance checks, scripts, repository structure, or [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|runtime]] evidence. Later parts and supporting repository documentation address those concerns.
 This part guides readers, authors, reviewers, implementers, and maintainers in using the document set consistently. It establishes document-set boundaries, layering rules, and navigation guidance to prevent implementation details from redefining the conceptual or logical architecture.