DIDO Solutions technical documentation and FX Demo knowledge base https://wiki.didosolutions.com/ 2026-08-22T20:33:55+00:00 https://wiki.didosolutions.com/ https://wiki.didosolutions.com/_media/wiki/logo.png text/html 2026-07-20T08:10:14+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/package?rev=1784535014&do=diff Package Go to Terms and Definitions Discussion A Package is a composite Artifact assembled and distributed as an identifiable unit. A Package may contain one or more Artifacts together with metadata needed to identify, verify, install, load, configure, or use the Package. A Package commonly has: text/html 2026-07-11T18:15:00+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/packet_loss?rev=1783793700&do=diff Packet Loss Go up to Terms and Definitions Discussion Packet Loss occurs when packets fail to reach the intended network destination or measurement point. In the context of internet_qos, Packet Loss results from congestion, queue overflow, policing, transmission errors, routing failures, device failures, or deliberate discard policies. text/html 2026-08-04T14:09:24+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/part_1_concept_to_fx_logical_profile_element?rev=1785852564&do=diff Part 1 Concept to FX Logical Profile Element Return to Terms and Definitions Discussion Part 1 Concept to FX Logical Profile Element traceability connects a conceptual element to the FX logical profile element that specializes, refines, constrains, or relates it. This Traceability relationship preserves conceptual meaning as the architecture moves from a conceptual foundation to a domain-specific logical profile. It shows how the FX Demo Logical Profile builds on Part 1 without redefining it… 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/p/part_1_concept_to_part_2_logical_element?rev=1784403224&do=diff Part 1 Concept to Part 2 Logical Element Return to P Terms Discussion Part 1 Concept to Part 2 Logical Element traceability connects a conceptual element to the logical element that specializes, refines, constrains, or relates it. This traceability relationship preserves conceptual meaning as the architecture moves from the conceptual layer to the logical layer. It shows how a Part 2 logical element builds on Part 1 without redefining Part 1. text/html 2026-08-04T14:09:24+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/part_2_logical_element_to_fx_logical_profile_element?rev=1785852564&do=diff Part 1 Concept to FX Logical Profile Element Return to Terms and Definitions Discussion Part 1 Concept to FX Logical Profile Element traceability connects a conceptual element to the FX logical profile element that specializes, refines, constrains, or relates it. This Traceability relationship preserves conceptual meaning as the architecture moves from a conceptual foundation to a domain-specific logical profile. It shows how the FX Demo Logical Profile builds on Part 1 without redefining it… 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/p/pdf?rev=1784403224&do=diff Portable Document Format (PDF) Go up to Terms and Definitions Discussion Portable Document Format (PDF) provides a digital format for representing electronic documents independently of the environment in which the documents are created, viewed, or printed. ISO 32000-1 defines PDF as a digital format for representing electronic documents that supports exchange and viewing independent of the creation, viewing, or printing environments. :contentReference[oaicite:0]{index=0} 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/p/pedigree?rev=1785852565&do=diff Pedigree Go up to Terms and Definitions Discussion Pedigree represents information about the lineage, custody, ownership, authority, qualification, or history of an entity, participant, Node, record, model, rule, evidence item, or governed artifact. In the FX Demo Reference Architecture, Pedigree supports trust assessment, qualification, governance review, evidence assessment, source evaluation, model governance, and accountability. text/html 2026-07-11T18:15:03+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/performance?rev=1783793703&do=diff Performance Return to Terms and Definitions Discussion Performance refers to the ability of a Qualified Node or governed function to meet defined timing, throughput, latency, capacity, and service-level expectations. In the Governed Node Service Market, Performance supports timely governed processing, provider comparison, service-level review, Competitive Substitution, and operational planning. text/html 2026-08-06T16:07:58+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/performance_efficiency?rev=1786032478&do=diff Performance Efficiency Go up to Terms and Definitions Discussion Performance Efficiency is a Quality Characteristic concerning performance relative to the resources used under specified conditions. Performance Efficiency can apply to: A Candidate SolutionA Distributed SystemA NodeA Node SetA serviceA software componentA hardware componentAn Execution FacilityAn Operational Resource 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/p/pipeline_workspace?rev=1784403224&do=diff Pipeline Workspace Go up to Terms and Definitions Discussion A Pipeline Workspace is the controlled file and execution context in which a build or deployment pipeline retrieves inputs, composes baselines, performs lifecycle operations, and records intermediate and final artifacts. text/html 2026-07-13T18:04:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/platform?rev=1783965897&do=diff Platform Go up to Terms and Definitions Discussion A Platform provides a managed combination of infrastructure, software, services, interfaces, policies, controls, and operational capabilities that supports the execution, deployment, or management of applications and workloads. text/html 2026-07-16T16:36:38+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/platform_deployment?rev=1784219798&do=diff Platform Deployment Go to Terms and Definitions Discussion Platform Deployment establishes an operational platform within a target Infrastructure Environment. The deployed platform may comprise: Operating-system componentsRuntime componentsMiddlewareContainer servicesData servicesMessaging services text/html 2026-07-16T16:47:48+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/platform_independence?rev=1784220468&do=diff Platform Independence Go to Terms and Definitions Discussion Platform Independence is the characteristic of information, behavior, structure, requirements, or artifacts that do not depend on a particular implementation platform. Platform Independence may apply to: ModelsSpecifications text/html 2026-07-16T16:44:14+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/platform_independent_information?rev=1784220254&do=diff Platform Independent Information Go to Terms and Definitions Discussion Platform Independent Information expresses meaning, structure, behavior, requirements, or constraints without depending on a particular implementation platform. Platform Independent Information may describe: 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/p/platform_independent_model?rev=1784403224&do=diff Platform Independent Model (PIM) Return to Terms and Definitions Discussion A Platform Independent Model, or PIM, provides a technology-neutral logical model of a system. It sits between the conceptual architecture and one or more platform-specific models. Within the FX Demo Reference Architecture, the PIM identifies architectural structures and obligations preserved across conforming implementations. These include node roles, topic concepts, information flows, metadata obligations, control-… text/html 2026-07-13T19:20:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/platform_initialization?rev=1783970441&do=diff Platform Initialization Go up to Terms and Definitions Discussion Platform Initialization is the controlled process of preparing the tools, providers, dependencies, configuration, credentials, and working state required to perform a Deployment on a selected Deployment Platform. The process may initialize Infrastructure as Code tooling, retrieve provider plugins, install provisioning collections, validate access credentials, prepare state storage, configure provider mirrors, and verify platfo… text/html 2026-07-17T16:57:08+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/platform_service?rev=1784307428&do=diff Platform Service Go to Terms and Definitions Discussion A Platform Service is a service that supplies a shared technical capability to applications, Workloads, operators, or other platform components. A Platform Service may supply: IdentityAuthenticationAuthorizationName resolution text/html 2026-07-16T16:44:53+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/platform_specific_information?rev=1784220293&do=diff Platform Specific Information Go to Terms and Definitions Discussion Platform Specific Information expresses implementation details associated with a particular implementation platform. Platform Specific Information may identify: Provider productsResource typesService names 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/p/platform_specific_model?rev=1784403224&do=diff Platform Specific Model (PSM) Return to Terms and Definitions Discussion Platform Specific Model, or PSM, provides a technology-specific model of a system. It sits between the Platform Independent Model (PIM) and the implementation artifacts. Within the FX Demo Reference Architecture (RA), the PSM maps technology-neutral architectural structures and obligations from the PIM to selected platform features. These include middleware constructs, interface definitions, topic definitions, message s… text/html 2026-07-16T16:41:10+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/platform_specific_parameter?rev=1784220070&do=diff Platform Specific Parameter Go to Terms and Definitions Discussion A Platform Specific Parameter supplies a value required to realize a platform-independent specification on a particular implementation platform. The parameter identifies implementation information that varies according to the selection: text/html 2026-08-04T20:41:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/policy?rev=1785876102&do=diff Policy Go up to Terms and Definitions Discussion A Policy is a statement of direction, rule, or constraint established by an Authority to guide or control decisions and actions. A Policy can establish: A required actionA permitted actionA prohibited actionA constraintA decision ruleA responsibility 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/p/policy_and_release_plane?rev=1784403224&do=diff Policy And Release Plane Return to Terms and Definitions Discussion The Policy and Release Plane supports governed decisions about access, disclosure, safeguarding, release, redaction, transformation, marking, obligations, and controlled movement of information. It separates the distribution of internal information from authorized release to another participant, authority, community, jurisdiction, or external recipient. 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/p/policy_and_release_state_considerations?rev=1784403224&do=diff Policy and Release State Consideration Return to Terms and Definitions Discussion Policy and release-state considerations identify the logical conditions governing whether FX information qualifies for external release. The FX Policy and Release Node evaluates release requests, policy constraints, recipient context, purpose, redaction requirements, transformation requirements, marking requirements, obligations, and source information provenance. It produces an 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/p/policy_evaluation_role?rev=1784403224&do=diff Policy Evaluation Role Go up to Terms and Definitions Discussion The Policy Evaluation Role identifies responsibility for evaluating policy constraints governing access, disclosure, safeguarding, release, redaction, transformation, marking, obligations, or the controlled movement of FX 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/p/portability?rev=1784403224&do=diff Portability Return to Terms and Definitions Discussion Portability describes the ability of a governed function implementation to move across approved platforms, runtimes, deployment environments, or operational contexts while preserving required behavior. In the Governed Node Service Market, Portability supports deployment flexibility, provider substitution, resilience, and reduced dependence on a single implementation environment. 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/p/protocol_buffers?rev=1785852565&do=diff Protocol Buffers Return to Terms and Definitions Discussion Protocol Buffers are a Google language-neutral, platform-neutral, extensible mechanism for serialising structured data. Protocol Buffers use .proto definition files to describe structured data. The Protocol Buffers compiler generates language-specific code that supports reading, writing, serialising, and deserialising structured data across files, streams, and network connections. 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/p/provenance?rev=1784403224&do=diff Provenance Go up to Terms and Definitions Discussion Provenance represents information about the origin, derivation, history, transformation, custody, or production of an entity, record, decision, output, or information item. In the FX Demo Reference Architecture, Provenance supports Traceability, Evidence, Audit, replay, reconstruction, review, accountability, and defensibility. text/html 2026-08-04T14:09:26+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/provenance_recording_role?rev=1785852566&do=diff Provenance Recording Role Go up to Terms and Definitions Discussion The Provenance Recording Role identifies responsibility for recording lineage relationships among FX information structures, Nodes, endpoints, interactions, rules, versions, models, decisions, and outputs. This role includes linking inputs to outputs, associating assertions with rule versions or model versions, identifying producing and consuming Nodes, preserving timestamps, and recording relationships needed for replay, re… text/html 2026-07-13T18:08:37+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/provider?rev=1783966117&do=diff Provider Go up to Terms and Definitions Discussion A Provider supplies or operates a resource, service, capability, interface, information source, or operational function for use by another party, system, component, or environment. The Provider role may be fulfilled by an organization, organizational unit, system, service, software component, platform, or infrastructure operator. text/html 2026-07-13T18:09:20+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/provider_abstraction?rev=1783966160&do=diff Provider Abstraction Go up to Terms and Definitions Discussion A Provider Abstraction defines a provider-independent representation of the capabilities, operations, inputs, outputs, errors, and lifecycle behaviors required from one or more Providers. The abstraction separates the requesting software from provider-specific interfaces, software development kits, data formats, authentication mechanisms, and operational details. text/html 2026-07-13T18:10:36+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/provider_contract?rev=1783966236&do=diff Provider Contract Go up to Terms and Definitions Discussion A Provider Contract specifies the capabilities, operations, inputs, outputs, constraints, errors, compatibility rules, and lifecycle behaviors that govern interaction with a Provider through a Provider Abstraction. The contract establishes the obligations that a conforming text/html 2026-07-16T16:45:21+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/provider_implementation?rev=1784220321&do=diff Provider Implementation Go to Terms and Definitions Discussion A Provider Implementation realizes defined capabilities through the products, services, interfaces, resource types, and operational mechanisms supplied by a particular provider. The provider may supply: Cloud infrastructure text/html 2026-07-13T19:36:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/provider_mirror?rev=1783971402&do=diff Provider Mirror Go up to Terms and Definitions Discussion A Provider Mirror is a controlled local or internal copy of infrastructure-provider software packages and associated metadata used by infrastructure automation tooling without direct access to the original distribution source. text/html 2026-07-13T18:11:14+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/provider_plugin?rev=1783966274&do=diff Provider Plugin Go up to Terms and Definitions Discussion A Provider Plugin is a software component that implements a Provider Contract for a particular Provider or class of Providers. The plugin translates provider-independent requests into provider-specific interfaces, commands, data structures, authentication mechanisms, and lifecycle operations. 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/p/provider_registry?rev=1784403224&do=diff Provider Registry Go up to Terms and Definitions Discussion A Provider Registry records and resolves the available Provider Plugins, their identities, supported contract versions, capabilities, compatibility information, and loading mechanisms. The registry provides a controlled discovery point through which core software locates and selects a plugin for a specified 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/p/provisioning?rev=1784403224&do=diff Provisioning Go up to Terms and Definitions Discussion Provisioning is the controlled process of creating, allocating, installing, or configuring resources so that they can provide a defined capability. Provisioning may apply to infrastructure resources, operating systems, software packages, services, users, credentials, storage, networks, runtime components, or application dependencies. 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/p/publisher_role?rev=1784403224&do=diff Publisher Role Return to P Terms Discussion A Publisher Role identifies a Logical Node's responsibility for producing information through a Logical Communication Endpoint. The Publisher Role supports information distribution without requiring direct coupling between the producing Logical Node and consuming Logical Nodes. The Logical Architecture identifies the endpoint and the information structure; later implementation profiles choose the communication mechanism. text/html 2026-07-13T18:35:27+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/pull_lock?rev=1783967727&do=diff Pull Lock Go up to Terms and Definitions Discussion A Pull Lock is a machine-processable record of the exact source revisions resolved and retrieved during a Crucible pull operation. A Pull Lock connects the source references in a Crucible Description to the immutable revision identifiers used in a particular pipeline execution. 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/p/python?rev=1784403224&do=diff Python Return to Terms and Definitions Discussion Python is used in the FX Demo implementation profile as an implementation language for selected Phase 0 nodes. Within the architecture document set, Python belongs to the implementation-specific technology layer and does not define conceptual or logical architecture meaning. text/html 2026-07-12T18:20:05+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/dido/99_annexes/annex-b-terms-and-definitions/p/start?rev=1783880405&do=diff P Return to Terms and Definitions * Note: You can add new terms beginning with P Add New Term Prompt ---------- List of Words * Package * Packet Loss * Part 1 Concept to FX Logical Profile Element * Part 1 Concept to FX Logical Profile Element * Part 1 Concept to Part 2 Logical Element * Pedigree * Performance * Performance Efficiency * Pipeline Workspace * Platform * Platform Deployment * Platform Independence * Platform Independent Information * Platform Independent Model (…