DIDO Solutions technical documentation and FX Demo knowledge base https://wiki.didosolutions.com/ 2026-08-23T00:07:08+00:00 https://wiki.didosolutions.com/ https://wiki.didosolutions.com/_media/wiki/logo.png text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/latency?rev=1784403224&do=diff Latency Go up to Terms and Definitions Discussion Latency represents the delay experienced by traffic as it moves through a network path. In the context of internet_qos, Latency reflects forwarding delay, queuing delay, transmission delay, propagation delay, and processing delay along the path. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/ledger?rev=1784403224&do=diff Ledger Go up to Terms and Definitions Discussion A Ledger is a record of entries documenting accounts, balances, obligations, transfers, settlements, or other value-related changes. In a Financial System, a Ledger supports accounting, settlement, reconciliation, accountability, and review. A Ledger may appear in centralised, distributed, or replicated forms, depending on the implementation context. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/legal_and_regulatory_defensibility?rev=1784403224&do=diff Legal and Regulatory Defensibility Go up to Terms and Definitions Discussion Legal and regulatory defensibility concerns the ability to support an outcome, decision, interpretation, or system behavior during authorized legal, regulatory, supervisory, administrative, or audit examination. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/lifecycle?rev=1784403224&do=diff Lifecycle Go up to Terms and Definitions Discussion A lifecycle describes how a thing progresses through states over time. A lifecycle identifies the states a thing enters, the events that cause state changes, the transitions between states, and the conditions that govern those transitions. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/lifecycle_stage?rev=1784403224&do=diff Lifecycle Stage Go up to Terms and Definitions Discussion A Lifecycle Stage is a defined and distinguishable part of the lifecycle of a system, artifact, environment, service, or process. Each Lifecycle Stage has an identified purpose, expected inputs, activities, outputs, responsibilities, controls, and transition conditions. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_acknowledgment?rev=1784403224&do=diff Logical Acknowledgement Return to L Terms Discussion A Logical Acknowledgement represents a Logical Data Structure Instance that reports receipt, acceptance, rejection, completion, failure, or other outcome for a command, request, message, event, or processing step. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_admission_rules?rev=1784403224&do=diff Logical Admission Rules Return to L Terms Discussion Logical Admission Rules define the conditions under which a Logical Node, Logical Communication Endpoint, Logical Data Structure Definition, Logical Interaction Pattern, or domain-specific logical extension participates in the logical architecture. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_assertion?rev=1784403224&do=diff Logical Assertion Return to L Terms Discussion A Logical Assertion represents a Logical Data Structure Instance that states a conclusion, derived fact, validation result, interpretation result, analytical result, policy decision, or other claim produced by a Logical Node. text/html 2026-08-04T14:09:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_audit_and_provenance_plane?rev=1785852565&do=diff Logical Audit and Provenance Plane Go up to Terms and Definitions Discussion The Logical Audit and Provenance Plane supports reconstruction, accountability, lineage, review, replay, recovery, auditability, and defensibility for FX logical processing. Logical Audit and Provenance Plane interactions record or relate what happened, when it happened, which FX logical text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_change_control?rev=1784403224&do=diff Logical Change Control Return to L Terms Discussion Logical Change Control governs changes to logical definitions, relationships, responsibilities, constraints, and interaction patterns. Logical Change Control supports review before a change affects other logical elements, domain profiles, implementation profiles, deployment profiles, testability plans, or evidence expectations. It identifies the changed element, the reason for the change, the affected logical relationships, the compatibilit… text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_command?rev=1784403224&do=diff Logical Command Return to L Terms Discussion A Logical Command represents a Logical Data Structure Instance that expresses an intended action by a Logical Node or Node Role. A Logical Command differs from a Logical Event. A Logical Command requests or directs action. A Logical Event reports the occurrence or result. Logical Commands primarily support Control Plane interactions, but a domain profile identifies any domain-specific command-handling requirements. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_communication_endpoint?rev=1784403224&do=diff Logical Communication Endpoint Return to L Terms Discussion A Logical Communication Endpoint identifies a platform-independent point of information exchange among Logical Nodes. A Logical Communication Endpoint provides a logical boundary for communication. It identifies the exchange point, the participating Logical Nodes, the communication roles, the Logical Data Structure Definition governing the exchanged information, the Logical Runtime Plane, and the traceability or evidence expectation… text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_compatibility?rev=1784403224&do=diff Logical Compatibility Return to L Terms Discussion Logical Compatibility identifies whether two or more logical elements work together without loss of meaning, structure, traceability, governance, or evidence expectations. Logical Compatibility applies to Logical Nodes, Logical Communication Endpoints, Logical Data Structure Definitions, Logical Data Structure Instances, Logical Runtime Planes, Logical Interaction Patterns, and Logical Policy Constraints. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_control_plane?rev=1784403224&do=diff Logical Control Plane Return to L Terms Discussion The Logical Control Plane supports operational coordination among Logical Nodes. Logical Control Plane interactions include registration, capability advertisement, command exchange, command acknowledgement, configuration coordination, schema and model version coordination, retry coordination, recovery coordination, replay coordination, and operational state management. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_data_plane?rev=1784403224&do=diff Logical Data Plane Return to L Terms Discussion The Logical Data Plane carries domain, financial, analytical, lifecycle, and derived information among Logical Nodes. Logical Data Plane interactions include publication, subscription, exchange, validation, enrichment, interpretation, assertion, transformation, and consumption of domain information. The Logical Data Plane supports information representing events, observations, assertions, computations, state changes, and domain results. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_data_structure_definition?rev=1784403224&do=diff Logical Data Structure Definition Return to L Terms Discussion A Logical Data Structure Definition describes the structure, meaning, and constraints of an information class at the platform-independent logical level. A Logical Data Structure Definition identifies the fields, relationships, permitted values, constraints, semantic references, lifecycle values, provenance references, identity requirements, and validation expectations that govern Logical Data Structure Instances. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_data_structure_instance?rev=1784403224&do=diff Logical Data Structure Instance Return to L Terms Discussion A Logical Data Structure Instance represents a populated occurrence of a Logical Data Structure Definition. A Logical Data Structure Instance contains values that conform to its governing Logical Data Structure Definition. Logical Nodes exchange, record, interpret, validate, trace, or evidence those values through Logical Communication Endpoints and logical interaction patterns. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_data_structure_traceability?rev=1784403224&do=diff Logical Data Structure Traceability Return to L Terms Discussion Logical Data Structure Traceability relates a Logical Data Structure Definition or Logical Data Structure Instance to its conceptual source, semantic context, producing Logical Nodes, consuming Logical Nodes, endpoints, interactions, Runtime Planes, governance constraints, lineage, and evidence expectations. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_endpoint_traceability?rev=1784403224&do=diff Logical Endpoint Traceability Return to L Terms Discussion Logical Endpoint Traceability relates a Logical Communication Endpoint to its participating Logical Nodes, Communication Roles, Logical Data Structure Definitions, Runtime Plane classification, governance constraints, and evidence expectations. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_event?rev=1784403224&do=diff Logical Event Return to L Terms Discussion A Logical Event represents a Logical Data Structure Instance that reports an occurrence, observation, state change, decision, derived result, or other fact relevant to the architecture. A Logical Event reports that something occurred or that a Logical Node observed, produced, derived, decided, or changed something. It does not instruct another Node to act. Commands express intended action; events report occurrence or result. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_evidence_traceability?rev=1784403224&do=diff Logical Evidence Traceability Return to L Terms Discussion Logical Evidence Traceability relates logical elements and logical interactions to the evidence expectations that later implementation, deployment, testability, and evidence plans satisfy. Logical Evidence Traceability does not create runtime evidence in Part 2. It identifies what later parts need to evidence. It connects claims about logical behavior to the logical Nodes, endpoints, information structures, Runtime Planes, interactio… text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_health_and_observability_plane?rev=1784403224&do=diff Logical Health and Observability Plane Return to L Terms Discussion The Logical Health and Observability Plane supports logical operational awareness across the distributed Logical Node network. Logical Health and Observability Plane interactions report or expose Logical Node state, lifecycle state, heartbeat, availability, degradation, failure, warning conditions, recovery progress, runtime metrics, and other operational observations. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_information_lineage?rev=1784403224&do=diff Logical Information Lineage Return to L Terms Discussion Logical Information Lineage describes the relationships among Logical Data Structure Instances as Logical Nodes exchange, transform, validate, interpret, assert, persist, replay, release, or evidence information. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_interaction_traceability?rev=1784403224&do=diff Logical Interaction Traceability Return to L Terms Discussion Logical Interaction Traceability relates a logical interaction pattern to its participating Logical Nodes, Communication Roles, endpoints, information structures, Runtime Planes, governance constraints, and evidence expectations. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_message?rev=1784403224&do=diff Logical Message Return to L Terms Discussion A Logical Message represents a Logical Data Structure Instance exchanged through a Logical Communication Endpoint. The Logical Message concept focuses on communication. It identifies information moving from one logical participant to another, whether the implementation later uses publish/subscribe, request/response, RPC, REST, message queues, event streams, files, shared services, or another exchange mechanism. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_model?rev=1784403224&do=diff Logical Model (LM) Return to Terms and Definitions Discussion A logical model describes a system from a selected architectural viewpoint without defining implementation artifacts. A system architecture contains multiple logical models when different architectural concerns require separate treatment. These concerns include information structure, persistence, messaging, service behavior, user interaction, governance, policy control, security, evidence, audit, and logging. text/html 2026-08-04T14:09:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_node?rev=1785852565&do=diff Logical Node Return to L Terms Discussion: A Logical Node identifies a platform-independent participant in the distributed logical architecture. It provides a logical point of responsibility for communication, role assignment, governance, Traceability, observability, auditability, and expectations for text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_node_boundary?rev=1784403224&do=diff Logical Node Boundary Return to L Terms Discussion Logical Node Boundary identifies what the Logical Architecture treats as inside or outside a Logical Node for purposes of responsibility, interaction, traceability, and review. A Logical Node Boundary separates the Logical Node from other Logical Nodes, external participants, Communication Endpoints, and implementation artifacts. It helps reviewers understand which responsibilities belong to the Logical Node and which interactions cross the … text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_node_collaboration?rev=1784403224&do=diff Logical Node Collaboration Return to L Terms Discussion Logical Node Collaboration describes how two or more Logical Nodes work together through explicit logical Communication Endpoints and logical interaction patterns. Logical Node Collaboration supports distributed operation. Examples of collaboration include publishing information, subscribing to information, issuing commands, acknowledging commands, requesting decisions, responding to requests, recording provenance, and producing evidenc… text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_node_identity?rev=1784403224&do=diff Logical Node Identity Return to Terms and Definitions Discussion Logical Node Identity uniquely identifies a Logical Node within the Logical Architecture/PIM. It allows logical interactions, responsibilities, events, records, observations, commands, audit entries, provenance entries, and evidence expectations to be used to identify the Logical Node involved. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_node_lifecycle_state?rev=1784403224&do=diff Logical Node Lifecycle State Return to L Terms Discussion Logical Node Lifecycle State describes the logical operational condition of a Logical Node as seen by the architecture. Logical lifecycle states support operational coordination, monitoring, recovery, replay, evidence, and review. The Logical Architecture uses those states to describe the Node condition without prescribing the implementation mechanism for reporting or storing the state. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_node_responsibility?rev=1784403224&do=diff Logical Node Responsibility Return to L Terms Discussion Logical Node Responsibility describes the obligation, function, or accountability associated with a Logical Node or Logical Node Role. Logical Node Roles identify categories of responsibility. Logical Node Responsibilities describe the specific responsibilities that a Logical Node carries within the logical architecture. Examples of responsibilities include producing, consuming, and validating information; preserving state; recording p… text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_node_role?rev=1784403224&do=diff Logical Node Role Return to L Terms Discussion A Logical Node Role identifies a platform-independent responsibility assigned to, or performed by, a Logical Node. Logical Node Roles allow the architecture to describe what a Logical Node does without tying the responsibility to any specific technology, process, service, container, pod, or deployment unit. A Logical Node performs one or more Logical Node Roles. The Logical Architecture assigns the same Logical Node Role to multiple Logical Node… text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_node_traceability?rev=1784403224&do=diff Logical Node Traceability Return to L Terms Discussion Logical Node Traceability relates a Logical Node to its conceptual source, Logical Node Identity, Logical Node Roles, Logical Node Responsibilities, Logical Communication Endpoints, Runtime Plane participation, interactions, governance relationships, and evidence expectations. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_ownership_of_definitions?rev=1784403224&do=diff Logical Ownership of Definitions Return to L Terms Discussion Logical Ownership of Definitions identifies responsibility for defining, maintaining, approving, and reviewing logical definitions. Logical definitions include Logical Nodes, Logical Node Roles, Logical Communication Endpoints, Logical Data Structure Definitions, Logical Runtime Planes, Logical Interaction Patterns, Logical Policy Constraints, and Logical Traceability Relationships. text/html 2026-08-04T14:09:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_policy_and_release_plane?rev=1785852565&do=diff Logical Policy and Release Plane Go up to Terms and Definitions Discussion The Logical Policy and Release Plane supports governed access, disclosure, safeguarding, redaction, transformation, marking, obligations, and release of FX information. Logical Policy and Release Plane interactions separate internal FX information distribution from authorized external disclosure. They identify how FX logical text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_policy_constraints?rev=1784403224&do=diff Logical Policy Constraints Return to L Terms Discussion Logical Policy Constraints define platform-independent restrictions, conditions, obligations, or decision criteria that govern logical interactions and information movement. Logical Policy Constraints apply to access, disclosure, safeguarding, release, redaction, transformation, marking, retention, replay, audit, provenance, and expectations for evidence. They control what information a Logical Node exchanges, to whom, for what purpose,… text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_record?rev=1784403224&do=diff Logical Record Return to L Terms Discussion A Logical Record represents a Logical Data Structure Instance preserved for continuity, review, audit, provenance, replay, reconstruction, or evidence. Logical Records support data at rest at the logical level without prescribing a database, file system, object store, ledger, log, archive, or persistence technology. The Logical Architecture identifies what information the system preserves and why; later implementation and deployment profiles select… text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_runtime_plane_traceability?rev=1784403224&do=diff Logical Runtime Plane Traceability Return to L Terms Discussion Logical Runtime Plane Traceability relates a logical interaction to the Runtime Plane that frames its architectural purpose. Logical Runtime Plane Traceability helps reviewers distinguish control, data, health and observability, policy, release, and audit and provenance concerns. It also supports cross-plane review by identifying when one plane affects, constrains, or produces information for another plane. text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/logical_versioning?rev=1784403224&do=diff Logical Versioning Return to L Terms Discussion Logical Versioning identifies versions of logical definitions, logical relationships, and logical constraints. Logical Versioning supports controlled evolution. It allows authors and reviewers to distinguish one version of a Logical Data Structure Definition, Logical Communication Endpoint, Logical Interaction Pattern, Logical Node Role, or logical policy constraint from another. text/html 2026-07-12T18:17:49+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/l/start?rev=1783880269&do=diff L Return to Terms and Definitions * Note: You can add new terms beginning with L Add New Term Prompt ---------- List of Words * Latency * Ledger * Legal and Regulatory Defensibility * Lifecycle * Lifecycle Stage * Logical Acknowledgement * Logical Admission Rules * Logical Assertion * Logical Audit and Provenance Plane * Logical Change Control * Logical Command * Logical Communication Endpoint * Logical Compatibility * Logical Control Plane * Logical Data Plane * Logical Da…