3.4 Traceability to Part 2 Distributed Node-Based Logical Architecture / PIM Part 2 defines the reusable, distributed, node-based Logical Architecture / PIM. This part specialises the Part 2 logical architecture for the FX Demo. The FX Demo Logical Profile inherits the Part 2 logical models and applies them to the Foreign Exchange Domain. It specialises Logical Nodes into FX logical Nodes, Logical Communication Endpoints into FX endpoints, Logical Data Structure Definitions into FX information definitions, Logical Runtime Planes into FX runtime-plane participation, Logical Interaction Patterns into FX interaction patterns, and Logical Traceability relationships into FX traceability relationships. Table 3-4: Part 2 logical elements specialised by the FX Demo Logical Profile Part 2: logical element Part 3 FX logical treatment Logical Node FX Transaction Intake Node, FX Validation Node, FX Semantic Interpretation Node, FX Contract State Node, FX Cash-Flow Computation Node, FX Policy and Release Node, FX Audit and Provenance Node, FX Health and Observability Node, FX Registry and Coordination Node, FX Replay and Reconstruction Node, and External Oversight Participant. Logical Node Role FX-specific roles such as Transaction Intake Role, Structural Validation Role, Semantic Interpretation Role, Cash-Flow Computation Role, Policy Evaluation Role, Release Control Role, Audit Recording Role, Provenance Recording Role, and Oversight Consumption Role. Logical Communication Endpoint FX-specific endpoints for transaction intake, validation results, semantic interpretation, contract state, cash-flow obligations, policy decisions, release packages, audit records, provenance records, node status, control commands, replay requests, and replay results. Logical Data Structure Definition FX-specific information definitions such as FX Transaction Candidate, FX Transaction Record, FX Validation Result, FX Semantic Assertion, FX Contract State, FX Cash-Flow Obligation, FX Policy Decision, FX Release Package, FX Audit Record, and FX Provenance Record. Logical Runtime Plane FX-specific participation in Control, Data, Health and Observability, Policy and Release, and Audit and Provenance planes. Logical Interaction Pattern FX-specific interaction patterns for transaction intake, validation, semantic interpretation, contract-state update, cash-flow computation, policy decision, release, audit/provenance, replay, and reconstruction. Logical Governance Model FX-specific ownership, versioning, compatibility, change control, admission rules, and policy constraints. Logical Traceability Model FX-specific traceability from concepts and reusable logical elements to FX profile elements, implementation mappings, deployment artefacts, and evidence expectations.