| 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 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:annex-b-terms-and-definitions:n: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 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. |