Differences

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

Link to this comparison view

Next revision
Previous revision
fxdemo:03-part:05-fx-demo-logical-profile-overview:05-4-fx-demo-logical-node-network:start [2026/07/09 16:35] – created owenfxdemo:03-part:05-fx-demo-logical-profile-overview:05-4-fx-demo-logical-node-network:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 2: Line 2:
 [[fxdemo:03-part:05-fx-demo-logical-profile-overview:start | Go To FX Demo Logical Profile Overview ]] [[fxdemo:03-part:05-fx-demo-logical-profile-overview:start | Go To FX Demo Logical Profile Overview ]]
  
-The FX Demo Logical Node Network consists of identifiable FX logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] that perform FX-specific responsibilities and communicate through explicit FX logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]].+The FX Demo Logical Node Network consists of identifiable FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] that perform FX-specific responsibilities and communicate through explicit FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]].
  
-The network includes FX logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] for transaction intake, validation, semantic interpretation, contract state management, cash-flow computation, policy and release, audit and provenance, health and observability, registry and coordination, replay and reconstruction, and external oversight consumption.+The network includes FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] for transaction intake, validation, semantic interpretation, contract state management, cash-flow computation, policy and release, audit and provenance, health and observability, registry and coordination, replay and reconstruction, and external oversight consumption.
  
-Each FX logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] has a logical responsibility within the FX Demo. The logical architecture treats those responsibilities separately, even when a later implementation profile packages several responsibilities into a single runtime artefact or distributes a single responsibility across multiple runtime artefacts.+Each FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] has a logical responsibility within the FX Demo. The logical architecture treats those responsibilities separately, even when a later implementation profile packages several responsibilities into a single runtime artifact or distributes a single responsibility across multiple runtime artifacts.
  
-The FX Demo Logical Node Network supports modularity, reviewability, controlled evolution, operational coordination, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], provenance, release control, replay, reconstruction, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] planning.+The FX Demo Logical Node Network supports modularity, reviewability, controlled evolution, operational coordination, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], provenance, release control, replay, reconstruction, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] planning.
  
 ---- ----
  • fxdemo/03-part/05-fx-demo-logical-profile-overview/05-4-fx-demo-logical-node-network/start.1783640129.txt.gz
  • Last modified: 2026/07/09 16:35
  • by owen