Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
fxdemo:02-part:00-introduction:start [2026/07/18 12:33] – external edit 127.0.0.1fxdemo:02-part:00-introduction:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 5: Line 5:
 [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial systems]] often operate across institutions, platforms, jurisdictions, organizations, and technical environments. They exchange structured information, coordinate operational behavior, apply rules, produce analytical results, control release, record [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|provenance]], and preserve [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]]. A Logical Architecture must organize those responsibilities before any implementation profile selects technologies, products, protocols, programming languages, deployment mechanisms, or runtime infrastructure. [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial systems]] often operate across institutions, platforms, jurisdictions, organizations, and technical environments. They exchange structured information, coordinate operational behavior, apply rules, produce analytical results, control release, record [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|provenance]], and preserve [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]]. A Logical Architecture must organize those responsibilities before any implementation profile selects technologies, products, protocols, programming languages, deployment mechanisms, or runtime infrastructure.
  
-[[fxdemo:01-part:start]] defines the conceptual foundation for the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]]. This part builds outward from that foundation by defining a distributed, node-based Logical Architecture as a [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model]]. It treats the system as a network of identifiable logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] that communicate via explicit logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]] and exchange logical Data Structure Instances conforming to logical Data Structure Definitions.+[[fxdemo:01-part:start]] defines the conceptual foundation for the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]]. This part builds outward from that foundation by defining a distributed, node-based Logical Architecture as a [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model]]. It treats the system as a network of identifiable logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]] that communicate via explicit logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]] and exchange logical Data Structure Instances conforming to logical Data Structure Definitions.
  
 This part makes distribution a logical architectural choice. The Logical Architecture supports independently operating Logical Nodes, cross-boundary communication, and participation in [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], including the [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane|Health and Observability Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]], and [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]]. This logical distribution supports modularity, separation of concerns, traceability, evidence, governance, and independent evolution. This part makes distribution a logical architectural choice. The Logical Architecture supports independently operating Logical Nodes, cross-boundary communication, and participation in [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], including the [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane|Health and Observability Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]], and [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]]. This logical distribution supports modularity, separation of concerns, traceability, evidence, governance, and independent evolution.
  • fxdemo/02-part/00-introduction/start.1784403224.txt.gz
  • Last modified: 2026/07/18 12:33
  • by 127.0.0.1