Differences

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

--- fxdemo:02-part:01-scope:start [2026/07/11 11:10] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:02-part:01-scope:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 3: / Line 3: @@
 [[fxdemo:02-part:start|Go to Top]]
-This part defines a distributed, node-based Logical Architecture for the Financial Systems [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] as a [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model]].
+This part defines a distributed, node-based Logical Architecture for the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] as a [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model]].
-This part specialises the Conceptual Architecture defined in [[fxdemo:01-part:start]] into platform-independent logical elements, relationships, responsibilities, constraints, information flows, interaction patterns, runtime-plane relationships, governance relationships, and traceability relationships. This part also defines the logical basis for policy-governed information sharing, sovereignty-aware release, residency-aware movement, metadata and aggregate view generation, release control, and release [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. It identifies how the Logical Policy and Release Plane supports distributed enforcement, replicated decision capability, policy administration, policy information sources, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:o:obligation|obligations]], release-specific exchanges, and audit/evidence relationships without prescribing a specific policy engine, gateway product, communication technology, or deployment topology.
+This part specializes the Conceptual Architecture defined in [[fxdemo:01-part:start]] into platform-independent logical elements, relationships, responsibilities, constraints, information flows, interaction patterns, runtime-plane relationships, governance relationships, and traceability relationships. This part also defines the logical basis for policy-governed information sharing, sovereignty-aware release, residency-aware movement, metadata and aggregate view generation, release control, and release [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. It identifies how the Logical Policy and Release Plane supports distributed enforcement, replicated decision capability, policy administration, policy information sources, [[dido:99_annexes:annex-b-terms-and-definitions:o:obligation|obligations]], release-specific exchanges, and audit/evidence relationships without prescribing a specific policy engine, gateway product, communication technology, or deployment topology.
-This part applies to financial structured-information processing systems that use identifiable logical [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] to communicate through explicit logical [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]]. It defines the Logical Architecture before later parts select communication technologies, data serialisation formats, programming languages, deployment mechanisms, runtime infrastructure, test mechanisms, and evidence-capture mechanisms.
+This part applies to financial structured-information processing systems that use identifiable logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]] to communicate through explicit logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]]. It defines the Logical Architecture before later parts select communication technologies, data serialisation formats, programming languages, deployment mechanisms, runtime infrastructure, test mechanisms, and evidence-capture mechanisms.
 This part defines one Logical Architecture that conforms to Part 1. It does not define every possible Logical Architecture that conforms to the Financial Systems Archetype Conceptual Architecture.
-This part does not define the FX Demo Logical Profile. [[fxdemo:03-part:start]] defines that profile. This part does not define DDS mappings, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structures, QoS profiles, Python implementation patterns, Protocol Buffers mappings, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:rest|REST]] bindings, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:rpc|RPC]] bindings, container-image mappings, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:k:kubernetes|Kubernetes]] or [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:k:k3s|K3s]] deployment, Crucible scenarios, acceptance checks, scripts, repository structure, or runtime evidence. Later parts and supporting repository documentation address those concerns.
+This part does not define the FX Demo Logical Profile. [[fxdemo:03-part:start]] defines that profile. This part does not define DDS mappings, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structures, QoS profiles, Python implementation patterns, Protocol Buffers mappings, [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|REST]] bindings, [[dido:99_annexes:annex-b-terms-and-definitions:r:rpc|RPC]] bindings, container-image mappings, [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes|Kubernetes]] or [[dido:99_annexes:annex-b-terms-and-definitions:k:k3s|K3s]] deployment, Crucible scenarios, acceptance checks, scripts, repository structure, or runtime evidence. Later parts and supporting repository documentation address those concerns.