Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top Backlinks This is a list of pages that seem to link back to the current page. MO-001 — Governed Distributed Test EnvironmentsMO-002a — Reproducible Test EnvironmentsMO-002b — Reproducible Test ExecutionMO-002 — Reproducible Test Environments and Test ExecutionMO-003 — Automated Test ExecutionMO-004a — DIDO Baseline ComparisonMO-004b — Validation Decision Based on DIDO Baseline ComparisonMO-004 — DIDO Baseline Comparison and ValidationMO-005 — Comparative Evaluation of Candidate SolutionsENV-001b — Identify Applicable Test DefinitionsENV-001d — Identify Included NodesENV-001f — Define Communication RelationshipsENV-001g — Define Configuration ValuesENV-001i — Define Security ConstraintsENV-001j — Define Deployment ConstraintsENV-001k — Define Version and Baseline InformationENV-001 — Define Test RequirementsENV-002c — Instantiate Included NodesENV-002e — Apply Configuration ValuesENV-002f — Establish Communication RelationshipsENV-002g — Enforce Environmental ConstraintsENV-002h — Enforce Security ConstraintsENV-002i — Enforce Deployment ConstraintsENV-002j — Apply Version and Baseline InformationENV-002k — Record Test Environment ConfigurationENV-002l — Validate Test Environment ConfigurationENV-002 — Configure Test EnvironmentENV-003a — Apply Required BaselineENV-003b — Apply Required Configuration ValuesENV-003c — Initialise Participating NodesENV-003e — Provision Required Test ResourcesENV-003f — Load Required Test InputsENV-003g — Establish Required Communication RelationshipsENV-003h — Apply Applicable ConstraintsENV-003i — Remove or Isolate Residual StateENV-003j — Validate Controlled Starting StateENV-003k — Record Controlled Starting StateENV-003 — Establish Controlled Starting StateENV-004a — Define Deterministic Environmental ConditionsENV-004b — Control Baselines and ConfigurationsENV-004c — Control Test InputsENV-004d — Control Time SourcesENV-004e — Control Random ValuesENV-004f — Control Execution OrderingENV-004g — Control Resource AllocationENV-004h — Control External DependenciesENV-004i — Control Communication ConditionsENV-004j — Detect Environmental VariationENV-004k — Record Environmental VariationENV-004l — Validate Environmental DeterminismENV-004m — Prevent Execution Under Uncontrolled ConditionsENV-004 — Provide Deterministic Test EnvironmentENV-005a — Emulate Distributed TopologyENV-005b — Emulate Participating NodesENV-005c — Emulate Communication BehaviourENV-005d — Emulate Time and Clock ConditionsENV-005e — Emulate Resource ConditionsENV-005f — Emulate Node FailuresENV-005g — Emulate Communication FailuresENV-005h — Emulate Network PartitionsENV-005i — Emulate Membership and Topology ChangesENV-005j — Emulate Recovery BehaviourENV-005k — Observe Distributed InteractionsENV-005l — Record Distributed-System EmulationENV-005m — Validate Emulation FidelityENV-005 — Emulate Distributed SystemsENV-006 — Reproduce Real-World ConditionsENV-007 — Support Repeatable Test EnvironmentsNOD-001a — Identify the Node RoleNOD-001b — Identify the Node TypeNOD-001c — Define Node InterfacesNOD-001d — Define Node DependenciesNOD-001e — Define Node Resource RequirementsNOD-001f — Define Node Lifecycle BehaviourNOD-001g — Define Node Observability RequirementsNOD-001h — Validate the Node DefinitionNOD-001 — Define a NodeNOD-002a — Select the Node DefinitionNOD-002b — Select the Node ImplementationNOD-002c — Resolve Node DependenciesNOD-002d — Allocate Node ResourcesNOD-002e — Instantiate the NodeNOD-002f — Establish the Node Initial StateNOD-002g — Record Node ProvisioningNOD-002h — Validate the Provisioned NodeNOD-002 — Provision a NodeNOD-003a — Select the Node ConfigurationNOD-003b — Resolve Node Configuration ValuesNOD-003c — Apply the Node ConfigurationNOD-003d — Establish Node BindingsNOD-003e — Protect Sensitive Configuration ValuesNOD-003f — Record Node ConfigurationNOD-003g — Validate the Configured NodeNOD-003 — Configure a NodeNOD-004a — Establish the Initial Node StateNOD-004b — Start the NodeNOD-004c — Confirm Node ReadinessNOD-004d — Transition the Node StateNOD-004e — Stop the NodeNOD-004f — Restart or Recover the NodeNOD-004g — Handle a Node Lifecycle ExceptionNOD-004h — Record Node Lifecycle ActivityNOD-004 — Control the Node LifecycleNOD-005a — Authorize Node ExecutionNOD-005b — Initiate Node ExecutionNOD-005c — Provide Node InputsNOD-005d — Observe Node ExecutionNOD-005e — Control Node ExecutionNOD-005f — Handle a Node Execution ExceptionNOD-005g — Complete Node ExecutionNOD-005h — Record Node ExecutionNOD-005 — Execute a NodeNOD-006 — Isolate a NodeNOD-007 — Identify a NodeNOD-008a — Establish Node ObservationNOD-008b — Observe Node StateNOD-008c — Observe Node ActivityNOD-008d — Observe Node Resource UseNOD-008e — Detect a Node DeviationNOD-008f — Record Node ObservationsNOD-008 — Observe a NodeNOD-009a — Establish Node Resource ControlsNOD-009b — Allocate Node ResourcesNOD-009c — Control Node Resource UseNOD-009d — Handle a Node Resource-Control ExceptionNOD-009e — Release Node ResourcesNOD-009f — Record Node Resource ControlNOD-009 — Control Node ResourcesNOD-010a — Specify a Node FaultNOD-010b — Authorize Node Fault InjectionNOD-010c — Prepare Node Fault InjectionNOD-010d — Inject a Node FaultNOD-010e — Control a Node FaultNOD-010f — Recover from a Node FaultNOD-010g — Record Node Fault InjectionNOD-010 — Inject Node FaultsNOD-011a — Specify Node State PreservationNOD-011b — Capture Node StateNOD-011c — Protect Preserved Node StateNOD-011d — Verify Preserved Node StateNOD-011e — Retain Preserved Node StateNOD-011f — Restore Preserved Node StateNOD-011g — Dispose of Preserved Node StateNOD-011h — Record Node State PreservationNOD-011 — Preserve Node StateNOD-012 — Reset a NodeNOD-013 — Maintain Node TraceabilityC.3.2 Node RequirementsC.3.3 Twin Node RequirementsTWIN-001 — Establish Twin IdentityTWIN-009 — Control Twin InteractionTWIN-009a — Identify Permitted Twin InteractionsTWIN-009b — Specify Twin Interaction DirectionNET-001 — Establish a Virtual NetworkNET-002 — Define Virtual Network TopologyNET-003 — Connect Nodes Through a Virtual NetworkNET-004 — Configure Communication CharacteristicsC.3.4 Virtual Network and Communication RequirementsAccess ControlActorAuthenticationCandidate SolutionCatalogCatalog EntryComplianceConfidentialityConfiguration ApplicationConfiguration ParameterConfiguration RecordConfiguration ValueCostCredentialCryptographic MaterialData SourceDistributed Financial SystemEnergy ConsumptionEvaluation CharacteristicException HandlingExecution FacilityExecutable InstructionExecutable InstructionExpected ResultFault InjectionFinancial NodeFunctional CorrectnessGovernance PolicyGovernedIdentifierIdentityInventoryMaintainabilityNetwork TopologyNode BindingNode ConfigurationNode ImplementationNode DefinitionNode SetOperational ResourceOperational StabilityPerformance EfficiencyPolicyQualified NodeQuality CharacteristicReal-World NodeRecoverabilityRegistryReliabilityResourceResource ConsumptionRoleScalabilitySecuritySensitive Configuration ValueSequenced Test ObjectSequence StepStarting ConditionStorage ConsumptionTest ArgumentTest Argument ValueTest CaseTest ExecutableTest ExecutionTest Execution ExceptionTest Execution Exception TypeTest ItemTest ObjectTest ResultTest SequenceTest SetTest StepTimeoutTwin NodeUserValidation CriteriaValidation DecisionVerdictVirtual Network16.1 Overview16.2 Script Role in Phase 016.7 Multi-Node Startup16.11 Script Model Summary17.4 Implementation Compatibility18.2 Part 3 FX Logical Element to Part 4 Implementation Artifact18.3 Implementation Artifact to Part 3 FX Logical Element18.4 Node Implementation Traceability18.5 Topic Implementation Traceability18.10 Implementation Traceability Summary19.3 Implementation Artefacts Prepared for Deployment19.7 Part 5 Handoff20.2 Implementation Artefacts Do Not Redefine Logical Elements20.3 DDS Topics Do Not Redefine Logical Communication Endpoints20.6 Runtime Processes Do Not Redefine FX Logical Nodes20.7 Repository Layout Does Not Redefine Architecture20.8 Scripts Do Not Redefine Interaction Patterns20.12 Implementation Constraints SummaryForewordIntroduction1.1 Purpose of the Handbook1.2 Scope of Phase 01.3 Intended Audience1.4 How to Use This Handbook2.1 Parent Architecture Sources2.2 Relationship to SIP-RA2.3 Relationship to FDIS-RA2.4 Relationship to Parts 1, 2, and 32.5 Relationship to the Phase 0 Implementation Source Material3.1 Purpose of the Phase 0 Baseline3.2 Logical Architecture Baseline3.3 FX Demo Logical Profile Baseline3.4 Implementation Technology Baseline3.6 Baseline Change Control3. Phase 0 Baseline4.3 Source Directories4.5 Configuration Directories4.6 Script Directories4.7 Test Directories4.8 Documentation Directories5.1 Supported Operating Systems5.2 VS Code / Code5.3 Python Environment5.4 Java Environment5.5 DDS Tooling5.6 Docker / Container Environment5.7 Git Environment5.8 Environment Verification5. Development Environment6.1 Required Tools6.2 Optional Tools6.5 Prerequisite Validation6.7 Tool Baseline Checklist6.8 Multiple Products, Platforms, and Implementations7.1 General Naming Principles7.3 Source File Naming7.5 Script Naming7.6 Configuration File Naming7.7 Topic Naming7.8 Node Naming7.9 Container Naming7.11 Spelling, Grammar, and Style7. Naming and File Conventions8.2 Generated Versus Handwritten Files8.3 IDL-Derived Artifacts8.4 Python-Generated Support Artifacts8.5 Generated Documentation9.1 Role of IDL in Phase 09.2 IDL Source Location9.3 Control Plane Type Definitions9.4 Data Plane Type Definitions9.6 Generated Type Locations9.7 Type Generation Validation9.8 Type Compatibility Rules9. DDS / IDL / Type Generation10.2 Node Lifecycle10.3 Node Startup Behavior10.4 Node Runtime Behavior10.5 Node Shutdown Behavior10.6 Node Status Reporting10.7 Node Command Handling10.8 Node Configuration10.9 Node Error Handling10.10 Node Documentation Requirements10. Node Implementation Pattern11.1 Purpose of the Control Plane11.2 Node Status Topic11.3 Node Command Topic11.4 Control Plane Message Semantics11.6 Control Plane Validation11.7 Control Plane Observability11. Control Plane Topics12.1 Purpose of the Data Plane in Phase 012.4 Topic Participation Rules12. Data Plane Topics13.1 Purpose of Build and Run Scripts13.8 buildContainers.sh13.9 runAll.sh13.10 runNode.sh13.11 stopAll.sh14.2 Container Design Principles14.4 Container Runtime Configuration14.6 Container Naming15.1 Purpose of Logging15.4 Node Logs15.6 Container Logs16.1 Purpose of Exception Handling Rules16.4 Configuration Errors16.6 Container Errors16.7 Recoverable and Non-Recoverable Errors16.8 Error Reporting16. Exception Handling17.4 Pull Request Expectations18.3 Type Generation Acceptance Criteria18.4 Node Acceptance Criteria18.5 Control Plane Acceptance Criteria18.6 Data Plane Acceptance Criteria18.7 Container Acceptance Criteria18.8 Documentation Acceptance Criteria18.9 Evidence Acceptance Criteria18.10 Phase 0 Completion Criteria19.2 Full ACTUS Processing19.5 Full IEF Policy Enforcement20.1 Implementation Language Decisions20.3 Python Scope Decisions20.4 Container Runtime Decisions20.7 September 2026 Demo Dependencies20.10 Risk Review and Baseline Acceptance dido/99_annexes/annex-b-terms-and-definitions/n/node.txt Last modified: 2026/08/04 07:10by nick_dido