DIDO Solutions technical documentation and FX Demo knowledge base https://wiki.didosolutions.com/ 2026-08-24T04:38:35+00:00 https://wiki.didosolutions.com/ https://wiki.didosolutions.com/_media/wiki/logo.png text/html 2026-07-21T01:19:35+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-2-001?rev=1784596775&do=diff P3-REQ-17-2-001 Return to Requirements Statement The FX Demo Logical Profile SHALL specialise the Part 2 Distributed Node-Based Logical Architecture / PIM for the Foreign Exchange Domain. Source Part 3, Section 17.2: FX Domain Profile Requirements. Rationale The FX Demo Logical Profile establishes the logical architecture for the Foreign Exchange Domain by specialising the generic Distributed Node-Based Logical Architecture / PIM defined in Part 2. Specialisation enables the architecture… text/html 2026-07-21T01:20:05+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-2-002?rev=1784596805&do=diff P3-REQ-17-2-002 Return to Requirements Statement The FX Demo Logical Profile SHALL preserve the Part 1 Conceptual Architecture. Source Part 3, Section 17.2: FX Domain Profile Requirements. Rationale The Part 1 Conceptual Architecture establishes the architectural principles, separation of concerns, governance model, and conceptual foundation for all subsequent architectural artifacts. Preserving the Conceptual Architecture ensures that the FX Demo Logical Profile remains architecturally … text/html 2026-07-21T01:20:34+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-2-003?rev=1784596834&do=diff P3-REQ-17-2-003 Return to Requirements Statement The FX Demo Logical Profile SHALL preserve the Part 2 Logical Architecture / PIM. Source Part 3, Section 17.2: FX Domain Profile Requirements. Rationale The Part 2 Logical Architecture / PIM defines the reusable, platform-independent logical architecture that serves as the parent for all Domain Logical Profiles. Preserving the Part 2 Logical Architecture ensures that the FX Demo Logical Profile remains compatible with the common logical mo… text/html 2026-07-21T01:20:53+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-2-004?rev=1784596853&do=diff P3-REQ-17-2-004 Return to Requirements Statement The FX Demo Logical Profile SHALL use the inherited classification path Finance Ecosphere → Monetary Ecosystem → Foreign Exchange Domain. Source Part 3, Section 17.2: FX Domain Profile Requirements. Rationale The inherited classification path establishes the architectural context of the FX Demo Logical Profile within the overall Reference Architecture. Using the established Finance Ecosphere, Monetary Ecosystem, and Foreign Exchange Domain… text/html 2026-07-21T01:21:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-2-005?rev=1784596871&do=diff P3-REQ-17-2-005 Return to Requirements Statement The FX Demo Logical Profile SHALL NOT redefine the Finance Ecosphere, Monetary Ecosystem, or Foreign Exchange Domain. Source Part 3, Section 17.2: FX Domain Profile Requirements. Rationale The Finance Ecosphere, Monetary Ecosystem, and Foreign Exchange Domain are defined by higher-level architectural artefacts and provide the common classification framework for all derived profiles. Preventing their redefinition preserves architectural con… text/html 2026-07-21T01:21:35+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-2-006?rev=1784596895&do=diff P3-REQ-17-2-006 Return to Requirements Statement The FX Demo Logical Profile SHALL define FX-specific logical Nodes, Node Roles, Communication Endpoints, information structures, Runtime Plane participation, interaction patterns, governance relationships, traceability relationships, and evidence expectations. text/html 2026-07-21T01:21:54+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-2-007?rev=1784596914&do=diff P3-REQ-17-2-007 Return to Requirements Statement The FX Demo Logical Profile SHALL NOT prescribe implementation technologies, data serialisation formats, programming languages, middleware products, deployment mechanisms, runtime scripts, repository structures, test tools, or evidence-capture mechanisms. text/html 2026-07-21T21:54:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-3-001?rev=1784670852&do=diff P3-REQ-17-3-001 Return to Requirements Statement The FX Demo Logical Profile SHALL define FX logical Nodes. Source Part 3, Section 17.3: FX Logical Node Requirements. Rationale Logical Nodes are the primary architectural building blocks of the FX Demo Logical Profile. Defining FX logical Nodes establishes the logical decomposition of the Foreign Exchange Domain while preserving the platform-independent architectural principles inherited from Parts 1 and 2. text/html 2026-07-21T21:54:35+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-3-002?rev=1784670875&do=diff P3-REQ-17-3-002 Return to Requirements Statement The FX Demo Logical Profile SHALL define the following FX logical Nodes: FX Transaction Intake NodeFX Validation NodeFX Semantic Interpretation NodeFX Contract State NodeFX Cash-Flow Computation NodeFX Policy and Release Node text/html 2026-07-21T21:54:52+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-3-003?rev=1784670892&do=diff P3-REQ-17-3-003 Return to Requirements Statement Each FX logical Node SHALL specialise a Logical Node from Part 2. Source Part 3, Section 17.3: FX Logical Node Requirements. Rationale Specialization preserves the architectural inheritance defined by the Part 2 Logical Architecture while allowing the FX Demo Logical Profile to introduce domain-specific logical behavior. This ensures consistency between the generic platform-independent architecture and the Foreign Exchange specialization. text/html 2026-07-21T21:55:07+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-3-004?rev=1784670907&do=diff P3-REQ-17-3-004 Return to Requirements Statement Each FX logical Node SHALL preserve traceability to the Node from Part 1. Source Part 3, Section 17.3: FX Logical Node Requirements. Rationale Preserving traceability to the Part 1 Conceptual Architecture ensures that every FX logical Node can be related back to its originating architectural concept. This enables governance, architectural review, impact assessment, and evidence generation throughout the lifecycle of the architecture. text/html 2026-07-21T22:16:32+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-3-005?rev=1784672192&do=diff P3-REQ-17-3-005 Return to Requirements Statement Each FX logical Node SHALL identify its FX logical Node Roles, responsibilities, Runtime Plane participation, Communication Endpoints, information structures, governance constraints, traceability relationships, and evidence expectations. text/html 2026-07-21T22:14:50+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-3-006?rev=1784672090&do=diff P3-REQ-17-3-006 Return to Requirements Statement The FX Demo Logical Profile SHALL distinguish FX logical Nodes from processes, services, containers, pods, virtual machines, serverless functions, threads, tasks, libraries, subroutines, RPC endpoints, REST resources, DDS participants, and deployment artefacts. text/html 2026-07-21T22:24:50+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-4-001?rev=1784672690&do=diff P3-REQ-17-4-001 Return to Requirements Statement The FX Demo Logical Profile SHALL define FX logical Node Roles. Source Part 3, Section 17.4: FX Logical Node Role Requirements. Rationale FX logical Node Roles define the logical responsibilities performed within the Foreign Exchange Domain independently of implementation technologies. Defining logical Node Roles provides the architectural abstraction required to allocate responsibilities consistently across logical Nodes while preserving … text/html 2026-07-21T22:25:17+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-4-002?rev=1784672717&do=diff P3-REQ-17-4-002 Return to Requirements Statement The FX Demo Logical Profile SHALL define the following FX logical Node Roles: Transaction Intake RoleStructural Validation RoleSemantic Interpretation RoleContract State Management RoleCash-Flow Computation RolePolicy Evaluation Role text/html 2026-07-21T22:25:40+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-4-003?rev=1784672740&do=diff P3-REQ-17-4-003 Return to Requirements Statement Each FX logical Node Role SHALL specialise Logical Node Role from Part 2. Source Part 3, Section 17.4: FX Logical Node Role Requirements. Rationale Specializing the Part 2 Logical Node Roles preserves the architectural inheritance established by the platform-independent Logical Architecture while allowing the FX Demo Logical Profile to define Foreign Exchange-specific logical responsibilities. This ensures that domain-specific roles remain… text/html 2026-07-21T22:25:55+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-4-004?rev=1784672755&do=diff P3-REQ-17-4-004 Return to Requirements Statement Each FX logical Node Role SHALL preserve traceability to Node Role from Part 1. Source Part 3, Section 17.4: FX Logical Node Role Requirements. Rationale Preserving traceability to the Part 1 Conceptual Architecture ensures that each FX logical Node Role maintains a clear relationship to the architectural concepts from which it is derived. This supports architectural governance, impact analysis, conformance assessment, and evidence generat… text/html 2026-07-21T22:26:07+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-4-005?rev=1784672767&do=diff P3-REQ-17-4-005 Return to Requirements Statement Each FX logical Node Role SHALL identify the responsibility performed by an FX logical Node without prescribing an implementation component, team assignment, operational owner, or deployment unit. Source Part 3, Section 17.4: FX Logical Node Role Requirements. text/html 2026-07-21T22:28:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-5-001?rev=1784672892&do=diff P3-REQ-17-5-001 Return to Requirements Statement The FX Demo Logical Profile SHALL define FX logical Communication Endpoints. Source Part 3, Section 17.5: FX Logical Communication Requirements. Rationale FX logical Communication Endpoints define the logical communication relationships that enable information exchange between FX logical Nodes and FX logical Node Roles. Defining these logical Communication Endpoints establishes the platform-independent communication architecture for the Fo… text/html 2026-07-21T22:28:27+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-5-002?rev=1784672907&do=diff P3-REQ-17-5-002 Return to Requirements Statement The FX Demo Logical Profile SHALL define the following FX logical Communication Endpoints: FX Transaction Intake EndpointFX Validation Result EndpointFX Semantic Interpretation EndpointFX Contract State EndpointFX Cash-Flow Obligation Endpoint text/html 2026-07-21T22:28:43+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-5-003?rev=1784672923&do=diff P3-REQ-17-5-003 Return to Requirements Statement Each FX logical Communication Endpoint SHALL specialise Logical Communication Endpoint from Part 2. Source Part 3, Section 17.5: FX Logical Communication Requirements. Rationale Specializing the Part 2 Logical Communication Endpoints preserves the architectural inheritance established by the platform-independent Logical Architecture while allowing the FX Demo Logical Profile to define communication relationships specific to the Foreign Exc… text/html 2026-07-21T22:28:59+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-5-004?rev=1784672939&do=diff P3-REQ-17-5-004 Return to Requirements Statement Each FX logical Communication Endpoint SHALL preserve traceability to the Communication Endpoint from Part 1. Source Part 3, Section 17.5: FX Logical Communication Requirements. Rationale Preserving traceability to the Part 1 Conceptual Architecture ensures that each FX logical Communication Endpoint maintains a direct relationship to the conceptual communication constructs from which it is derived. This supports architectural governance, … text/html 2026-07-21T22:29:18+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-5-005?rev=1784672958&do=diff P3-REQ-17-5-005 Return to Requirements Statement Each FX logical Communication Endpoint SHALL identify participating FX logical Nodes or Node Roles, communication roles, carried FX logical information structures, Runtime Plane classification, governance constraints, traceability relationships, and evidence expectations. text/html 2026-07-21T22:29:34+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-5-006?rev=1784672974&do=diff P3-REQ-17-5-006 Return to Requirements Statement The FX Demo Logical Profile SHALL distinguish FX logical Communication Endpoints from DDS Topics, REST resources, RPC methods, Protocol Buffers services, message queues, event streams, files, database handoffs, shared-memory locations, network routes, and deployment artefacts. text/html 2026-07-21T22:29:47+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-5-007?rev=1784672987&do=diff P3-REQ-17-5-007 Return to Requirements Statement The FX Demo Logical Profile SHALL NOT prescribe one communication technology or interaction style. Source Part 3, Section 17.5: FX Logical Communication Requirements. Rationale The FX Demo Logical Profile defines a platform-independent logical architecture and therefore must not mandate a specific communication technology or interaction style. Different deployments may realize the same logical Communication Endpoint using technologies such… text/html 2026-07-21T22:32:28+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-6-001?rev=1784673148&do=diff P3-REQ-17-6-001 Return to Requirements Statement The FX Demo Logical Profile SHALL define the logical information structures for FX. Source Part 3, Section 17.6: FX Logical Information Requirements. Rationale FX logical information structures define the platform-independent information model used throughout the Foreign Exchange Domain. They establish the logical meaning of information exchanged, processed, governed, and retained by FX logical Nodes and FX logical Communication Endpoints … text/html 2026-07-21T22:32:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-6-002?rev=1784673164&do=diff P3-REQ-17-6-002 Return to Requirements Statement The FX Demo Logical Profile SHALL define the following FX logical information structures: FX Transaction CandidateFX Transaction RecordFX Validation ResultFX Semantic AssertionFX Contract StateFX Cash-Flow ObligationFX Policy Decision text/html 2026-07-21T22:32:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-6-003?rev=1784673177&do=diff P3-REQ-17-6-003 Return to Requirements Statement Each FX logical information structure SHALL specialise one or more Part 2 logical information concepts. Source Part 3, Section 17.6: FX Logical Information Requirements. Rationale Specializing the logical information concepts defined in Part 2 preserves the architectural inheritance established by the platform-independent Logical Architecture while allowing the FX Demo Logical Profile to define information structures specific to the Foreig… text/html 2026-07-21T22:33:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-6-004?rev=1784673195&do=diff P3-REQ-17-6-004 Return to Requirements Statement Each FX logical information structure SHALL preserve traceability to Data Structure Definition, Data Structure Instance, Evidence, Traceability, or other applicable Part 1 concepts. Source Part 3, Section 17.6: FX Logical Information Requirements. text/html 2026-07-21T22:33:29+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-6-005?rev=1784673209&do=diff P3-REQ-17-6-005 Return to Requirements Statement Each FX logical information structure SHALL identify its logical purpose, primary Runtime Plane, producing Node or Node Role, consuming Node or Node Role, governance constraints, traceability relationships, and evidence expectations. text/html 2026-07-21T22:33:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-6-006?rev=1784673225&do=diff P3-REQ-17-6-006 Return to Requirements Statement The FX Demo Logical Profile SHALL distinguish FX logical information structures from IDL structures, Protocol Buffers messages, JSON Schema definitions, XML Schema definitions, Avro schemas, OpenAPI schemas, ontology classes, database tables, generated language types, files, wire formats, runtime payloads, and implementation records. text/html 2026-07-21T22:35:48+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-001?rev=1784673348&do=diff P3-REQ-17-7-001 Return to Requirements Statement The FX Demo Logical Profile SHALL define participation in the FX Runtime Plane. Source Part 3, Section 17.7: FX Runtime Plane Requirements. Rationale Participation in the FX Runtime Plane establishes how the logical architectural elements of the FX Demo Logical Profile interact within the Runtime Plane model defined by the Reference Architecture. Defining Runtime Plane participation provides a consistent architectural foundation for organi… text/html 2026-07-21T22:35:58+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-002?rev=1784673358&do=diff P3-REQ-17-7-002 Return to Requirements Statement The FX Demo Logical Profile SHALL use the following FX Runtime Planes: Logical Control PlaneLogical Data PlaneLogical Health and Observability PlaneLogical Policy and Release PlaneLogical Audit and Provenance Plane Source text/html 2026-07-21T22:36:14+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-003?rev=1784673374&do=diff P3-REQ-17-7-003 Return to Requirements Statement The Logical Control Plane SHALL support operational coordination among FX logical Nodes. Source Part 3, Section 17.7: FX Runtime Plane Requirements. Rationale The Logical Control Plane provides the architectural capability for coordinating the behavior of FX logical Nodes. It supports the logical exchange of operational control information, enabling Nodes to coordinate activities, manage operational state, and perform runtime interactions … text/html 2026-07-21T22:36:27+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-004?rev=1784673387&do=diff P3-REQ-17-7-004 Return to Requirements Statement The Logical Data Plane SHALL carry FX domain, analytical, lifecycle, validation, interpretation, and derived information among FX logical Nodes. Source Part 3, Section 17.7: FX Runtime Plane Requirements. Rationale The Logical Data Plane provides the architectural capability for exchanging the logical information required to support Foreign Exchange processing. It enables the movement of domain information, analytical results, lifecycle in… text/html 2026-07-21T22:36:38+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-005?rev=1784673398&do=diff P3-REQ-17-7-005 Return to Requirements Statement The Logical Health and Observability Plane SHALL support observation of FX logical Node operational condition and behaviour. Source Part 3, Section 17.7: FX Runtime Plane Requirements. Rationale The Logical Health and Observability Plane provides the architectural capability for observing the operational condition and behaviour of FX logical Nodes. It supports logical monitoring, operational visibility, status reporting, and health assessm… text/html 2026-07-21T22:36:54+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-006?rev=1784673414&do=diff P3-REQ-17-7-006 Return to Requirements Statement The Logical Policy and Release Plane SHALL support governed access, disclosure, safeguarding, redaction, transformation, marking, obligations, and release of FX information. Source Part 3, Section 17.7: FX Runtime Plane Requirements. text/html 2026-07-21T22:37:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-007?rev=1784673433&do=diff P3-REQ-17-7-007 Return to Requirements Statement The Logical Audit and Provenance Plane SHALL support auditability, provenance, lineage, reconstruction, replay, review, accountability, and defensibility for FX logical processing. Source Part 3, Section 17.7: FX Runtime Plane Requirements. text/html 2026-07-21T22:37:26+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-008?rev=1784673446&do=diff P3-REQ-17-7-008 Return to Requirements Statement The FX Demo Logical Profile SHALL distinguish FX Runtime Planes from DDS domains, DDS topics, DDS partitions, REST resource groups, RPC service groups, message queues, event streams, Kubernetes namespaces, network segments, security zones, deployment environments, and runtime configuration groupings. text/html 2026-07-21T22:37:38+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-009?rev=1784673458&do=diff P3-REQ-17-7-009 Return to Requirements Statement Cross-plane FX logical relationships SHALL preserve the distinct architectural purpose of each FX Runtime Plane involved. Source Part 3, Section 17.7: FX Runtime Plane Requirements. Rationale FX logical relationships frequently span multiple Runtime Planes. While interactions across Runtime Planes are expected, they must not blur or redefine the architectural responsibilities assigned to each plane. Preserving the distinct purpose of every… text/html 2026-07-21T22:56:21+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-001?rev=1784674581&do=diff P3-REQ-17-8-001 Return to Requirements Statement The FX Demo Logical Profile SHALL define an FX Transaction and Contract Lifecycle Model. Source Part 3, Section 17.8: FX Lifecycle Requirements. Rationale The FX Transaction and Contract Lifecycle Model provides the platform-independent architectural description of how FX transactions and contracts progress through their logical lifecycle. Defining this model establishes a consistent architectural foundation for transaction processing, con… text/html 2026-07-21T22:56:47+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-002?rev=1784674607&do=diff P3-REQ-17-8-002 Return to Requirements Statement The FX Transaction and Contract Lifecycle Model SHALL distinguish candidate transaction information, validated transaction information, semantically interpreted transaction information, contract state, computed cash-flow obligations, policy release state, and audit/provenance records. text/html 2026-07-21T22:57:03+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-003?rev=1784674623&do=diff P3-REQ-17-8-003 Return to Requirements Statement FX Transaction Lifecycle States SHALL identify the logical processing condition of FX transaction information during intake, validation, semantic interpretation, contract state processing, cash-flow computation, release evaluation, audit, provenance, replay, and reconstruction. text/html 2026-07-21T22:57:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-004?rev=1784674635&do=diff P3-REQ-17-8-004 Return to Requirements Statement FX Contract State Transitions SHALL identify prior state, target state, triggering information, responsible FX logical Node or Node Role, applicable rule or interpretation context, timestamp, and provenance reference. Source text/html 2026-07-21T22:57:29+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-005?rev=1784674649&do=diff P3-REQ-17-8-005 Return to Requirements Statement Validation-controlled transitions SHALL depend on FX Validation Results. Source Part 3, Section 17.8: FX Lifecycle Requirements. Rationale Validation-controlled transitions ensure that transaction information progresses through the lifecycle only after the required logical validation activities have been completed. Depending upon FX Validation Results preserves architectural consistency by ensuring that lifecycle progression is governed by… text/html 2026-07-21T22:57:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-006?rev=1784674661&do=diff P3-REQ-17-8-006 Return to Requirements Statement Interpretation-controlled transitions SHALL depend on FX Semantic Assertions. Source Part 3, Section 17.8: FX Lifecycle Requirements. Rationale Interpretation-controlled transitions ensure that lifecycle progression depends upon the logical interpretation of transaction information rather than solely upon syntactic validity. By requiring transitions to depend on FX Semantic Assertions, the architecture distinguishes semantic interpretation… text/html 2026-07-21T22:58:00+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-007?rev=1784674680&do=diff P3-REQ-17-8-007 Return to Requirements Statement Cash-flow computation triggers SHALL identify the logical conditions that initiate computation of FX Cash-Flow Obligations. Source Part 3, Section 17.8: FX Lifecycle Requirements. Rationale Cash-flow obligations are produced only when the logical conditions defined by the FX lifecycle have been satisfied. Identifying the logical conditions that initiate cash-flow computation ensures that obligation generation is governed by the architectur… text/html 2026-07-21T22:58:14+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-008?rev=1784674694&do=diff P3-REQ-17-8-008 Return to Requirements Statement Policy and release state considerations SHALL identify the logical conditions that govern external release of FX information. Source Part 3, Section 17.8: FX Lifecycle Requirements. Rationale Not all FX information is suitable for external release at every point in the transaction lifecycle. Policy and release state considerations define the logical conditions under which information may be disclosed outside the FX processing environment w… text/html 2026-07-21T22:58:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-009?rev=1784674705&do=diff P3-REQ-17-8-009 Return to Requirements Statement Audit and provenance state records SHALL preserve the logical history of FX lifecycle processing. Source Part 3, Section 17.8: FX Lifecycle Requirements. Rationale Audit and provenance state records provide the architectural evidence required to reconstruct and understand the logical progression of FX transaction and contract processing. Preserving the logical history of lifecycle activities supports auditability, traceability, accountabil… text/html 2026-07-21T22:58:36+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-010?rev=1784674716&do=diff P3-REQ-17-8-010 Return to Requirements Statement The FX Transaction and Contract Lifecycle Model SHALL NOT prescribe a state-machine implementation, workflow engine, database status field, event store, rules engine, orchestration mechanism, API, DDS topic, REST resource, or runtime persistence mechanism. text/html 2026-07-21T23:00:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-001?rev=1784674816&do=diff P3-REQ-17-9-001 Return to Requirements Statement The FX Demo Logical Profile SHALL define logical interaction patterns for FX. Source Part 3, Section 17.9: FX Logical Interaction Requirements. Rationale Logical interaction patterns define the platform-independent exchanges of information and responsibilities among FX logical Nodes. They provide the architectural description of how logical processing activities are coordinated while remaining independent of communication technologies, dep… text/html 2026-07-21T23:00:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-002?rev=1784674825&do=diff P3-REQ-17-9-002 Return to Requirements Statement The FX Demo Logical Profile SHALL define the following FX logical interaction patterns: Register FX Logical NodeReport FX Node StatusIntake FX Transaction CandidateValidate FX Transaction CandidateInterpret FX Transaction Semantics text/html 2026-07-21T23:00:40+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-003?rev=1784674840&do=diff P3-REQ-17-9-003 Return to Requirements Statement Each FX logical interaction pattern SHALL identify participating FX logical Nodes or Node Roles. Source Part 3, Section 17.9: FX Logical Interaction Requirements. Rationale Every logical interaction occurs between one or more FX logical Nodes operating in defined Node Roles. Identifying the participating Nodes or Node Roles establishes architectural accountability, clarifies interaction responsibilities, supports interoperability, and enab… text/html 2026-07-21T23:00:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-004?rev=1784674857&do=diff P3-REQ-17-9-004 Return to Requirements Statement Each FX logical interaction pattern SHALL identify the FX logical Communication Endpoints involved. Source Part 3, Section 17.9: FX Logical Interaction Requirements. Rationale Logical Communication Endpoints define the architectural points through which FX logical Nodes exchange information. Identifying the participating Communication Endpoints for every logical interaction clarifies architectural interfaces, supports interoperability, ena… text/html 2026-07-21T23:01:06+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-005?rev=1784674866&do=diff P3-REQ-17-9-005 Return to Requirements Statement Each FX logical interaction pattern SHALL identify the FX logical information structures exchanged, recorded, or referenced. Source Part 3, Section 17.9: FX Logical Interaction Requirements. Rationale Logical interaction patterns are defined not only by the participating architectural elements but also by the logical information that they exchange, record, or reference. Identifying these logical information structures preserves semantic co… text/html 2026-07-21T23:01:21+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-006?rev=1784674881&do=diff P3-REQ-17-9-006 Return to Requirements Statement Each FX logical interaction pattern SHALL identify the FX Runtime Plane or FX Runtime Planes involved. Source Part 3, Section 17.9: FX Logical Interaction Requirements. Rationale Every logical interaction occurs within one or more FX Runtime Planes that define its architectural purpose. Identifying the Runtime Plane or Runtime Planes associated with each interaction preserves separation of concerns, clarifies architectural responsibilities… text/html 2026-07-21T23:01:34+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-007?rev=1784674894&do=diff P3-REQ-17-9-007 Return to Requirements Statement Each FX logical interaction pattern SHALL identify governance constraints. Source Part 3, Section 17.9: FX Logical Interaction Requirements. Rationale Every FX logical interaction is subject to architectural governance that determines how the interaction is authorized, controlled, interpreted, and managed throughout its lifecycle. Identifying governance constraints for each interaction pattern ensures that architectural responsibilities ar… text/html 2026-07-21T23:01:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-008?rev=1784674905&do=diff P3-REQ-17-9-008 Return to Requirements Statement Each FX logical interaction pattern SHALL identify traceability expectations. Source Part 3, Section 17.9: FX Logical Interaction Requirements. Rationale Traceability enables every FX logical interaction to be related to the architectural concepts, logical information structures, Runtime Planes, lifecycle states, governance decisions, and evidence that support it. Identifying traceability expectations for each interaction pattern preserves… text/html 2026-07-21T23:01:58+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-009?rev=1784674918&do=diff P3-REQ-17-9-009 Return to Requirements Statement Each FX logical interaction pattern SHALL identify evidence expectations for later deployment, testability, and evidence planning. Source Part 3, Section 17.9: FX Logical Interaction Requirements. Rationale Evidence planning is an architectural concern that begins during logical design rather than during implementation. Identifying evidence expectations for every logical interaction pattern ensures that future implementations can support v… text/html 2026-07-21T23:02:38+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-9-010?rev=1784674958&do=diff P3-REQ-17-9-010 Return to Requirements Statement FX logical interaction patterns SHALL remain independent of DDS, REST, RPC, Protocol Buffers, message queues, event streams, file exchange, shared services, databases, logs, deployment mechanisms, runtime scripts, and evidence-capture tools. text/html 2026-07-21T23:04:08+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-10-001?rev=1784675048&do=diff P3-REQ-17-10-001 Return to Requirements Statement The FX Demo Logical Profile SHALL define an FX Logical Governance Model. Source Part 3, Section 17.10: FX Logical Governance Requirements. Rationale The FX Logical Governance Model establishes the platform-independent architectural framework for governing the creation, maintenance, evolution, and use of FX logical architecture elements. It provides the architectural basis for managing ownership, compatibility, change, admission, policy, a… text/html 2026-07-21T23:04:19+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-10-002?rev=1784675059&do=diff P3-REQ-17-10-002 Return to Requirements Statement The FX Logical Governance Model SHALL define: FX Logical Ownership of DefinitionsFX Logical VersioningFX Logical CompatibilityFX Logical Change ControlFX Logical Admission RulesFX Logical Policy Constraints Source Part 3, Section 17.10: FX Logical Governance Requirements. text/html 2026-07-21T23:04:32+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-10-003?rev=1784675072&do=diff P3-REQ-17-10-003 Return to Requirements Statement FX Logical Ownership of Definitions SHALL identify responsibility for defining, maintaining, approving, and reviewing FX logical definitions. Source Part 3, Section 17.10: FX Logical Governance Requirements. Rationale text/html 2026-07-21T23:04:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-10-004?rev=1784675085&do=diff P3-REQ-17-10-004 Return to Requirements Statement FX Logical Versioning SHALL identify versions of FX logical definitions, relationships, constraints, and profile elements. Source Part 3, Section 17.10: FX Logical Governance Requirements. Rationale Logical versioning enables the architectural evolution of the FX Demo Logical Profile while preserving traceability, governance, and interoperability. Identifying versions of logical definitions, relationships, constraints, and profile element… text/html 2026-07-21T23:04:58+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-10-005?rev=1784675098&do=diff P3-REQ-17-10-005 Return to Requirements Statement FX Logical Compatibility SHALL identify whether FX logical elements work together without loss of meaning, structure, traceability, governance, or evidence expectations. Source Part 3, Section 17.10: FX Logical Governance Requirements. text/html 2026-07-21T23:05:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-10-006?rev=1784675113&do=diff P3-REQ-17-10-006 Return to Requirements Statement FX Logical Change Control SHALL govern changes to FX logical definitions, relationships, responsibilities, constraints, lifecycle states, and interaction patterns. Source Part 3, Section 17.10: FX Logical Governance Requirements. text/html 2026-07-21T23:05:30+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-10-007?rev=1784675130&do=diff P3-REQ-17-10-007 Return to Requirements Statement FX Logical Admission Rules SHALL define conditions governing participation of FX logical elements in the FX Demo Logical Profile. Source Part 3, Section 17.10: FX Logical Governance Requirements. Rationale Not every logical element is automatically eligible for inclusion within the FX Demo Logical Profile. Logical Admission Rules establish the architectural criteria that govern whether logical definitions, relationships, interaction patte… text/html 2026-07-21T23:05:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-10-008?rev=1784675141&do=diff P3-REQ-17-10-008 Return to Requirements Statement FX Logical Policy Constraints SHALL define platform-independent restrictions, conditions, obligations, or decision criteria governing FX logical interaction or FX information movement. Source Part 3, Section 17.10: FX Logical Governance Requirements. text/html 2026-07-21T23:05:54+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-10-009?rev=1784675154&do=diff P3-REQ-17-10-009 Return to Requirements Statement The FX Logical Governance Model SHALL remain independent of repositories, workflow tools, requirements-management systems, policy engines, rules engines, access-control products, ticketing systems, approval systems, configuration services, runtime registries, and deployment mechanisms. text/html 2026-07-21T23:07:28+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-001?rev=1784675248&do=diff P3-REQ-17-11-001 Return to Requirements Statement The FX Demo Logical Profile SHALL define an FX Demo Logical Traceability Model. Source Part 3, Section 17.11: FX Logical Traceability Requirements. Rationale The FX Demo Logical Traceability Model establishes the architectural framework for relating conceptual architecture, logical architecture, and future implementation artefacts. By defining traceability as a logical architectural concern, the FX Demo Logical Profile preserves consisten… text/html 2026-07-21T23:07:39+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-002?rev=1784675259&do=diff P3-REQ-17-11-002 Return to Requirements Statement The FX Demo Logical Traceability Model SHALL define traceability from Part 1 conceptual elements to FX logical profile elements. Source Part 3, Section 17.11: FX Logical Traceability Requirements. Rationale The FX Demo Logical Profile is derived from the conceptual architecture established in Part 1. Traceability from conceptual elements to logical profile elements preserves architectural intent, demonstrates that conceptual concerns have… text/html 2026-07-21T23:07:53+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-003?rev=1784675273&do=diff P3-REQ-17-11-003 Return to Requirements Statement The FX Demo Logical Traceability Model SHALL define traceability from Part 2 logical elements to FX logical profile elements. Source Part 3, Section 17.11: FX Logical Traceability Requirements. Rationale The FX Demo Logical Profile specializes the platform-independent logical architecture defined in Part 2. Traceability from Part 2 logical elements to FX logical profile elements demonstrates how the FX profile derives from the broader log… text/html 2026-07-21T23:08:17+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-004?rev=1784675297&do=diff P3-REQ-17-11-004 Return to Requirements Statement The FX Demo Logical Traceability Model SHALL define: FX Node TraceabilityFX Endpoint TraceabilityFX Information Structure TraceabilityFX Runtime Plane TraceabilityFX Interaction TraceabilityFX Evidence Traceability Source text/html 2026-07-21T23:08:27+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-005?rev=1784675307&do=diff P3-REQ-17-11-005 Return to Requirements Statement FX Node Traceability SHALL relate an FX logical Node to inherited logical sources, conceptual sources, Node Roles, responsibilities, endpoints, Runtime Plane participation, interactions, governance relationships, and evidence expectations. text/html 2026-07-21T23:08:40+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-006?rev=1784675320&do=diff P3-REQ-17-11-006 Return to Requirements Statement FX Endpoint Traceability SHALL relate an FX logical Communication Endpoint to inherited logical sources, conceptual sources, participating Nodes, Communication Roles, information structures, Runtime Plane classifications, governance constraints, and evidence expectations. text/html 2026-07-21T23:09:20+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-007?rev=1784675360&do=diff P3-REQ-17-11-007 Return to Requirements Statement FX Information Structure Traceability SHALL relate FX logical information structures to inherited logical sources, conceptual sources, Nodes, endpoints, interactions, Runtime Planes, governance constraints, lineage, and evidence expectations. text/html 2026-07-21T23:09:32+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-008?rev=1784675372&do=diff P3-REQ-17-11-008 Return to Requirements Statement FX Runtime Plane Traceability SHALL relate FX logical interactions and information exchanges to their FX Runtime Plane classification. Source Part 3, Section 17.11: FX Logical Traceability Requirements. Rationale Runtime Plane Traceability identifies the Runtime Plane classification associated with every logical interaction and information exchange. This relationship preserves architectural intent, enables consistent interpretation of run… text/html 2026-07-21T23:09:53+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-009?rev=1784675393&do=diff P3-REQ-17-11-009 Return to Requirements Statement FX Interaction Traceability SHALL relate FX logical interaction patterns to inherited Part 2 interaction patterns, Nodes, roles, endpoints, information structures, Runtime Planes, governance constraints, and evidence expectations. text/html 2026-07-21T23:10:18+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-010?rev=1784675418&do=diff P3-REQ-17-11-010 Return to Requirements Statement FX Evidence Traceability SHALL relate FX logical profile elements and interactions to evidence expectations for later implementation, deployment, testing, and review. Source Part 3, Section 17.11: FX Logical Traceability Requirements. text/html 2026-07-21T23:10:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-011?rev=1784675433&do=diff P3-REQ-17-11-011 Return to Requirements Statement FX logical traceability SHALL support forward review from the conceptual concern to the FX logical profile element. Source Part 3, Section 17.11: FX Logical Traceability Requirements. Rationale Forward traceability enables reviewers to begin with a conceptual concern defined in the architecture and determine how that concern is realized within the FX Demo Logical Profile. This capability supports architectural validation, impact analysis,… text/html 2026-07-21T23:10:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-012?rev=1784675445&do=diff P3-REQ-17-11-012 Return to Requirements Statement FX logical traceability SHALL support backward review from the FX logical profile element to the Part 1 conceptual source and the Part 2 logical source. Source Part 3, Section 17.11: FX Logical Traceability Requirements. text/html 2026-07-21T23:12:22+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-11-013?rev=1784675542&do=diff P3-REQ-17-11-013 Return to Requirements Statement FX logical traceability SHALL support later traceability from FX logical profile elements to implementation artefacts, deployment artefacts, test scenarios, runtime observations, audit records, provenance records, and evidence packages. text/html 2026-07-21T23:13:23+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-12-001?rev=1784675603&do=diff P3-REQ-17-12-001 Return to Requirements Statement The FX Demo Logical Profile SHALL remain platform-independent. Source Part 3, Section 17.12: Implementation Boundary Requirements. Rationale The FX Demo Logical Profile defines platform-independent logical architecture rather than implementation-specific technologies. Maintaining platform independence ensures that the logical architecture can be realized using multiple technologies, middleware products, deployment environments, and operat… text/html 2026-07-21T23:13:34+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-12-002?rev=1784675614&do=diff P3-REQ-17-12-002 Return to Requirements Statement An Implementation Profile / PSM SHALL preserve the FX Demo Logical Profile defined in this part. Source Part 3, Section 17.12: Implementation Boundary Requirements. Rationale An Implementation Profile or Platform-Specific Model realizes the logical architecture rather than replacing or modifying it. Preserving the FX Demo Logical Profile ensures that all implementation decisions remain faithful to the platform-independent architecture whi… text/html 2026-07-21T23:13:56+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-12-003?rev=1784675636&do=diff P3-REQ-17-12-003 Return to Requirements Statement An Implementation Profile / PSM SHALL map FX logical elements to selected implementation artefacts without redefining them. Source Part 3, Section 17.12: Implementation Boundary Requirements. Rationale The purpose of an Implementation Profile or Platform-Specific Model is to realize the logical architecture using implementation-specific technologies. This realization is achieved by mapping logical elements to implementation artefacts rath… text/html 2026-07-21T23:14:07+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-12-004?rev=1784675647&do=diff P3-REQ-17-12-004 Return to Requirements Statement An Implementation Profile / PSM SHALL preserve traceability from implementation artefacts to the FX logical elements they realise. Source Part 3, Section 17.12: Implementation Boundary Requirements. Rationale Implementation artefacts derive their architectural meaning from the FX Demo Logical Profile. Preserving traceability between implementation artefacts and the logical elements they realize enables architectural review, impact analysi… text/html 2026-07-21T23:14:24+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-12-005?rev=1784675664&do=diff P3-REQ-17-12-005 Return to Requirements Statement An Implementation Profile / PSM SHALL NOT use a technology selection to redefine an FX logical Node, FX logical Node Role, FX logical Communication Endpoint, FX logical information structure, FX Runtime Plane, FX logical interaction pattern, FX logical governance relationship, or FX logical traceability relationship. text/html 2026-07-21T23:14:49+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-12-006?rev=1784675689&do=diff P3-REQ-17-12-006 Return to Requirements Statement A Deployment, Testability, and Evidence Plan SHALL preserve traceability to the FX Demo Logical Profile defined in this part. Source Part 3, Section 17.12: Implementation Boundary Requirements. Rationale Deployment, Testability, and Evidence Plans describe how an implementation is deployed, verified, observed, and evaluated. These plans derive their architectural meaning from the FX Demo Logical Profile and therefore must preserve traceab… text/html 2026-07-21T23:15:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/p3-req-17-12-007?rev=1784675711&do=diff P3-REQ-17-12-007 Return to Requirements Statement A Deployment, Testability, and Evidence Plan SHALL NOT redefine FX logical elements through deployment topology, runtime packaging, test tooling, monitoring tooling, evidence-capture tooling, repository structure, or runtime scripts. text/html 2026-07-11T19:59:50+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-d-requirements/part-03/start?rev=1783799990&do=diff Part 3 Requirements Return to Annex D: Requirements This page identifies the canonical requirement records for Part 3: FX Demo Logical Profile. part-03 index ---------- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.